Explanation:
An AWS CloudFormation stack policy is a JSON document that defines the update actions that can be performed on designated resources. During a stack update, you can set a stack policy to prevent intentional or accidental updates to specific stack resources (like databases). By default, all resources can be updated. Creating a stack policy that explicitly allows updates to all resources but explicitly denies Update:* actions on the protected database resource is the correct and most native way to prevent accidental modifications.
Ultimate access to all questions.
Question 24
A company uses AWS CloudFormation to deploy its application infrastructure. Recently, a user accidentally changed a property of a database in a CloudFormation template and performed a stack update that caused an interruption to the application. A SysOps administrator must determine how to modify the deployment process to allow the DevOps team to continue to deploy the infrastructure, but prevent against accidental modifications to specific resources. Which solution will meet these requirements?
A
Set up an AWS Config rule to alert based on changes to any CloudFormation stack. An AWS Lambda function can then describe the stack to determine if any protected resources were modified and cancel the operation.
B
Set up an Amazon EventBridge event with a rule to initiate based on any CloudFormation API call. An AWS Lambda function can then describe the stack to determine if any protected resources were modified and cancel the operation.
C
Launch the CloudFormation templates using a stack policy with an explicit allow for all resources and an explicit deny of the protected resources with an action of Update:*.
D
Attach an IAM policy to the DevOps team role that prevents a CloudFormation stack from updating, with a condition based on the specific Amazon Resource Names (ARNs) of the protected resources.
No comments yet.