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.

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

How to get your inputs

  • Inputs: use billing exports, metrics, or logs to get real counts/GB where possible.
  • Units: convert throughput (Mbps) or rates (RPS) into monthly units when needed.
  • Scenarios: build a baseline and a high-usage scenario to avoid under-budgeting.

Result interpretation

  • Storage is steady; transfer usually spikes during deploys, CI, or multi-region pulls.
  • If transfer dominates, optimize cache/pull patterns before trimming storage.

Common mistakes

  • Using a single average and ignoring peak/incident scenarios.
  • Double-counting or missing adjacent line items (transfer, logs, retries).

Advanced inputs to capture

  • Average image size and retained tags per repo drive stored GB-month.
  • Pull volume from CI and cluster nodes can spike during releases.
  • Account for cache hit rates so you do not double count pulls.
  • Separate in-region pulls from cross-region or public pulls.

Scenario planning

Scenario Stored GB Egress GB Drivers
Baseline Average Typical Normal pull rate
Peak High Spike Release day / CI surge

Validate after changes

  • Compare your estimate to the first real bill and adjust assumptions.
  • Track the primary driver metric (requests/GB/count) over time.

Next steps

Advertisement

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

Related guides

Advertisement

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