Q: You enabled AWS CloudTrail across your organization. However, when you search the logs to find out who uploaded a specific image `logo.png` into an S3 bucket, nothing appears. You only see bucket creation events. Where is the log?
By default, CloudTrail only records Management Events (Control Plane actions). These include creating infrastructure (CreateBucket, RunInstances, UpdateSecurityGroup).
Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "AWS reliability requires differentiating between AWS control plane limits and host-level resource exhaustion. The interviewer is testing: Management Events vs Data Events.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
By default, CloudTrail only records Management Events (Control Plane actions). These include creating infrastructure (CreateBucket, RunInstances, UpdateSecurityGroup). It natively ignores Data Events (Data Plane actions) like s3:GetObject, s3:PutObject, or dynamodb:PutItem because logging trillions of them would result in astronomical CloudTrail bills. To see the logo.png upload, you must explicitly edit the CloudTrail configuration and opt-in to paying to record Data Events specifically targeting that S3 bucket.
- Immediate Triage: By default, CloudTrail only records Management Events (Control Plane actions). These include cr
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Relying on legacy bucket ACLs instead of modern S3 Block Public Access and IAM bucket policies when configuring enabled CloudTrail across AWS recommends disabling ACLs (Bucket Owner Enforced) in favor of centralized declarative bucket policies and account-level Block Public Access controls.
-
Confusing SSE-S3 encryption with KMS customer-managed key (SSE-KMS) authorization policies when configuring enabled CloudTrail across
Accessing SSE-KMS encrypted objects requires both
s3:GetObjectandkms:Decryptpermissions; neglecting KMS key policies causes silent 403 Forbidden errors. - Using sequential timestamps or predictable prefixes for high-throughput S3 read and write keys when configuring enabled CloudTrail across Sequential key prefixes limit S3 horizontal partitioning; randomized hash prefixes distribute workloads across partitions to achieve 3,500 PUT and 5,500 GET requests/sec.
- Failing to audit S3 object delete markers when troubleshooting missing versioned objects when configuring enabled CloudTrail across Issuing a DELETE on a versioned bucket only adds a delete marker; engineers must retrieve previous versions or purge markers to restore data.