A production stack contains a database.
Prevent an operator from deleting the database during a stack update or stack deletion.
Which setting is most appropriate?
Use a resource DeletionPolicy and stack termination protection as appropriate for the required protection boundary.
Detailed explanation
These controls define resource retention and prevent deletion of the stack itself when required.
These controls define resource retention and prevent deletion of the stack itself when required.
Dashboard protection does not protect the database resource.
Dashboard protection does not protect the database resource.
DNS TTL is unrelated to CloudFormation deletion protection.
DNS TTL is unrelated to CloudFormation deletion protection.
A name does not control deletion operations.
A name does not control deletion operations.
Check official documentation
Compare the following points with the official documentation.
CloudFormation DeletionPolicy and termination protectionの公式説明を確認する。
What to confirm
リソース保持ポリシーとスタック削除保護を区別できる。
Key points
- DeletionPolicy
- TerminationProtection
- Database protection
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Resource versus stack scope
DeletionPolicy applies to a resource; termination protection applies to the stack operation.
Retention choice
Retaining a resource avoids data loss but may require separate cleanup and cost management.