Skip to content
FinOps workspace
COST LEDGER / DECISION GUIDE

AWS data transfer costs: egress and inter-zone spend

AWS data transfer costs are best explained by the path each flow takes. A useful review identifies the source, destination and services involved, then connects charged traffic to the application that generated it.

Request a quote
Server cabinets in the mint and dark green Cost Ledger visual style
Define the workload before comparing its cost.

AWS data transfer costs: start with a traffic map

The EC2 transfer pricing section separates internet and regional traffic categories. Rates and exemptions depend on the path and service. A cloud-wide AWS bandwidth cost per GB is therefore insufficient. Build a register of charged flows and verify the current rule for each service and direction.

FlowEvidence to collectDecision to test
Internet deliveryService, destination and billed bytesCan unnecessary payload or repeated delivery be removed?
Between zonesSource and destination zone, application purposeIs the flow required by the resilience design?
Between RegionsReplication or application trafficDoes the data movement match the business requirement?
Through NATGateway placement and processed bytesWhich traffic needs this route?

Start with the AWS audit boundary and reconcile network line items to the payer bill. The EC2 cost guide covers compute dependencies, while the S3 cost guide helps identify traffic associated with object delivery. Assign each flow to an application owner before comparing changes.

Distinguish transfer from NAT processing

AWS documents separate NAT gateway hourly and data-processing charges and describes route choices that affect the bill. Check gateway placement and the destination of traffic. Any proposal to use a different route must also document security and connectivity requirements. A NAT processing reduction is not automatically the same as removing an internet transfer charge.

  • Inventory gateways and the route tables that use them.
  • Identify the service endpoints and external destinations used by each application.
  • Separate the amount processed from the amount charged as transfer.
  • Have the network owner validate the proposed route and failure behavior.

The route is part of the cost calculation. Keep a before and after network diagram with the estimate. An architecture change can move charges from one service to another, and a narrower billing view may hide that effect. The team reviewing the proposal should be able to trace a billed flow back to the application action that caused it.

Reduce unnecessary data movement first

Review repeated downloads, replication scope and application payloads with their owners. Compare the required behavior with actual movement rather than classifying all transfer as waste. Some traffic exists to meet recovery, geographic or latency requirements. State those constraints in the proposal before ranking an architecture change by expected financial benefit.

  1. Group billed traffic by source, destination and service.
  2. Link the largest unexplained lines to workload behavior and available network evidence.
  3. Test one approved route or application change against its requirements.
  4. Compare all affected service charges after the change for the same workload.

Read the cross-cloud egress review when the decision includes moving between clouds. A public list price comparison should not determine the architecture by itself. Include the engineering effort, recurring service changes and operational burden in the business case. Ask for editable calculations and a register of exceptions so your team can repeat the review as traffic patterns change.

Prepare billing exports, the current route diagram and the workload owners for a quote. Clarify which Regions and environments are included, whether investigation needs network telemetry and who approves implementation. The handover should show the source of every estimate and the traffic paths left outside the analysis.

Server cabinets in the mint and dark green Cost Ledger visual style
Trace charged data movement back to an application and an owner.

Questions before a cost review

Is all AWS traffic charged at the same rate?

No. The applicable rule depends on the service, source, destination and direction. Separate internet, regional and intermediary processing costs before estimating a change.

Related workload decisions

Continue the review with aws ec2 cost, aws s3 cost. Each guide addresses a separate decision within the same cloud cost boundary.

Get my FinOps quote