1. What are Lifecycle Rules?

S3 Lifecycle rules automate the transition of objects between storage classes and the expiration (deletion) of objects. They help optimize costs by automatically moving data to cheaper storage as it ages.

Core Concept Lifecycle rules let you define: "After 30 days, move to Standard-IA. After 90 days, move to Glacier. After 365 days, delete." This automation ensures you’re always paying the lowest price for data based on its age.

2. Lifecycle Rule Types


Transition Actions

  1. Move objects to a different storage class after a specified number of days
  2. Example: Move from Standard to Standard-IA after 30 days
  3. Example: Move from Standard-IA to Glacier Flexible after 90 days


Expiration Actions

  1. Delete objects after a specified number of days
  2. Delete expired delete markers (versioned buckets)
  3. Delete incomplete multipart uploads after a specified number of days
  4. Delete previous versions after a specified number of days

3. Transition Waterfall

Transition Order (top to bottom only):

S3 Standard
  ↓
S3 Standard-IA  /  S3 Intelligent-Tiering
  ↓
S3 One Zone-IA
  ↓
S3 Glacier Instant Retrieval
  ↓
S3 Glacier Flexible Retrieval
  ↓
S3 Glacier Deep Archive

You CANNOT transition upward (e.g., Glacier to Standard).
To move data back, you must COPY it to a new object.


4. Transition Constraints

5. Lifecycle Rule Configuration


Rule Scope

  1. Apply to entire bucket or filter by prefix (e.g., logs/) or tags
  2. Multiple rules can apply to the same objects
  3. Maximum: 1,000 lifecycle rules per bucket


Example: Full Lifecycle Policy

Rule: "OptimizeLogStorage"
Filter: Prefix = logs/

Transitions (Current Version):
  Day 0  → S3 Standard (default)
  Day 30 → S3 Standard-IA
  Day 90 → S3 Glacier Flexible Retrieval
  Day 365 → S3 Glacier Deep Archive

Expiration:
  Day 2555 (7 years) → Delete object

Previous Versions:
  Day 30 → Delete previous versions

Incomplete Multipart Uploads:
  Day 7 → Abort and delete


6. S3 Analytics — Storage Class Analysis

  1. Analyzes access patterns over 30+ days and provides recommendations
  2. Helps you decide lifecycle transition timing
  3. Only works for Standard → Standard-IA recommendations
  4. Results viewable in Console or exported to S3 (CSV)

7. Common Lifecycle Patterns


Pattern 1: Log Management

  1. Day 0: Standard → Day 30: Standard-IA → Day 90: Glacier Flexible → Day 365: Delete


Pattern 2: Compliance Archive

  1. Day 0: Standard → Day 30: Standard-IA → Day 90: Glacier Deep Archive → Day 2555 (7yr): Delete


Pattern 3: Media Assets

  1. Day 0: Standard → Day 60: Intelligent-Tiering → No expiration


Pattern 4: Version Cleanup

  1. Current: keep in Standard. Previous: IA after 30d, delete after 90d. Abort multipart after 7d.

8. Cost Optimization Tips

  1. Always enable lifecycle rules for log buckets
  2. Use Intelligent-Tiering for unpredictable access patterns
  3. Abort incomplete multipart uploads — they silently accumulate costs
  4. Delete expired delete markers in versioned buckets
  5. Use S3 Analytics before creating lifecycle rules
  6. Remember minimum storage duration charges

9. When to use

Common scenarios:

  1. Cost optimization — Automatically move infrequently accessed data to cheaper storage classes (e.g., S3 Standard → S3 IA → Glacier) after a set number of days.
  2. Data retention policies — Auto-delete objects after a required retention period (e.g., delete logs after 90 days).
  3. Transition large datasets — Move old backups or archives to Glacier Deep Archive to save costs.
  4. Clean up incomplete multipart uploads — Delete failed/abandoned multipart uploads after X days.
  5. Versioned buckets — Expire or transition previous object versions separately from current versions.


Exam Tip Lifecycle questions: "Automatically move old data to cheaper storage" = Lifecycle Transition rules. "Delete after 7 years" = Lifecycle Expiration. "30 days before Standard-IA" = minimum constraint. "Cannot go from Glacier to Standard" = must copy. "Abort old multipart uploads" = Lifecycle Expiration action. "Unknown access pattern" = Intelligent-Tiering (no lifecycle needed). S3 Analytics helps decide WHEN to create transitions.