AWS Egress Cost Calculator: Model Baseline vs Peak Transfer Spend

Use this calculator to price one transfer boundary at a time, compare baseline and peak months, and decide what to optimize next. It is designed for estimation and action planning, not just formula output.

Maintained by CloudCostKit Editorial Team. Last updated: 2026-04-19. 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.

Validate boundary assumptions (guide) Map AWS network line items (guide) Estimate CDN origin + edge bandwidth Estimate replication and DR transfer

Inputs

Data transfer (GB / month)
Avg throughput: 7.61 Mbps.
Avg throughput (Mbps)
Estimate helper
Est 24,624 GB/month.
Pricing mode
Use tiered mode when pricing changes by volume.
Price ($ / GB)
Enter your provider's effective $/GB for the region/path/tier.
Scenario presets
Pick a boundary-first starter so the estimate reflects the right transfer path.

Results

Estimated monthly cost
$225.00
Egress
2,500 GB
Price
$0.09 / GB
Decision-support snapshot
Scenario boundary: Custom transfer boundary
Baseline monthly spend: $225.00
Peak monthly spend: Peak scenario disabled
Marginal peak impact: Enable peak scenario to estimate delta
Next action:
  • Validate the transfer boundary and effective rate before changing architecture assumptions.
  • Capture one baseline and one peak month to avoid hidden spike surprises.

When to use this calculator first

Start here when your team needs a planning number now and already knows the transfer boundary being modeled. This page helps you turn traffic assumptions into a budget range quickly, then decide the highest-value follow-up.

  • You can name the boundary clearly (public internet, CDN origin fill, cross-region replication, or DR sync).
  • You need baseline and peak monthly spend for a launch, incident, or seasonal decision.
  • You want to compare optimization levers before changing architecture or contracts.

What this estimate still misses

This tool is intentionally lightweight so teams can model quickly. Before final budget sign-off, reconcile the estimate against billing exports and provider rules.

  • Credits, committed-use discounts, free tiers, and contracted rates.
  • Non-bandwidth charges such as requests, connection-minute fees, and service-specific pricing.
  • Operational behavior changes such as retry storms, regional failover policies, or unplanned cache churn.

Next step after your estimate

Once you have a baseline and peak estimate, route to the next page by intent. This keeps the workflow fast and prevents over-analysis on the calculator page.

Clarify boundary and rate assumptions
Use the egress guide when you need confidence that the modeled path and rate logic are correct.
Map estimate to AWS network bill lines
Use the AWS network costs guide to align this estimate with line-item billing surfaces.
Model CDN-origin and edge delivery next
Use when cache behavior likely drives your peak-month transfer costs.
Model replication and DR transfer separately
Use when cross-region traffic needs its own baseline and peak estimate.

Example scenario

  • Public API outbound transfer: 3,200 GB/month at $0.085/GB gives a baseline estimate near $272/month.
  • CDN origin fill traffic: tiered pricing with cache-miss spikes can double monthly transfer spend during launch windows.
  • Cross-region replication: model a stable month and a DR test month separately before committing a budget.

Included

  • Baseline and peak monthly transfer estimates for one selected boundary.
  • Scenario presets for internet egress, CDN origin fill, cross-region replication, and launch bursts.
  • Tiered pricing support with per-tier breakdown.
  • Mbps-to-GB estimate helpers for teams that start from throughput metrics.
  • Decision-support summary with marginal peak impact and next actions.

Not included

  • Provider-specific free allowances, enterprise discounts, and billing credits.
  • Per-request, per-connection, and other non-bandwidth service fees.
  • Business-side demand assumptions (marketing events, contract changes, product rollout behavior).

How we calculate

  • Model one transfer boundary per run (internet egress, CDN origin fill, cross-region replication, or another defined path).
  • Monthly cost = GB x effective $/GB, or the sum of tiers when tiered mode is enabled.
  • Turn on peak mode to compare baseline spend against launch or incident traffic.
  • Repeat for each major path and combine line items in your final budget sheet.

FAQ

When should I use this calculator before reading the full guide?
Use this page first when you already know the transfer boundary and want a fast baseline-vs-peak estimate to support a planning decision.
Can I model multiple boundaries in one run?
You should not. Run one boundary at a time (for example internet egress vs cross-region replication) and sum the results later.
Why keep a peak scenario if average traffic looks stable?
Peak months are where budgets fail. The marginal peak impact highlights how much extra transfer cost appears during launches, retries, or failover windows.
What should I do after the first estimate?
Use the egress guide for boundary validation, then map AWS network charges and refine adjacent calculators like CDN origin and cross-region transfer.

Related tools

Validate boundary assumptions (guide) Map AWS network line items (guide) Estimate CDN origin + edge bandwidth Estimate replication and DR transfer Translate API payload to transfer GB

Related guides

API Gateway vs ALB vs CloudFront cost: what to compare (requests, transfer, add-ons)
A practical cost comparison of API Gateway, Application Load Balancer (ALB), and CloudFront. Compare request pricing, data transfer, caching impact, WAF, logs, and the hidden line items that change the answer.
CloudFront cache hit rate: how it changes origin egress cost
Cache hit rate strongly influences origin requests and origin egress (cache fill). Learn a simple model, what breaks hit rate, and the practical levers to improve it safely.
Azure Front Door pricing: model requests, bandwidth, and origin traffic
A practical Azure Front Door cost model: edge bandwidth, request volume, logging, and origin traffic (cache fill). Includes a checklist to validate hit rate and avoid double-counting egress.
CDN Cost Guide: Diagnose the Bill, Choose the Right Calculator, and Validate the Model
Use this CDN guide to diagnose which CDN line item moved first, route to the right calculator, and keep bandwidth, request fees, and origin egress as separate cost surfaces.
Cloud CDN pricing (GCP): bandwidth, requests, and origin egress (cache fill)
A practical Cloud CDN cost model: edge bandwidth, request volume, and origin egress (cache fill). Includes validation steps for hit rate by path, heavy-tail endpoints, and purge/deploy events that reduce hit rate.
CloudFront pricing: estimate bandwidth and request costs (without hardcoding prices)
A practical way to estimate CloudFront-style CDN costs using your own bandwidth ($/GB) and request-fee ($ per 10k/1M) assumptions, plus common pitfalls like tiered pricing and origin egress.

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