Describe a basic lifecycle policy to manage cloud storage costs
This tests cost optimization via tiered storage and automated expiration. Strong answers list transitions from Standard to IA to Glacier, then deletion after set days, plus retrieval costs. A red flag is using manual scripts instead of native lifecycle rules.
This tests whether you can design an automated cost-control policy using cloud-native lifecycle management rather than one-off fixes. A strong answer defines a multi-phase rule set: transition objects from Standard to Standard-IA after 30 days, move them to Glacier Flexible Retrieval after 90 days, and expire them after one year. You should note that rules apply to existing and future objects, that per-request ingestion charges apply for transitions, and that retrieval costs vary by tier.
Read the original → docs.aws.amazon.com
- #mlops
- #cloud-cost-optimization
- #s3
- #storage-lifecycle
- #infrastructure
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.