Storage Costs Explained (GB-month, requests, retrieval)

Start with a calculator if you need a first-pass estimate, then use this guide to validate the assumptions and catch the billing traps.

This is the storage system budgeting parent page. Use it to model stored data as a real operating system: capacity, copies, retrieval, and lifecycle transitions all belong here before you trust a storage total.

Stay here while you still need the broader storage budget map. Move into S3 pricing, replication, or archive-transition pages only after the broader storage budget shape is clear.

Start here when stored data changes class, copy count, or access pattern

• Use this parent guide first when the bill depends on how data moves between hot, warm, archive, and replica states.
• Stay here if copies, retrieval, and lifecycle transitions are part of the decision instead of treating storage as only GB-month.
• Move to narrower tools after the capacity and lifecycle shape is defined.

The biggest budgeting mistake is treating storage as only stored bytes

Storage budgets drift because multiple cost surfaces move together. Stored GB-month, request activity, replica copies, archive retrieval, lifecycle transitions, and egress do not behave the same way even when teams bucket them together as one storage line.

• Capacity-only planning: teams price stored bytes but ignore requests, retrieval, and copy behavior.
• Lifecycle blind spots: archive moves look cheap until restores, minimum durations, or transitions appear.
• Workflow jump too early: readers often need the system budget map before one S3 workflow page is useful.

1) Start with stored GB-month (capacity)

• Measure average stored GB (or estimate from current size and growth).
• Price it with your $/GB-month rate (watch for storage class/tier changes).
• Tool: object storage cost calculator

2) Add request fees (activity)

Storage is often paired with request pricing (PUT/GET/LIST). If you store many small objects, request fees can be a meaningful percentage of total cost.

• Estimate PUT/GET counts per day, then convert to monthly.
• Check request units (per 1,000 / 10,000 / 1,000,000).

3) Add replication and backups (copies)

• Replica storage: you store a second copy (often close to 1x extra GB-month).
• Replication traffic: bytes copied may be billed as transfer depending on product.
• Tools: storage replication cost, S3 replication cost
• Guide: S3 replication cost explained

4) Add egress/transfer (the common surprise)

When data leaves the storage boundary (to users, to another region, or to a CDN/origin), you may pay egress. Many storage architectures are "bandwidth-shaped": the monthly bill grows with reads/deliveries.

• Tools: egress cost, cross-region transfer
• Guide: egress costs explained

Common pitfalls

• Ignoring growth: GB-month changes over time, even if pricing does not.
• Ignoring small-object amplification: request fees and metadata overhead.
• Counting CDN bandwidth but forgetting origin egress (cache fill).
• Double counting replication: both replica storage and copy traffic can be billed.

Lifecycle decision matrix

• Hot data with frequent reads: prioritize latency tier and optimize request behavior.
• Warm operational data: move to lower-cost class with defined access windows.
• Archive and compliance data: model retrieval fees before deep archive transitions.
• Replication-heavy workloads: split steady writes from one-time migrations.

The common miss at this layer is pricing only stored bytes while copies, retrieval, and lifecycle transitions do the real damage later.

Choose the right next page

• S3 pricing anatomy: use S3 pricing explained when you need the base bill structure.
• Copy-path economics: use S3 replication cost when the main problem is changed data becoming copies and transfer.
• Archive-transition boundary: use S3 to Glacier transfer cost when the main problem is lifecycle moves, duration rules, and restore readiness.

Storage validation checklist

1. Confirm average GB-month, not only end-of-month snapshots.
2. Track top request classes and their billing units.
3. Separate replica storage and replication transfer line items.
4. Reconcile retrieval and egress after lifecycle policy changes.

Related tools

Specialist pages work best after the wider storage budget map is clear. Start with S3 pricing explained, S3 replication cost, or S3 to Glacier transfer cost only when you already know which workflow is actually driving the bill.

More storage guides

Related guides

Related calculators

FAQ