Q: You have 100TB of data in S3 that is accessed very infrequently (once a year for audit). How do you minimize storage costs?
Use S3 Glacier Deep Archive — cheapest storage class. ~$1/TB/month vs S3 Standard ~$23/TB/month.
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: "When an interviewer asks how I troubleshoot this in AWS, I frame it through my hands-on production experience. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
Use S3 Glacier Deep Archive — cheapest storage class. ~$1/TB/month vs S3 Standard ~$23/TB/month.
- Use S3 Lifecycle Policy to auto-transition objects to Glacier after X days.
- Or directly upload to Glacier class if you know immediately it's archival.
- S3 Intelligent-Tiering — auto-moves between tiers based on access patterns (good if access pattern is unpredictable).
Remediation & Permanent Safeguards
Retrieval: takes 12 hours. For audit use case, 12 hours is acceptable. If you need faster retrieval (hours not days), use S3 Glacier Flexible Retrieval (expedited: 1-5 min, standard: 3-5 hours). Setup: Also consider:
- S3 Storage Lens — visibility into which buckets/prefixes have stale data.
- Use S3 Lifecycle Policy to auto-transition objects to Glacier after X days.
- Or directly upload to Glacier class if you know immediately it's archival.
- S3 Intelligent-Tiering — auto-moves between tiers based on access patterns (good if access patter...
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 100TB data accessed 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 100TB data accessed
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 100TB data accessed 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 100TB data accessed Issuing a DELETE on a versioned bucket only adds a delete marker; engineers must retrieve previous versions or purge markers to restore data.