A healthcare software-as-a-service (SaaS) provider uses AWS Organizations to manage member accounts. To meet strict regulatory auditing requirements, a Solutions Architect must design a solution that automatically aggregates AWS CloudTrail logs from all AWS Regions and all current and future member accounts. The logs must be stored in a single centralized Amazon S3 bucket located in a dedicated security operations account. The architecture must enforce that all logs are encrypted at rest using a customer managed KMS key. To prevent tampering, administrators of the member accounts must not have permission to decrypt the stored logs, nor should they be able to modify or delete the logging configuration. Which TWO actions must the Solutions Architect take to design a secure and compliant centralized logging architecture? (Select TWO.)
- Configure the S3 bucket policy in the dedicated security operations account to allow the "cloudtrail.amazonaws.com" service principal to perform "s3:PutObject" actions, restricted by a condition checking the organization ID. Configure the customer managed KMS key policy in the security operations account to allow "cloudtrail.amazonaws.com" to perform "kms:GenerateDataKey*" and "kms:DescribeKey" actions, restricted by the same organization ID condition.Cevap
- Create an organization trail from the management account (or delegated administrator account) of the AWS Organization. Configure the trail to deliver log files to the centralized S3 bucket in the dedicated security operations account, and configure it to use the Amazon Resource Name (ARN) of the customer managed KMS key located in the security operations account for encryption.Cevap
- CDeploy a Service Control Policy (SCP) to all organizational units (OUs) that allows member accounts to write logs to the centralized S3 bucket, and configure each member account to assume a role in the security operations account to run local CloudTrail trails.
- DEnable default S3 bucket encryption on the centralized S3 bucket using the AWS-managed KMS key (aws/s3). Rely on AWS-managed S3 bucket keys to automatically handle cross-account key permissions and ensure that member accounts are restricted from decrypting the logs.
- ECreate an S3 bucket policy in the dedicated security operations account that grants "s3:PutObject" permissions to the root principal of each member account, and use S3 Object Lock in compliance mode to prevent the member accounts from reading or modifying the files.