Here is an introduction to UPDATE_ROLLBACK_COMPLETE AWS status. Our Server Management Support team is here to lend a hand with your queries and issues.

An Introduction to UPDATE_ROLLBACK_COMPLETE in AWS

If we come across the UPDATE_ROLLBACK_COMPLETE AWS error, it indicates that the last stack did not deploy but it can still be updated.

A specific stack that is in the UPDATE_ROLLBACK_FAILED state will continue rolling back to the UPDATE_ROLLBACK_COMPLETE state. Based on the reason behind the failure, we can fix the error and continue the rollback.

If we continue the rollback, we can return the stack to a working state. After that, we can try to update the stack again.

If we get the UPDATE_ROLLBACK_FAILED message, we cannot deploy a new update until the status changes to UPDATE_ROLLBACK_COMPLETE. In this scenario, we can either complete the update rollback process or delete the stack and create a new one.

Although the latter option seems easier, our experts recommend completing the update rollback process.

Our experts recommend using the aws cloudformation continue-update-rollback in order to complete the update rollback.

aws cloudformation continue-update-rollback \
--stack-name StackName \
--resources-to-skip ListOfResources

Here StackName and ListOfResoruces have to be replaced by the name of the stack and the list of the logical IDs of resources that we want to skip. Our experts would like to point out that the ListOfResources should include only those resources in the UPDATE_FAILED state.

Alternatively, we can do this via the AWS Console:

1. First, head to the cloud formation area of the AWS console.
2. Next, choose the stack that needs the rollback.
3. After that, select Continue update rollback under Stack Action.

   In case this update rollback is not successful, we can choose Advanced troubleshooting in the Continue update rollback section and select the resources we want to skip.

Once it is successful, the status will have the “** UPDATE_ROLLBACK_COMPLETE**” status. We will be able to deploy our updates again.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

To sum up, our Support Engineers introduced us to the UPDATE_ROLLBACK_COMPLETE status in AWS. We also got a look at how to change status from UPDATE_ROLLBACK_FAILED to UPDATE_ROLLBACK_COMPLETE status.