The Six-Million-Dollar Lifecycle RulePipeline · medium · ~12 minYour company stores 230PB in production S3 — the largest bucket holds 45PB and 300B+ objects, dominated by user-generated content that's hot briefly after creation and then rarely touched.Finance has flagged the storage line. A platform engineer drafts the fix as one account-wide lifecycle rule:*"Any object older than 30 days transitions to Glacier Instant Retrieval. One rule, every bucket, ship it Friday."*You're the reviewer. The proposal's savings estimate multiplies the per-GB price delta by 230PB — and mentions no other bill line. One bucket in the estate has caught your attention: ~90% of its bytes already sit in Standard-IA, yet the access logs say 60-70% of all reads hit the ~10% still in Standard.Evidence

The estate, by the numbers

The proposed rule + the price sheet

Storage Class Analysis, sampled per bucket

Checkpoints

What does the telltale bucket — 90% of bytes in Standard-IA, but 60-70% of accesses hitting the Standard slice — actually tell you?

The media-assets bucket alone would transition ~80 billion objects. At $0.02 per 1,000 transition requests, what is the one-time transition fee for that bucket, in millions of dollars?

Why must the account-wide rule categorically exclude buckets like thumbs-cache (billions of objects averaging ~14KB)?

Rewrite the proposal as a per-bucket decision framework: what gets measured before any rule ships, the arithmetic gate a bucket must pass, how the target class is chosen, and what you monitor afterwards.