INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Break cost into quantity times the matching rate; explain how versions, transitions and replication add quantities and which conditions to check in official pricing.

Prerequisite

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

A calculation relationship, not a network path
A calculation relationship, not a network path1: Quantity — 2,000,000 requests ÷ 1,000 requests/group = 2,000 groups — Rate unit. 2: Rate unit — 2,000 groups × 0.003 CU/group = 6.00 CU — Component cost12QuantityRate unitComponent costA calculation relationship, not a network path1: Quantity — 2,000,000 requests ÷ 1,000 requests/group = 2,000 groups — Rate unit. 2: Rate unit — 2,000 groups × 0.003 CU/group = 6.00 CU — Component cost12QuantityRate unitComponent cost
  1. Quantity → Rate unit2,000,000 requests ÷ 1,000 requests/group = 2,000 groups
  2. 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.

There are 2,000,000 GETs at an invented 0.003 CU per 1,000 requests. How many groups do you multiply by?
Read the answer and reason

Answer: 2,000 groups · First divide by the rate denominator. Multiplying the raw request count by a per-1,000 rate would overstate this component by 1,000 times.

Worked example: calculate four components, then add them

Fictional Region R, one month; CU is not a real currency
Component and quantityInvented rateCalculationSubtotal
Storage: 100GiB for a full month0.04 CU / GiB-month100 × 1 × 0.044.00 CU
GET: 2,000,000 requests0.003 CU / 1,000 requests2,000,000 ÷ 1,000 × 0.0036.00 CU
Retrieval: 50GiB0.02 CU / GiB50 × 0.021.00 CU
Outbound transfer: 20GiB0.10 CU / GiB20 × 0.102.00 CU
Total for these four itemsOther costs excluded4 + 6 + 1 + 213.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.

What is the four-component total in this synthetic example, distinct from storage alone?
Read the answer and reason

Answer: 13.00 CU · Add 4.00 storage + 6.00 GET + 1.00 retrieval + 2.00 transfer = 13.00 CU. This covers only the four invented components and is not an AWS bill.

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.

Same invented conditions, changing only retained storage
ChangeRecalculation
Stored volume rises from 100GiB to 200GiB200 × 0.04 = 8.00 CU
GET, retrieval and transfer unchanged6.00 + 1.00 + 2.00 = 9.00 CU
New four-component total8.00 + 9.00 = 17.00 CU

Choose an option to see the result and explanation.

Only retained storage doubles; the other quantities stay the same. Does the total necessarily double?
Read the answer and reason

Answer: No; the new total is 17.00 CU · Only storage increases by 4.00 CU. Adding that to 13.00 gives 17.00 CU. Recalculate the components whose quantities changed.

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.

At an invented 0.01 CU per 1,000 transitions, 100,000 objects transition once. What is the added request component?
Read the answer and reason

Answer: 1.00 CU · 100,000 ÷ 1,000 = 100 groups; 100 × 0.01 = 1.00 CU. Calculate this separately from storage after the transition or duration minimums.

For a real estimate, return to official pricing with explicit assumptions

  1. Specify Region, bucket type, class, duration, counts and volume including versions.
  2. List operations, retrieved volume, transfer routes, transitions, replication and encryption.
  3. Check matching official rates, denominators, tiers and minimums; align quantities and units.
  4. Review applicable credits/contracts, tax and currency separately; compare estimate with actual usage.

Check, then explain in your own words

  1. Match quantities and rate denominators.
  2. Separate storage, operations, retrieval and transfer.
  3. Add quantities introduced by versions, transitions and replication.
  4. 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.