Cloud cost
Lifecycle policy
A rule that automatically moves or deletes stored data after a set condition (an age threshold, most often) without anyone touching it by hand.
Last updated
Definition
A lifecycle policy is what turns a storage-class decision from a one-time manual move into an ongoing, automatic one: transition an object to a colder class after 30 days, expire noncurrent versions after 90, delete an incomplete multipart upload after a week. Without one, every one of those cleanups depends on someone remembering to do it, which is why they usually don't happen.
The failure mode runs in both directions: no policy at all lets storage grow forever, but a policy written without checking a class's minimum storage duration can trigger early-delete penalties the moment it runs. The rule has to match the data's real access pattern, not just an age guess.
Where it shows up
A lifecycle policy is a rule attached directly to a storage bucket or volume in the provider's console, defining an age threshold that triggers a class transition, a version expiration, or a delete. S3's lifecycle configuration is the standard example, visible on the bucket's own management tab.
What makes it expensive
The trap here is writing a policy that transitions data before checking a class's minimum storage duration, which triggers an early-delete penalty the moment it runs. A new policy deserves a full billing cycle of scrutiny afterward. Retrieval and penalty charges on the destination class are what tell you the age threshold was set too aggressively.
Related
More in Cloud cost
- Committed use discount (CUD)
- Reserved instance (RI)
- Savings plan (SP)
- On-demand vs. spot instances
- Data egress
- Amortized, blended, and unblended cost
- Billed vs. effective vs. list vs. contracted cost
- Rightsizing
- Idle and orphaned resources
- Storage class
- Incremental snapshot
- Allocatable capacity
- Requests vs. limits
- Cluster idle
- Workload idle
- Bin packing
- Cost allocation tags
- Tag coverage
- Unallocated spend
- Showback vs. chargeback
- Unit economics
- RI/SP coverage and utilization
- Observability tax
- Metric cardinality
- High-water-mark billing
- Log ingest vs. index
- Snowflake credit
- Auto-suspend / resume minimum
- BigQuery slot
- Bytes scanned & partition pruning
- Time Travel & Fail-safe
Connect a provider. See one number.
Connect your first provider and CostMon normalizes it alongside everything else you run. Your team gets one number everyone can check.