There is one moment in day-to-day deployments that anyone who has worked with CloudFormation for a while knows: the update fails, the rollback starts, and then the stack just sits there with UPDATE_ROLLBACK_FAILED . No new deployment, no deletion from the pipeline, just a red status and the question of who changed “just a little thing in the console” yesterday. Whether you use CDK, the Serverless Framework or SAM, there is always a CloudFormation stack underneath, so this affects everyone.

On October 22, 2026, AWS introduced a new option for exactly this situation: Force Rollback . It gets a stack out of UPDATE_ROLLBACK_FAILED with a single call, even when several resources in nested stacks are stuck. That is convenient. It is also a tool that quietly lets drift creep into your infrastructure.…