A company is building a continuous integration and continuous delivery (CI/CD) pipeline using AWS CodePipeline in a centralized DevTools AWS account. The pipeline needs to deploy application stacks to multiple production member accounts within the same AWS Organization by using AWS CloudFormation. The deployment artifacts are stored in an Amazon S3 bucket in the DevTools account. The company's security policy requires that all data stored in the S3 bucket be encrypted at rest and that access follow the principle of least privilege. During execution, the pipeline fails because the deployment roles in the target production accounts cannot access the artifacts in the S3 bucket. Which combination of actions will allow the pipeline to successfully deploy the application stacks to the production accounts? (Select two.)
- Configure the Amazon S3 artifact bucket in the DevTools account to use an AWS KMS customer managed key, and update the key policy to allow the cross-account IAM roles in the production accounts to perform decryption operations.Cevap
- BConfigure the Amazon S3 artifact bucket in the DevTools account to use the default AWS managed key (aws/s3), and attach a policy to the production execution roles allowing cross-account access to the default key.
- Configure the pipeline's deployment stage to assume a cross-account IAM role in the target production accounts, and update the S3 bucket policy in the DevTools account to grant these roles permission to read the artifacts.Cevap
- DApply a Service Control Policy (SCP) to the production Organizational Unit (OU) that explicitly delegates access to the DevTools account's CodePipeline service role, allowing it to bypass local IAM policies in the production accounts.
- EManually update the configuration of the deployed resources in the production accounts using the AWS Console to point to the central S3 bucket, then configure CloudFormation drift detection to prevent future stack updates from rolling back due to manual changes.