A SysOps Administrator initiates an update on an AWS CloudFormation stack. During the update, a resource creation fails. CloudFormation attempts to roll back the stack to its previous stable state, but the rollback process fails, leaving the stack in the UPDATE_ROLLBACK_FAILED state. Which of the following is a common cause for this rollback failure?
- A resource in the stack was manually deleted or modified outside of CloudFormation before the rollback was attempted.Cevap
- BThe rollback was initiated automatically, but CloudFormation requires a manual rollback trigger to proceed from a failed update.
- CThe update was performed using an in-place deployment strategy instead of a blue/green deployment strategy.
- DThe user initiating the update lacks the iam:PassRole permission required to execute the rollback operation.
Cevap
A resource in the stack was manually deleted or modified outside of CloudFormation before the rollback was attempted.
The correct answer is that a resource in the stack was manually deleted or modified outside of CloudFormation before the rollback was attempted. When resources are modified or deleted out-of-band, the stack suffers from drift. During a rollback, CloudFormation attempts to return the resources to their previous configuration. If a resource no longer exists or is in an unexpected state, the rollback operation will fail, placing the stack in the UPDATE_ROLLBACK_FAILED state.
Adım Adım Çözüm
Anahtar Kavram
AWS CloudFormation Rollback Failures and Drift Management