I have a Pulumi configuration to deploy something onto fargate using

awsx

. However, when the service errors, AWS simply keeps trying to deploy the same service and Pulumi hangs indefinitely. How can I get Pulumi to fail on a failed deploy instead of having AWS retry endlessly?

Pulumi should never hang indefinitely. In some cases, it may take something like 10 to 15 mins to fail, but this is common among all IaC tools to my knowledge.

I waited a little over 22 minutes and ended up killing the deploy myself. When I checked the AWS ECS task logs, it looks like it tried to launch the task multiple times failing each time. Is there a way to tell it to fail fast (if the first deploy fails, fail on pulumi)?

I've pasted examples of setting up an ECS Fargate cluster.

@mysterious-family-43099 This is more of an ECS issue than a Pulumi issue, most likely. ECS will continue to try to get the desired count of the service. Have you enabled the deployment circuit breaker on the ECS Fargate service? Also, if you have a load balanced service, the health check settings on the load balancer will come into play as well. You can get into the same kind of situation with CloudFormation as well, so it is not specific to Pulumi.

@quaint-hydrogen-7228 I saw the deployment circuit breaker. I am going to try to enable that. I think my load balancer does 3 health checks before making sure the service is healthy.