Data Transfer Costs

Inter-region, inter-AZ. Add up fast.

Overview

Cloud data-transfer pricing is the line item that surprises teams every quarter. Inter-AZ, inter-region, and internet egress all carry per-byte charges; chatty service-to-service traffic across an AZ boundary turns into a five-figure monthly cost without anyone noticing. The discipline is architecture that minimises crossings, not after-the-fact monitoring.

• Inter-AZ within a VPC. Per-byte cost on traffic that crosses AZ boundaries inside the same region. Cheap per byte, expensive at service-mesh volume.
• Inter-region. Premium per-byte rates between regions. The most expensive class for east-west traffic.
• Internet egress. Bytes leaving the cloud. Per-byte cost plus contractual minimums; CDN offload is the standard mitigation.
• Quarterly review plus per-service breakdown. Standing review catches drift; per-service attribution surfaces the chatty offenders.

The approach

Three habits keep transfer cost matched to actual need: AZ-aware design from day one, region-aware design for hot paths, and a quarterly review that catches new chatty patterns before they accumulate.

• AZ-aware service placement. Service replicas talk to local-AZ peers preferentially. Cross-AZ chat is the easiest line to cut.
• Region-aware architecture. Hot paths stay regional. Cross-region traffic only for genuinely cross-region needs.
• Internet egress optimisation. CDN offload, response compression, asset versioning. Egress drops without sacrificing user experience.
• Quarterly cost review plus documented per-service pattern. Per-service the transfer architecture; quarterly review catches drift before it becomes structural.

Why this compounds

Each correctly-designed service produces ongoing transfer-cost savings. The patterns transfer between services; new services ship with bandwidth-aware architecture instead of recreating the same chatty patterns.

• Cost efficiency. Right architecture cuts transfer bytes. The savings continue every month.
• Operational fit. Hot-path latency drops alongside the transfer cost. AZ-local traffic is also faster traffic.
• Engineering culture shifts. Cost-aware architecture replaces tribal preference. New services arrive at the right shape.
• Year-one investment, year-two habit. First architecture review is heavy lift. By year two, transfer-cost thinking is part of design review.