Stack deletion stuck as DELETE_IN_PROGRESS

0

I have a stack that has been stuck as DELETE_IN_PROGRESS for over 2 hours despite the underlying DynamoDB table having been deleted.
I have tried to manually create the table again and delete that to no avail. Is there a way to get that stack marked as DELETED or could someone from AWS support help with that please?

Additionally, will setting the TimeoutInMinutes parameter when creating the stack using the Node SDK help to avoid this in the future or does that only apply for creation of the stack?

Thank you

asked 3 years ago8387 views
3 Answers
1

Just in case someone runs across this in the future, it finally timed out after about 8 hours of being stuck DELETE_IN_PROGRESS.

answered 3 years ago
0

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.

answered 3 years ago
0

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.

answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions