AWS ECR Cost Calculator

Estimate ECR-style costs with a simplified model: storage (GB-month) plus data transfer out. Compare baseline vs peak image usage with your pricing.

Maintained by CloudCostKit Editorial Team. Last updated: 2026-02-07. 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: ECR pricing Guide: estimate image storage Guide: reduce ECR costs Data egress calculator

Inputs

Stored data (GB-month)
Average stored GB over the month (~1.95 TB-month).
Starting storage (GB)
Monthly growth (%)
Months in period
Est 1,560 GB-month avg.
Storage price ($ / GB-month)
Data transfer out (GB/month)
Avg 1.52 Mbps. If pulls are inside AWS/VPC, egress may be lower.
Egress price ($ / GB)
Scenario presets
This is a simplified storage + transfer model. Scanning, replication, and downstream network paths can add cost.

Results

Estimated monthly total
$245.00
Storage
$200.00
Transfer
$45.00
Stored (GB-month)
2,000
Egress (GB/month)
500

Separate quiet image inventory from bursty pull behavior

ECR costs usually have one slow-moving line item and one bursty one. Stored GB-month grows with image retention and tag sprawl. Transfer or pull-driven cost changes when CI, release automation, or clusters pull far more often than teams expect.

  • Measure average stored image size and retained tag count by repository to understand the steady baseline.
  • Estimate pull behavior separately for CI pipelines, cluster nodes, and any public or cross-region consumers.
  • Keep replication, scanning, and downstream compute-network spend outside this page unless you model them explicitly.

Where ECR estimates usually drift

  • Retention sprawl: stale tags and repeated builds grow stored GB-month quietly over time.
  • Release-day pull storms: node churn, rollouts, and CI rebuilds create transfer spikes that averages hide.
  • Cache assumptions: local node cache or pull-through cache behavior changes real pull volume a lot.
  • Boundary confusion: cluster egress, NAT, and runtime networking are adjacent costs, not registry cost.

How to reconcile the estimate with production evidence

  1. Compare stored GB-month against actual repository inventory rather than raw image count alone.
  2. Review CI and deployment windows to see whether pull bursts explain the transfer portion of the bill.
  3. Separate in-region cached pulls from cross-region, internet, or public pull paths before changing prices.
  4. Run a release-week or release-month scenario if the platform behaves very differently during rollouts.

What to do when storage or transfer dominates

If storage dominates, clean up retention policy and tag hygiene. If transfer dominates, investigate image size, rollout frequency, and cache efficiency. If neither explains the broader platform total, the next review belongs with cluster networking, NAT, or workload runtime rather than ECR alone.

Next steps

Guides All calculators Guide: ECR pricing Guide: estimate image storage Guide: reduce ECR costs Data egress calculator

Example scenario

  • 2,000 GB-month stored at $0.10/GB-month and 500 GB/month egress at $0.09/GB.
  • Peak 200% scenario captures release-day pull spikes.

Included

  • Storage baseline: stored GB-month x $ per GB-month.
  • Egress estimate: GB/month transfer out x $ per GB.
  • Optional storage growth estimator (GB-month average).
  • Baseline vs peak scenario table for storage and egress spikes.

Not included

  • Replication, scanning, and feature add-ons unless modeled separately.
  • Compute/network costs in your cluster (node egress, NAT, load balancers).

How we calculate

  • Storage cost = stored GB-month x $ per GB-month.
  • Transfer cost = egress GB/month x $ per GB.
  • Total = storage + transfer.

FAQ

Do internal pulls inside AWS count as internet egress?
Not always. Egress depends on where images are pulled to (same region/VPC vs cross-region vs internet). Use your effective $/GB for the path that applies to your workloads.
How do I estimate stored GB-month?
Use the average stored size over the month. If you retain many tags and rebuild images frequently, stored GB-month grows quickly. Retention policies are the biggest lever.

Related tools

Guide: ECR pricing Guide: estimate image storage Guide: reduce ECR costs Data egress calculator

Related guides

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 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.
Estimate RDS backup storage (GB-month) from retention and churn
A practical method to estimate RDS backup storage (GB-month): start from daily changed data, retention days, and sanity-check with snapshot sizes. Includes common mistakes that inflate backup cost.
RDS backups and snapshots (how to estimate cost)
A practical approach to estimating RDS backup and snapshot storage: retention, growth, and the biggest planning mistakes.

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-07. Reviewed against CloudCostKit methodology and current provider documentation. See the Editorial Policy .