- Newest
- Most votes
- Most comments
@hameedullah Thanks for the quick answer. I checked my CloudFormation template and there are no hardcoded resource IDs. This is the same template that I've essentially used for years (making occasional updates to the AMI's and whatnot) and this is the first time I've had it fail like this. As for the routes, those are dynamically created in the CloudFormation template, which again, hasn't changed.
I ended up going with my gut and telling it not to rollback on failure. I then told it to re-run at that point with the exact same CloudFormation script. Low and behold, it ran through to successfully complete. So I think something changed with the AWS process that made it fail, but at least I have a way to successfully bypass the error and get it working.
Relevant content
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 months ago
This is a generic error msg and sometimes it is the cause of another resources which is referenced from LoadBalancer not provisioned correctly. Can you please check your cloudformation template if there are any hardcoded resource IDs. I have seen this issue happening also when the routes were not configured properly in the referenced Subnets. Please check for reference: https://github.com/aws-samples/ecs-refarch-cloudformation/blob/master/infrastructure/load-balancers.yaml