Practical guide
AWS egress pricing: build a tiered monthly transfer estimate
calculate AWS data transfer out with pricing tiers. Includes a worked example, calculator scope, and practical questions.
Updated · Sources checked
How tiered egress pricing works
A tiered transfer estimate prices each eligible slice of usage at its own rate. Reaching a cheaper tier does not make the first part of the month’s traffic cheaper retroactively. The free allowance and tier scope also matter: AWS documents an aggregated internet-transfer allowance rather than a separate allowance for every application.
First distinguish transfer out to the internet from cross-Region, cross-Availability Zone, and service processing charges. Those categories can appear in the same bill but do not share one universal rate schedule.
Worked example with hypothetical tiers
Use this deliberately fictional schedule to understand the math: the first 100 GB is free, the next 1,000 GB costs $0.10 per GB, and subsequent usage costs $0.08 per GB. These are teaching inputs, not quoted AWS tier prices.
For 1,600 GB total usage, billable volume is 1,500 GB after the hypothetical allowance. The first 1,000 billable GB costs $100; the remaining 500 GB costs $40. Total modeled transfer is $140. Multiplying all 1,500 GB by $0.08 would incorrectly produce $120.
In the actual calculator, use the displayed AWS schedule and enter total eligible internet transfer rather than manually subtracting its allowance first. Double-subtracting an allowance understates cost. If another service already consumes the shared allowance, incorporate that usage into the aggregated input instead of giving this application an independent free block.
Reconcile the estimate
Record the source services and account scope used for your volume. Consistent units matter: an application’s decimal byte conversion may differ from the units of a billing export. Keep raw bytes available so you can explain discrepancies.
The tool covers its published internet-transfer tiers through 500 TB and excludes cross-zone and cross-Region traffic, China, GovCloud, and architecture-specific processing charges. A forecast beyond its supported range needs a service-specific quote or broader billing model.
Frequently asked questions
Does inbound data cancel outbound data? Do not net the two directions. Price each applicable category under its own rules.
Can I give every microservice the free allowance? No. Apply the published aggregation rules across the eligible usage scope.
Calculate your scenario
Use the data transfer cost calculator. Keep the displayed region, pricing date, billing units, and exclusions alongside your result. The arithmetic examples above illustrate usage or explicitly hypothetical rates; they are not AWS quotes.
Source
Billing structure checked against official AWS documentation on September 6, 2026.