An organization has enabled log file integrity validation on an active AWS CloudTrail trail. While the trail successfully delivers CloudTrail log files to the destination Amazon S3 bucket, the administrator notices that no digest files are being generated or delivered to the bucket, preventing log validation. Which of the following is the most likely cause of this issue?
- AThe IAM policy attached to the CloudTrail service role is missing the iam:PassRole permission, which prevents CloudTrail from passing the execution role to the S3 bucket during digest delivery.
- BAn Amazon EventBridge rule is missing to trigger an AWS Systems Manager Automation document that initiates digest file generation when log files are written to S3.
- The S3 bucket policy limits s3:PutObject permissions to the path prefix AWSLogs/123456789012/CloudTrail/*, which prevents CloudTrail from delivering the digest files to the prefix AWSLogs/123456789012/CloudTrail-Digest/*.Cevap
- DThe KMS key policy used to encrypt the trail does not allow the kms:GenerateDataKey action for the digest prefix, although it allows it for the log prefix.
Cevap
The S3 bucket policy limits s3:PutObject permissions to the path prefix AWSLogs/123456789012/CloudTrail/*, which prevents CloudTrail from delivering the digest files to the prefix AWSLogs/123456789012/CloudTrail-Digest/*.
The correct answer is correct because CloudTrail log file integrity validation stores digest files under the 'CloudTrail-Digest' prefix rather than the standard 'CloudTrail' prefix. If the S3 bucket policy is overly restrictive and only grants permissions for the standard prefix, CloudTrail will fail to write the digests, resulting in missing files and validation failures.
Adım Adım Çözüm
Anahtar Kavram
CloudTrail S3 Bucket Permissions for Log File Integrity Validation