Topic lessonTopic: S3: versions, retention, replication and cost
S3 Lifecycle explained: storage transitions and version expiration
S3 Lifecycle applies rules to transition eligible objects between storage classes or expire them. “Make old data cheaper” is incomplete: identify the target version, age, action and cost, including how long recovery can take.
Distinguish transitions, expiration, current/noncurrent versions, delete markers and incomplete multipart uploads; explain how to review a rule against retention needs.
Know S3 keys and Versioning. The synthetic example uses an enabled general purpose bucket without protections that prevent deletion. The figure illustrates eligible actions, not their exact execution times or a real deletion.
First distinguish what should remain from what may expire
A transition changes storage class; expiration concerns removal. A new rule also applies to eligible existing data. In a general purpose bucket, a bucket-policy Deny does not stop Lifecycle actions. Review the affected data before enabling a rule.
- Current data vB → Current markerIf current-version expiration applies, a marker is added rather than deleting every data version.
- Noncurrent data vA → vA removedIf NoncurrentVersionExpiration conditions are met; a different target from the upper row.
- Current data vB
- Data selected by an ordinary read.
- Current marker
- Current expiration adds a marker; vB becomes noncurrent.
- Noncurrent data vA
- Age is measured from becoming noncurrent.
- vA removed
- Noncurrent expiration permanently removes that version.
Choose an option to see the result and explanation.
Read the filter and the age being measured
| Field | Meaning |
|---|---|
| Filter | Selects by prefix, tags or size; an empty filter covers the bucket |
| Current-version Days | Age from creation of that object version |
| NoncurrentDays | Age since the version became noncurrent |
| Newer noncurrent versions to retain | When configured, review both age and retained-count conditions and the Filter requirement |
The day draft vA was stored differs from the day final vB superseded it. The noncurrent age of vA starts when its successor vB is created. Days does not generally mean time since the last read. Eligibility uses UTC date boundaries, and physical processing is asynchronous.
Choose an option to see the result and explanation.
Separate data versions, markers and incomplete uploads
| Target | Action and caution |
|---|---|
| Current version | Unversioned: permanent deletion; enabled: normally add a marker; suspended: consider replacement of a null version |
| Noncurrent version | NoncurrentVersionExpiration permanently deletes it; choose retention separately |
| Expired object delete marker | Cleanup targets a marker after no data versions remain |
| Incomplete multipart upload | AbortIncompleteMultipartUpload is separate from expiration of completed objects |
A multipart upload sends data in separate parts. Those parts may remain even though an incomplete upload has not produced a completed object. AbortIncompleteMultipartUpload removes the incomplete parts, not completed objects. Its rules cannot use tag-based filters.
Choose an option to see the result and explanation.
Separate supported transitions from cost-effective transitions
Current Lifecycle configurations do not transition objects smaller than 128KB by default. Explicit size filters can alter eligibility, but per-object transition charges can outweigh savings. Older configurations may retain pre-September-2024 defaults, so inspect the actual configuration.
Do not select a storage class by storage rate alone. S3 Glacier Flexible Retrieval and Deep Archive require restoration before reading. Moving immediately needed data there changes the application access model. Supported onward transitions also depend on the source class.
| Storage class | Minimum storage duration |
|---|---|
| Standard-IA / One Zone-IA | 30 days |
| Glacier Instant Retrieval / Flexible Retrieval | 90 days |
| Glacier Deep Archive | 180 days |
Choose an option to see the result and explanation.
Separate eligibility from completed processing
Eligibility is not a guarantee of instant completion. Distinguish queued work from ineligible data or incorrect rules. An ordinary object listing does not cover older versions or incomplete uploads. Billing changes do not always coincide with physical processing; Intelligent-Tiering transitions have a specific exception.
- Define retention, recovery window and immediate-access needs.
- Identify filters, versioning state and whether targets are current versions, older versions or parts.
- Choose transition, expiration or abort; review age and storage-class conditions.
- Review cost and permanent-deletion effects, then verify the relevant versions and results.
Check, then explain in your own words
- Choose targets and retention.
- Separate current and noncurrent age.
- Distinguish transitions, expiration and aborts.
- Review costs and completion evidence.
Check your understanding: Does current-version expiration remove all older data and storage charges?
No. Review versioning state, retained versions, separate expiration actions and minimum-duration charges.
An object becoming invisible to an ordinary read is different from permanent removal of all versions; processing and billing each have conditions.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsTransition versus expiration; existing data; asynchronous actions and billing exception; bucket policy does not block Lifecycle
Used in this lessonFirst distinguish what should remain from what may expire Read the filter and the age being measured Separate eligibility from completed processing
- Lifecycle configuration elementsChecked:
Scope and conditionsFilters; current/noncurrent ages; data versions/markers/multipart; UTC eligibility; count/age conditions
Used in this lessonFirst distinguish what should remain from what may expire Read the filter and the age being measured Separate data versions, markers and incomplete uploads
- Expiring objectsChecked:
Scope and conditionsCurrent versus noncurrent; versioning states; asynchronous expiration; minimum duration
Used in this lessonFirst distinguish what should remain from what may expire Separate data versions, markers and incomplete uploads Separate eligibility from completed processing
Scope and conditionsIncomplete parts are distinct from completed objects; dedicated abort action; no tag-based filter
Used in this lessonSeparate data versions, markers and incomplete uploads
Scope and conditionsSupported directions; 128KB defaults and older configurations; per-object overhead; asynchronous processing; class costs
Used in this lessonSeparate supported transitions from cost-effective transitions
- Understanding S3 storage classesChecked:
Scope and conditionsRetrieval versus storage; minimum size/duration; Glacier restoration differences
Used in this lessonSeparate supported transitions from cost-effective transitions