A CloudFormation update fails while creating a resource.
Avoid leaving a partial configuration and automatically return to the pre-update state.
Which setting is most appropriate?
Use CloudFormation rollback behavior and the appropriate OnFailure configuration for the stack operation.
Detailed explanation
The stack can return resources to the prior state when creation or update fails.
The stack can return resources to the prior state when creation or update fails.
S3 object versions do not restore CloudFormation resource state.
S3 object versions do not restore CloudFormation resource state.
DNS TTL does not control CloudFormation rollback.
DNS TTL does not control CloudFormation rollback.
Manual deletion can break dependencies and leave the stack in an unstable state.
Manual deletion can break dependencies and leave the stack in an unstable state.
Check official documentation
Compare the following points with the official documentation.
AWS CloudFormation rollback on failureの公式説明を確認する。
What to confirm
スタックの失敗状態とロールバック動作を説明できる。
Key points
- CloudFormation rollback
- OnFailure
- Update failure
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Atomic change
Rollback reduces the chance that an update leaves a partially applied configuration.
Recovery state
The stack event and rollback result should be inspected before another change.