Cloudformation stuck on UPDATE_COMPLETE_CLEANUP_IN_PROGRESS for a couple of hours.


Cloudformation is trying to delete the ingress custom resource I have created in my EKS cluster, but it is waiting for a reply from the ALB controller which due to improper permissions and configuration won't return anything. As a result, the stack is unable to continue. I am wondering if there is anyway to force kill cloudformation out of this state or reduce the 3-hour timeout period?

1 Answer

Dear Customer - Thanks for reaching out to us via AWS re:Post

A CloudFormation stack gets stuck in the UPDATE_COMPLETE_CLEANUP_IN_PROGRESS state when AWS CloudFormation is still in the process of removing old resources, or cannot remove those resources due to a dependency issue.

This has been conveyed in the Knowledge Center article, here I hope the above information was helpful

answered a year 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