Data transfer is the AWS line item everyone underestimates

# architecture# aws# infrastructure
Data transfer is the AWS line item everyone underestimatesVlad Z

Data transfer costs are the most consistently underestimated line item in AWS They're not the...

Data transfer costs are the most consistently underestimated line item in AWS

They're not the biggest cost in most accounts. But they're the one that grows the fastest as systems scale, the one nobody was thinking about when the architecture was designed, and the one that's hardest to reduce without touching the architecture itself

That's what makes it hard high-impact

The charges come from several directions

Traffic leaving AWS to the internet is charged per GB. Traffic between regions is charged per GB in both directions. Traffic between availability zones within the same region is charged per GB. Only traffic within the same AZ between the same service type is free

In a microservices architecture where services are spread across AZs, every API call can generate billable transfer. Not much per call. At thousands of calls per second it adds up to a significant monthly line item that wasn't in anyone's cost model

The diagnosis starts with the data transfer line in your bill broken down by usage type. Most people have never looked at this breakdown. It usually contains at least one surprise

The fixes depend on what you find

Services talking across AZs: consolidate them or use a service mesh that routes traffic locally. Services unnecessarily calling APIs in other regions: move the data closer or cache aggressively. Internet egress higher than expected: check if data is being transferred to clients in an uncompressed format, check if assets are being served directly from S3 instead of through CloudFront

CloudFront is worth a specific mention. Serving content through CloudFront instead of directly from origin reduces egress costs because AWS prices CloudFront egress lower than direct S3 or EC2 egress, and CDN caching reduces the total volume of data transferred from origin

The architecture changes required to fix data transfer problems are real work

But the savings compound with every point of traffic growth

The team that fixes this today pays less at 2x traffic, 5x traffic, 10x traffic

The team that doesn't pays more every month, forever