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

Storage cost estimates often fail because teams only price "stored GB". This guide gives a simple framework to model storage like a real bill: capacity (GB-month) plus activity (requests) plus copies (replication/backup) plus transfer.

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.

Storage validation checklist

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

More storage guides

Artifact Registry pricing (GCP): storage + downloads + egress (practical estimate)

A practical Artifact Registry cost model: stored GB-month baseline, download volume from CI/CD and cluster churn, and outbound transfer. Includes a workflow to estimate GB-month from retention and validate layer sharing and peak pull storms.

Aurora pricing (what to include): compute, storage, I/O, and backups

A practical checklist for estimating Aurora costs: instance hours (or ACUs), storage growth, I/O-heavy workloads, backups/retention, and the line items that commonly surprise budgets.

Aurora Serverless v2 pricing: how to estimate ACUs and avoid surprise bills

A practical way to estimate Aurora Serverless v2 costs: ACU-hours, storage GB-month, backups/retention, and how to model peaks so your estimate survives real traffic.

AWS CloudTrail Pricing & Cost Guide

CloudTrail cost model for management vs data events, Lake vs S3 logs, and pricing drivers with estimation steps.

AWS ECS Pricing & Cost Guide (EC2 vs Fargate drivers)

ECS cost model for compute, storage, and networking. Compare EC2 vs Fargate and identify real cost drivers.

AWS RDS cost optimization (high-leverage fixes)

A short playbook to reduce RDS cost: right-size instances, control storage growth, tune backups, and avoid expensive I/O patterns.

AWS RDS pricing (what to include)

A practical checklist for estimating AWS RDS costs: instances, storage, backups, I/O, and the line items that commonly surprise budgets.

Azure Blob Storage pricing: a practical cost model

Model Blob Storage cost without copying price tables: GB-month, operations, redundancy/replication, retrieval, and egress.

Azure Container Registry Pricing (2026): ACR Cost by Tier

Model Azure Container Registry cost from storage, pull volume, and egress. Compare Basic/Standard/Premium impacts with practical ACR budgeting steps.

Azure Cosmos DB pricing: a practical estimate (RU/s, storage, and egress)

A driver-based Cosmos DB estimate: RU/s capacity, stored GB, and data transfer. Includes a workflow to validate RU drivers and avoid underestimating burst, hot partitions, and retries.

Azure Event Hubs Pricing & Cost Guide (throughput, retention, egress)

Estimate Event Hubs cost from throughput units, ingress, capture/storage, and egress. Includes a planning checklist.

Azure Key Vault pricing: estimate operations, keys/secrets, and request spikes

A practical Key Vault cost model: baseline objects (keys/secrets/certs) plus operation volume. Includes a workflow to map traffic to Key Vault calls and validate caching, retries, and hot-path mistakes.

A practical breakdown of S3-like object storage pricing: GB-month storage, request fees, and data egress - plus how to estimate each without missing hidden line items.

S3 CRR vs SRR cost: what changes (transfer, storage, requests)

A practical cost comparison of S3 cross-region replication (CRR) vs same-region replication (SRR). Compare transfer/feature fees, extra replica storage, and request costs - with calculators.

Copy storage pricing: what you pay for when data moves

A practical guide to pricing storage copy operations (cross-region copy, replication, backups) across S3-like object storage: transfer, requests, and extra storage.

S3 replication cost: how to estimate cross-region replication

A practical guide to estimating S3 replication cost: what data volume to count, which fees to expect, and how to model replica storage, requests, and transfer. Includes a fast checklist.

S3 to Glacier transfer cost: what to include in the move

A practical checklist for S3 to Glacier transfer cost: transition requests, minimum storage duration, and any transfer or rewrite overhead.

S3 pricing: a practical model for storage, requests, egress, and replication

A practical S3 pricing guide: what to include (GB-month, requests, egress, replication) and how to estimate the key inputs without copying price tables.

Related calculators

Data Egress Cost Calculator

Estimate monthly egress spend from GB transferred and $/GB pricing.

API Response Size Transfer Calculator

Estimate monthly transfer from request volume and average response size.

VPC Data Transfer Cost Calculator

Estimate data transfer spend from GB/month and $/GB assumptions.

Cross-region Transfer Cost Calculator

Estimate monthly cross-region transfer cost from GB transferred and $/GB pricing.

RPS to Monthly Requests Calculator

Estimate monthly request volume from RPS, hours/day, and utilization.

API Request Cost Calculator

Estimate request-based charges from monthly requests and $ per million.

FAQ

Why is storage pricing confusing?

Because the bill is rarely just GB-month. Many products add request fees, replication/backup copies, and transfer (egress or inter-region) on top of base storage.

What is GB-month?

GB-month is the average stored GB over the billing month. If you store 100 GB for half the month and 200 GB for half the month, your average is ~150 GB-month.

What usually dominates storage cost?

For large datasets, GB-month dominates. For many small objects, request fees can matter. For multi-region setups, replication plus transfer can dominate.

Last updated: 2026-02-23