Stack is in UPDATE_ROLLBACK_FAILED state and can not be updated
ID: aws/cloudformation-update-rollback-failed
Version Compatibility
| Version | Status | Introduced | Deprecated | Notes |
|---|---|---|---|---|
| 2 | active | — | — | — |
Root Cause
CloudFormation stack update failed and the rollback also failed, leaving the stack in a broken state. Usually caused by resources that were manually modified outside CloudFormation, or by resources that cannot be rolled back (e.g., RDS with deletion protection).
genericWorkarounds
-
85% success Use ContinueUpdateRollback to skip the failing resources
aws cloudformation continue-update-rollback \ --stack-name my-stack \ --resources-to-skip ResourceLogicalId1 ResourceLogicalId2 # Identify failing resources from stack events: aws cloudformation describe-stack-events --stack-name my-stack
-
82% success Fix the external state that caused rollback failure, then continue rollback
1. Check stack events: aws cloudformation describe-stack-events --stack-name my-stack 2. Identify the resource that failed to rollback 3. Manually fix it (re-create deleted resources, remove deletion protection, etc.) 4. Run: aws cloudformation continue-update-rollback --stack-name my-stack
Sources: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html
Dead Ends
Common approaches that don't work:
-
Deleting the stack to start fresh
75% fail
DELETE will fail if resources have deletion protection, dependencies from other stacks, or non-empty S3 buckets. Even if deletion succeeds, you lose all managed resources and state.
-
Retrying the same update that caused the failure
95% fail
The stack is in a failed state and won't accept updates until the rollback is completed. The same update will fail for the same reason.