Price AWS egress across the tiered internet schedule plus inter-AZ and cross-region traffic in one bill.
Internet egress uses a declining tiered schedule with breakpoints at 10 TB, 50 TB and 150 TB per month, so the blended rate you actually pay is always below the headline first-tier price. Traffic that never leaves AWS is not free either: crossing an Availability Zone is billed on both the sending and receiving side, and crossing a region is billed at a higher per-GB rate. Every rate is a user-supplied list price to confirm on the AWS data transfer pricing page for your regions. Egress is the line item that scales with success rather than with capacity, and separating internet, inter-AZ and cross-region traffic shows whether the fix is a CDN, an AZ-aware topology, or a replication rethink.
Data Transfer Cost
billable GB = egress − free allowance, split across the 10 TB, 50 TB and 150 TB boundaries; inter-AZ traffic is charged twice, once per direction.
billable GB = egress − free allowance, split across the 10 TB, 50 TB and 150 TB boundaries; inter-AZ traffic is charged twice, once per direction. Internet egress uses a declining tiered schedule with breakpoints at 10 TB, 50 TB and 150 TB per month, so the blended rate you actually pay is always below the headline first-tier price. Traffic that never leaves AWS is not free either: crossing an Availability Zone is billed on both the sending and receiving side, and crossing a region is billed at a higher per-GB rate. Every rate is a user-supplied list price to confirm on the AWS data transfer pricing page for your regions.
Egress is the line item that scales with success rather than with capacity, and separating internet, inter-AZ and cross-region traffic shows whether the fix is a CDN, an AZ-aware topology, or a replication rethink.
This calculator takes 10 inputs: Internet data transfer out, Free tier allowance, Price up to 10 TB, Price for the next 40 TB, Price for the next 100 TB, Price above 150 TB, Traffic between Availability Zones, Inter-AZ price per direction, Traffic between regions, Cross-region price. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
AWS meters data transfer out of one Availability Zone and into another as two separate flows. A chatty service spread across three AZs therefore pays double the per-GB rate on every cross-zone request and response.