Topic lessonTopic: S3: versions, retention, replication and cost
How to estimate S3 costs: storage, requests, retrieval and transfer
S3 cost is more than stored capacity. Separate storage class and duration, request counts, retrieved volume and transfer route. Practice matching units in a synthetic example using invented rates rather than current AWS prices.
Break cost into quantity times the matching rate; explain how versions, transitions and replication add quantities and which conditions to check in official pricing.
Know S3, Versioning, Lifecycle and Replication. Values describe a teaching-only general purpose bucket in fictional Region R for one complete month. CU is an invented cost unit, not USD or JPY. This is not an AWS quote, free-use guarantee or bill forecast.
Match the quantity to the rate’s denominator
- Quantity → Rate unit2,000,000 requests ÷ 1,000 requests/group = 2,000 groups
- Rate unit → Component cost2,000 groups × 0.003 CU/group = 6.00 CU
- Quantity
- Example: 2,000,000 GET requests. Identify what is counted.
- Rate unit
- Example: 0.003 CU per 1,000 requests; use 2,000 groups.
- Component cost
- 2,000 × 0.003 = 6.00 CU, separate from other components.
For a real estimate, track storage, requests, data retrieval and transfer separately, then add relevant management or replication features. A GET request count and the volume retrieved by that request are distinct quantities.
Choose an option to see the result and explanation.
Worked example: calculate four components, then add them
| Component and quantity | Invented rate | Calculation | Subtotal |
|---|---|---|---|
| Storage: 100GiB for a full month | 0.04 CU / GiB-month | 100 × 1 × 0.04 | 4.00 CU |
| GET: 2,000,000 requests | 0.003 CU / 1,000 requests | 2,000,000 ÷ 1,000 × 0.003 | 6.00 CU |
| Retrieval: 50GiB | 0.02 CU / GiB | 50 × 0.02 | 1.00 CU |
| Outbound transfer: 20GiB | 0.10 CU / GiB | 20 × 0.10 | 2.00 CU |
| Total for these four items | Other costs excluded | 4 + 6 + 1 + 2 | 13.00 CU |
This example uses GiB = 2³⁰ bytes. The S3 pricing page describes storage GB using that binary unit. For a real estimate, review meter units, storage changes within the month and class-specific billable quantities. A point-in-time reading of “100GB now” is not automatically the monthly average.
Choose an option to see the result and explanation.
Versions and object counts affect storage and operations
Versioning stores complete versions, not only their differences. A key absent from an ordinary listing may still retain older stored versions. Review delete markers and incomplete multipart uploads too.
| Change | Recalculation |
|---|---|
| Stored volume rises from 100GiB to 200GiB | 200 × 0.04 = 8.00 CU |
| GET, retrieval and transfer unchanged | 6.00 + 1.00 + 2.00 = 9.00 CU |
| New four-component total | 8.00 + 9.00 = 17.00 CU |
Choose an option to see the result and explanation.
Identify the additional quantities introduced by transitions and replication
A transition introduces per-object transition requests, not just a different storage rate. At an invented 0.01 CU per 1,000 transitions, moving 100,000 objects once costs 100,000 ÷ 1,000 × 0.01 = 1.00 CU. This increment is excluded from the earlier four-component totals.
Some classes impose minimum duration or billable size, so early deletion can leave charges. For archives, review metadata, retrieval and temporary restored copies. “Old data belongs in a cheaper class” is insufficient to determine total cost or usability.
For replication, separate destination storage, replication requests and transfer. Review inter-Region transfer for CRR rather than assuming identical transfer treatment for SRR. Add the relevant RTC, Batch and KMS terms when used. Creating a replica does not remove source storage charges.
Choose an option to see the result and explanation.
For a real estimate, return to official pricing with explicit assumptions
- Specify Region, bucket type, class, duration, counts and volume including versions.
- List operations, retrieved volume, transfer routes, transitions, replication and encryption.
- Check matching official rates, denominators, tiers and minimums; align quantities and units.
- Review applicable credits/contracts, tax and currency separately; compare estimate with actual usage.
Check, then explain in your own words
- Match quantities and rate denominators.
- Separate storage, operations, retrieval and transfer.
- Add quantities introduced by versions, transitions and replication.
- Verify official pricing assumptions and recalculate.
Check your understanding: Does knowing “100GB stored in S3” determine the cost?
No. You also need duration, class, versions, operations, retrieval, transfer and other applicable conditions.
Multiply each quantity by its matching rate and include the applicable components. Do not reuse this lesson’s invented rates as an actual quote.
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.
- Amazon S3 pricingChecked:
Scope and conditionsFee axes, binary storage GB, Region/class/count/duration conditions and replication; no live rates quoted; all classroom prices explicitly invented
Used in this lessonMatch the quantity to the rate’s denominator Worked example: calculate four components, then add them Identify the additional quantities introduced by transitions and replication
- How S3 Versioning worksChecked:
Scope and conditionsPUT/GET/DELETE workflows; opaque version IDs; whole-object storage per version
Used in this lessonVersions and object counts affect storage and operations
- Working with delete markersChecked:
Scope and conditionsNo-data marker; current versus explicit marker GET; listing and storage charges
Used in this lessonVersions and object counts affect storage and operations
Scope and conditionsIncomplete parts are distinct from completed objects; dedicated abort action; no tag-based filter
Used in this lessonVersions and object counts affect storage and operations
- Understanding S3 storage classesChecked:
Scope and conditionsRetrieval versus storage; minimum size/duration; Glacier restoration differences
Used in this lessonIdentify the additional quantities introduced by transitions and replication
Scope and conditionsSupported directions; 128KB defaults and older configurations; per-object overhead; asynchronous processing; class costs
Used in this lessonIdentify the additional quantities introduced by transitions and replication
- Replication requirementsChecked:
Scope and conditionsBoth buckets versioning-enabled; ownership/Object Lock boundary; destination Lifecycle original age; Region transfer differences
Used in this lessonIdentify the additional quantities introduced by transitions and replication
- Replicating encrypted objectsChecked:
Scope and conditionsExplicit KMS opt-in; source/destination key permissions; valid destination-Region key; save success is not copy completion; Bucket Key boundary
Used in this lessonIdentify the additional quantities introduced by transitions and replication