- Newest
- Most votes
- Most comments
Just in case someone runs across this in the future, it finally timed out after about 8 hours of being stuck DELETE_IN_PROGRESS.
As an additional aside, I went through the cloudtrail logs during the time period the Cloudformation stack was to be deleted as shown in the "Why is my AWS CloudFormation stack stuck in progress?" AWS youtube video. Sadly, in this case I did not see any errors in the log events.
After some experimentation on another account and being able to recreate it, it looks like it is because programmatically detached and deleted the policy from the user that was used to kick off the teardown of the stack. I was able to recreate/attach the policy on the other account to the user and the cloud formation DELETE_IN_PROGRESS was able to resolve and finish out.
However, on the account I had the issue in the first place on, I have already deleted the user. I have tried to create a user with the same name and same policy attached but it looks like cloudformation is going off of the User ARN since this doesn't work. So it looks like I will still need someone to go in and possibly change that status on the AWS support side.
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 2 months ago
- How do I update a CloudFormation stack that's failing because of a resource that I manually deleted?AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago