CloudFormation Force Rollback: Recover from a Stuck Update Rollback in One Operation!
Hi everyone, it's Shii-chan! CloudFormation rollbacks just got easier!
AWS What's New
aws.amazon.com
What was announced?
AWS What's New announced force rollback, which makes it simpler to complete a CloudFormation update rollback. An update rollback returns your stack to a known good state.
The story so far
If some resources could not roll back automatically, you had to identify, list, and retry the operation for each affected resource.
What changes
With force rollback, CloudFormation completes the update rollback in a single operation and returns your stack to a deployable state. Resources that still need attention, such as one affected by a change outside CloudFormation, are recorded so you can review and resolve them before your next deployment.
It works across every CloudFormation workflow:
- AWS CLI
- SDKs
- AWS CDK
- AI agents
Dive Deep
How to use it:
- Run continue update rollback with the force rollback option
- Create a drift-aware change set to review any configuration differences before your next deployment
Details are in "Continue rolling back an update" in the CloudFormation User Guide. Force rollback is available in all Regions at no additional cost.
Wrap-up
- Force rollback completes an update rollback in one operation
- No more finding and retrying each affected resource by hand
- Resources needing attention are recorded and reviewable with a drift-aware change set
- All Regions, no additional cost
This one is for IaC operators who have ever been stuck with a failed rollback!
