AWS adds Force Rollback for stuck CloudFormation stacks

On October 22, 2026, AWS introduced a Force Rollback option in ContinueUpdateRollback that pulls a stack out of UPDATE_ROLLBACK_FAILED in a single call by skipping resources whose rollback failed, including nested stacks. Skipped resources show UPDATE_COMPLETE but no longer match the template, so a drift check is needed before the next deployment.

• Available via --force-rollback in AWS CLI and ForceRollback in the SDK
• Skipped resources show UPDATE_COMPLETE and are reported as NOT_CHECKED by drift detection
• force-rollback and --resources-to-skip are mutually exclusive
• The feature is free and available in all regions