Networking calculators

Model networking costs by making boundaries explicit (internet, cross-region, cross-AZ) and using effective rates.

All calculators Guide: networking costs Guide: egress costs Methodology

Start with boundaries

  • Internet egress (to the public internet)
  • Cross-region transfer
  • Cross-AZ / intra-region transfer
  • CDN edge bandwidth vs origin egress (cache fill)

Common mistakes

  • Using CDN bandwidth as a proxy for origin egress (double-counting or missing cache fill).
  • Mixing GB vs GiB or applying a single $/GB across multiple transfer paths.
  • Ignoring retries/timeouts that multiply requests and bytes during incidents.

Quick workflow (get a defensible estimate)

  1. Measure GB/month for each boundary (internet, cross-region, cross-AZ) from logs/metrics if possible.
  2. Pick an effective $/GB for each boundary (region and tier matter).
  3. Model a baseline month and a peak month (incidents and launches amplify traffic).

What to validate in billing

  • Which line item is the real driver (egress, inter-AZ, inter-region, NAT processed GB, endpoint-hours).
  • Whether your estimate matches a representative month (then adjust assumptions, not the math).
  • Whether caches and locality behave as intended (cache hit rate, AZ affinity, regional routing).

How to get your inputs

  • Internet egress: CDN or load balancer bytes out, or billing usage types.
  • Cross-AZ: VPC flow logs summaries or provider transfer metrics.
  • Cross-region: replication/DR logs or billing export usage types.
  • Effective rates: use blended $/GB for each boundary, not a single rate.
18 networking tools
CDN Cost Calculator
Estimate total CDN cost from bandwidth and request pricing.
CDN Origin Egress Calculator
Estimate origin egress and requests from CDN edge volume and cache hit rate.
CloudFront Cost Calculator
Estimate CDN cost for CloudFront-style pricing assumptions.
VPC Data Transfer Cost Calculator
Estimate data transfer spend from GB/month and $/GB assumptions.
AWS NAT Gateway Cost Calculator
Estimate NAT gateway hourly + per-GB processed costs from your inputs.
AWS Load Balancer Cost Calculator (ALB/NLB)
Estimate load balancer fixed + LCU/NLCU usage costs from your inputs.
AWS API Gateway Cost Calculator
Estimate API Gateway-style cost from request volume plus response transfer assumptions.
API Gateway Request Volume Estimator
Estimate API Gateway request volume from baseline RPS and peak traffic windows.
AWS WAF Cost Calculator
Estimate WAF-style costs from Web ACLs, rules, and request volume.
WAF Request Volume Estimator
Estimate evaluated WAF requests from baseline traffic and attack spikes.
AWS Route 53 Cost Calculator
Estimate DNS costs from hosted zones, query volume, and health checks.
Data Egress Cost Calculator
Estimate monthly egress spend from GB transferred and $/GB pricing.
CDN Bandwidth Cost Calculator
Estimate monthly CDN bandwidth cost from GB transferred and $/GB pricing.
Cross-region Transfer Cost Calculator
Estimate monthly cross-region transfer cost from GB transferred and $/GB pricing.
API Response Size Transfer Calculator
Estimate monthly transfer from request volume and average response size.
CDN Request Cost Calculator
Estimate CDN request fees from monthly requests and $ per 10k/1M pricing.
API Request Cost Calculator
Estimate request-based charges from monthly requests and $ per million.
AWS ALB LCU / NLB NLCU Calculator
Estimate LCU/NLCU capacity units per hour from connections and bytes processed.

Result interpretation

  • If egress dominates, check CDN cache hit rate and origin egress separately.
  • If inter-AZ transfer dominates, review service locality and load balancer routing.
  • If NAT or endpoint costs dominate, validate processed GB and endpoint-hours assumptions.
  • Use a peak scenario for incident months; retries and timeouts change network spend fast.

Scenario planning

  • Baseline: typical egress, inter-AZ, and cross-region volumes.
  • Peak: 2x-4x traffic and higher retry rates during incidents.
  • Cache shifts: model a lower cache hit rate for launch weeks.
  • Route changes: re-evaluate when you add regions or new endpoints.

Validate after changes

  • Verify boundary splits (internet, cross-AZ, cross-region) in billing exports.
  • Check cache hit rates and origin egress after CDN changes.
  • Review flow logs or transfer metrics after routing updates.
Advertisement