Inter region data transfer is one of the largest hidden costs in a multi region AWS estate. The rate matrix is asymmetric. The buyer side that maps the flow lines before the architecture is set cuts the bill by twenty to forty percent.
AWS charges for data transfer between every commercial region. The rate sits between one and two cents per gigabyte for most pairs. The rate matrix is asymmetric and some pairs cost twice the average rate.
Multi region architectures often cross the matrix at scale. Without flow line mapping the inter region bill becomes the largest hidden line item in the AWS estate.
AWS publishes a rate matrix for inter region transfer. The rate is per gigabyte. The matrix carries asymmetric pricing where some region pairs cost more than others.
Most commercial region pairs sit between one and two cents per gigabyte. The rate is invoiced by the source region. The destination region does not pay an ingress charge.
A small set of region pairs sit above the typical rate. Transfers to and from South America, the Middle East, and parts of Asia can carry up to nine cents per gigabyte.
Cross availability zone traffic inside one region is metered separately at one cent per gigabyte each way. Multi AZ architectures pay this rate at scale.
| Pair | Source rate | Destination rate | Notes |
|---|---|---|---|
| us east 1 to us west 2 | $0.02 per GB | Free | Standard pair |
| us east 1 to eu west 1 | $0.02 per GB | Free | Atlantic pair |
| us east 1 to ap south 1 | $0.08 per GB | Free | Higher band pair |
| us east 1 to me central 1 | $0.085 per GB | Free | Middle East pair |
| Cross AZ intra region | $0.01 per GB | $0.01 per GB | Bi directional charge |
Most multi region AWS estates carry a small set of flow patterns. The buyer side that maps the flow lines holds the cost optimization plan.
A primary region replicates data to a secondary region for disaster recovery. The replication runs at steady state. The replicate is often the largest single inter region flow.
A global database keeps read replicas in distant regions. Each write to the primary fan outs as a transfer to every read replica region. The pattern compounds the rate matrix.
An application in region A calls a service in region B. The request and response both pay the source rate of their respective region. The call adds latency and cost.
Three patterns drive most of the unexpected inter region transfer bills. Each pattern is invisible to the application team and visible only on the AWS bill.
Centralized logging from multiple regions to a single CloudWatch Logs destination crosses the rate matrix. High verbosity application logs can move terabytes a month.
Cross region backup of EBS, RDS, and S3 carries the inter region rate. Daily backup of a multi terabyte database is a recurring transfer cost.
ECR image pulls from a region that does not host a regional cache pay the inter region rate. CI/CD pipelines that pull on every build compound the cost.
AWS offers commitment based discounts on data transfer through the Private Pricing Agreement and the Enterprise Discount Program. The lever is not used as often as the compute commitment lever.
The Enterprise Discount Program covers most AWS services including data transfer. The customer commits to a multi year spend and receives a percentage discount across the program.
A Private Pricing Agreement can negotiate the data transfer rate directly. The achieved rate sits below the list rate by ten to forty percent depending on volume.
The deepest discounts apply to single region or region cluster commitments. A globally diversified estate carries a thinner discount band.
Four FinOps moves cut the transfer bill before any architecture change. Each move can be run inside a quarter.
Aggregate logs in the source region first, then ship a compressed digest to the central region. The move cuts log shipping cost by sixty to ninety percent.
Deploy an ECR cache in every region that runs CI/CD pipelines. The cache holds container images locally and removes the inter region pull cost.
Cut the cross region backup retention to match the recovery objective. Most estates over retain by a factor of two or three.
Identify the top five cross region service calls. Move at least one side of each call to remove the cross region hop.
Architecture decisions made at design time govern the inter region transfer bill for the life of the workload. Three patterns make the largest difference.
Active passive disaster recovery carries a one way replicate. Active active carries bi directional traffic at every write. The cost ratio is typically two to three times higher for active active.
A region cluster pattern groups workloads into two or three regions. A region sprawl pattern distributes workloads across many regions. Region cluster cuts the matrix surface area.
Edge first patterns push more processing to CloudFront, Lambda Edge, and regional Lambda. Core first patterns pull traffic back to a primary region. Edge first cuts the inter region matrix exposure.
The checklist takes the buyer from the AWS bill review to the executed FinOps plan. The earlier the work starts, the wider the option set.
AWS charges between one and nine cents per gigabyte for inter region data transfer depending on the source destination pair. Most US to US and US to EU pairs sit at two cents per gigabyte. Transfers involving South America, the Middle East, and parts of Asia can carry rates up to nine cents per gigabyte from the source region.
No. The AWS rate matrix is asymmetric. The source region pays the egress rate and the destination region does not pay an ingress charge. Some pairs cost more than others and some pairs cost the same in either direction while others differ. The buyer side reads the matrix per pair before sizing the bill.
No. VPC Peering between regions uses the same inter region data transfer rate as standard egress. The peering relationship is a routing convenience and does not change the rate. Customers often assume peering offers a discount and the assumption drives unexpected bills at scale.
Direct Connect between an on premise data center and AWS uses a Direct Connect data transfer out rate that sits below the standard egress rate. Direct Connect does not change the rate between AWS regions inside AWS. Inter region transfer continues to follow the standard matrix even with Direct Connect at one end of the flow.
Yes. A Private Pricing Agreement can negotiate the inter region transfer rate directly. The achieved rate typically sits between ten and forty percent below the list rate depending on the volume of inter region traffic. The Enterprise Discount Program covers data transfer at the program discount level but does not target the inter region rate specifically.
AWS charges one cent per gigabyte each way for traffic that crosses availability zones inside a single region. The charge applies in both directions, which means a one way one gigabyte transfer between AZs costs two cents in total. Multi AZ architectures pay this rate continuously and the cost compounds at scale.
Cross region log shipping to CloudWatch Logs, cross region backup of EBS and RDS, cross region container image pulls from ECR, global database read replica fan out, and chatty service calls between application tiers all drive high inter region transfer bills. Each of these is invisible to the application team and visible only on the AWS bill.
Redress runs the inter region bill review, the flow mapping, the architecture review, the four FinOps moves, and the PPA negotiation inside the Vendor Shield subscription and the Renewal Program. The work includes the EDP scope review and the contract negotiation against the prior commitment band.
Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, the AWS service line, and the Software Spend Assessment.
Read the EDP negotiation playbook, the cost optimization service, the AWS Services hub, the benchmarking service, and the Benchmark Program.
The companion playbook covers the AWS Enterprise Discount Program commitment math, the partner channel route, and the buyer side moves that recover spend without re platforming.
Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.
Open the playbook in your browser. Corporate email only.
Open the Paper →Inter region transfer is a tax on the architecture. The buyer side that maps the flow lines before the architecture is set pays the tax once. The team that ships first and reads the bill later pays it forever.
We have run sixty three AWS multi region cost reviews with median twenty eight percent cut on the transfer bill. Every engagement starts with one conversation.
Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
