Wondering how to resolve CloudFormation stack stuck in UPDATE_ROLLBACK_FAILED state? We can help you.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see how our Support techs assist with this query.

How to resolve CloudFormation stack stuck in UPDATE_ROLLBACK_FAILED state?

For this issue, actions that you can perform on the stack are the ContinueUpdateRollback or DeleteStack operations.

This is because CloudFormation requires further input from you to acknowledge that the stack is out of sync with the template that the stack is attempting to roll back to.

To retry the rollback and resolve the error, you can use ContinueUpdateRollback.

Please note to resolve the error, you might need to raise limits, change permissions, or modify other settings.

In some cases, retrying the rollback doesn’t resolve the error.

In these cases, you must skip resources, and also acknowledge that these resources no longer reflect the desired state in the CloudFormation template.

Today, let us see the steps followed by support techs to resolve it.

1. Firstly, open the CloudFormation console.
2. Then from the navigation pane, choose Stacks.
3. From the Stack name column, select the stack that’s stuck in UPDATE_ROLLBACK_FAILED status.
4. If you don’t want to skip resources, choose Stack Actions, and then choose Continue update rollback.

-or-

If you want to skip FAILED resources during rollback, complete the following:

1. From the Stack name column, select the stack that’s stuck in UPDATE_ROLLBACK_FAILED status.
2. Choose Stack Actions, and then choose Continue update rollback.
3. In the Continue update rollback dialog box, expand Advanced troubleshooting.
4. In the Resources to skip – optional section, select the resources that you want to skip.
5. Finally, choose Continue update rollback.

[Need help with the process? We’d be happy to assist]

Conclusion

In short, we saw how our Support Techs resolve CloudFormation UPDATE_ROLLBACK_FAILED state error.