AWS EBS Cost Calculator (GB-month + IOPS)

Estimate EBS-style block storage cost with a simple model: storage + provisioned IOPS + provisioned throughput. Compare baseline vs peak capacity with your effective pricing.

Maintained by CloudCostKit Editorial Team. Last updated: 2026-02-23. Editorial policy and methodology.

Best next steps

Use this calculator for the first estimate, then validate the answer with the closest guide or companion tool.

Guide: EBS pricing (what to include) Guide: gp3 IOPS and throughput Guide: gp2 vs gp3 cost Guide: EBS snapshot cost

Inputs

Storage (GB-month)
Approx 0.49 TB-month.
Storage price ($ / GB-month)
Provisioned IOPS (IOPS-month)
Avg IOPS
IOPS price ($ / IOPS-month)
Provisioned throughput (MB/s-month)
Avg throughput (MB/s)
Throughput price ($ / MB/s-month)
Headroom (%)
Use 120-150% for bursty workloads.
Est 4,375 IOPS, 150 MB/s.
Scenario presets

Results

Estimated monthly total
$80.00
Storage
$40.00
Provisioned IOPS
$30.00
Provisioned throughput
$10.00
IOPS-month
6,000
MB/s-month
250
Performance share
50%

Separate storage baseline from paid performance headroom

EBS does not usually surprise teams because storage exists. It surprises them because performance is provisioned above what the workload really needs, or because storage and snapshot thinking get mixed together into one blurry number.

  • Measure storage GB-month separately from paid IOPS and throughput so you can see which side is driving spend.
  • Keep volume type explicit: gp2, gp3, and more specialized profiles do not carry the same cost shape.
  • Treat snapshots and backup retention as adjacent storage programs, not part of this core volume estimate.

Where EBS estimates usually drift

  • Idle overprovisioning: volumes often stay oversized long after the peak event that justified them.
  • Paid performance headroom: IOPS and throughput premiums can dominate when teams provision for worst case and never revisit it.
  • Volume-type mismatch: staying on an older or more expensive performance profile distorts the monthly baseline.
  • Snapshot confusion: teams sometimes blame the volume page for snapshot or backup line items that belong elsewhere.

How to reconcile the estimate with the bill

  1. Compare billed storage, IOPS, and throughput charges with the actual volume configuration in the same period.
  2. Check whether volumes are still provisioned for a past incident, migration, or benchmark instead of current workload.
  3. Review whether snapshot storage is being counted as part of the core EBS spend by mistake.
  4. Run a right-sized scenario beside the current scenario to see how much cost is really tied to performance headroom.

What to do when one component dominates

If performance dominates, revisit IOPS, throughput, and volume-type choice. If storage dominates, inspect stale volumes and oversized allocations. If the broader block-storage program still looks expensive after that, the next stop is snapshots, backups, and restore policy rather than more tuning of the core volume estimate.

Next steps

Guides All calculators Guide: EBS pricing (what to include) Guide: gp3 IOPS and throughput Guide: gp2 vs gp3 cost Guide: EBS snapshot cost

Example scenario

  • 500GB, 6,000 IOPS, 250 MB/s throughput - estimate monthly storage + performance charges.
  • Peak 220% scenario helps budget for scaling bursts.

Included

  • Storage cost from GB-month x $/GB-month.
  • IOPS cost from IOPS-month x $/IOPS-month (if your volume type charges for it).
  • Throughput cost from MB/s-month x $/MB/s-month (if your volume type charges for it).
  • Optional IOPS and throughput headroom estimator.
  • Baseline vs peak scenario table for capacity spikes.

Not included

  • Snapshots/backup storage, data transfer, and EC2 instance costs.
  • Tiered pricing and per-volume-type minimums unless you reflect them in pricing inputs.

How we calculate

  • Storage cost = GB-month x $ per GB-month.
  • IOPS cost = provisioned IOPS x $ per IOPS-month (set price to 0 if not billed).
  • Throughput cost = provisioned MB/s x $ per MB/s-month (set price to 0 if not billed).
  • Total = storage + IOPS + throughput.

FAQ

Do all EBS volume types charge for IOPS and throughput?
No. Some volume types include baseline performance and only charge for storage, while others bill separately for provisioned performance. Use $0 for components that don't apply to your plan.
Does this include snapshots?
No. Snapshots are typically billed as separate storage. Model them separately if you take frequent snapshots or keep long retention.
How should I estimate GB-month?
Use the average allocated storage (or average used, depending on billing). If storage grows over time, model multiple months or scenarios.

Related tools

Guide: EBS pricing (what to include) Guide: gp3 IOPS and throughput Guide: gp2 vs gp3 cost Guide: EBS snapshot cost EBS snapshot cost calculator Guide: EBS cost optimization EC2 cost calculator

Related guides

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.
Storage Costs Explained (GB-month, requests, retrieval)
A practical storage cost model: GB-month, requests, retrieval, and transfer. Includes estimation checklist.
CDN Cost Comparison Guide: Compare Pricing, Per-GB Rates, and Provider Trade-Offs
Compare CDN pricing across providers with a practical framework for bandwidth, requests, per-GB rates, regional mix, and origin egress. Built for CDN cost comparison and provider-decision workflows.
Cloud cost estimation checklist: build a model Google (and finance) will trust
A practical checklist to estimate cloud cost without missing major line items: requests, compute, storage, logs/metrics, and network transfer. Includes a worksheet template, validation steps, and the most common double-counting traps.
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.
Google Kubernetes Engine (GKE) pricing: nodes, networking, storage, and observability
GKE cost is not just nodes: include node pools, autoscaling, requests/limits (bin packing), load balancing/egress, storage, and logs/metrics. Includes a worked estimate template, pitfalls, and validation steps to keep clusters right-sized.

Disclaimer

Educational use only. Not legal, financial, or professional advice. Results are estimates based on the inputs and assumptions shown on this page. Verify pricing and limits with your providers and documentation.

Last updated: 2026-02-23. Reviewed against CloudCostKit methodology and current provider documentation. See the Editorial Policy .