Zero Extra Cost: ECS Now Auto-Saves on Cross-AZ Traffic
Hey, Shii-chan here!
AWS What's New
aws.amazon.com
I found a great update today for engineers running ECS — and it comes at no extra cost!
What was announced?
According to AWS What's New, Amazon ECS Service Connect now supports Zone-Aware routing. It prioritizes routing service-to-service traffic to endpoints within the same Availability Zone (AZ) as the originating task, aiming to cut cross-AZ data transfer costs and latency.
The story so far
Until now, spreading an application across multiple AZs for resiliency often meant service-to-service traffic crossed zone boundaries, and cross-AZ data transfer costs piled up. As the announcement puts it, this forced a trade-off between cost and resilience.
What changes
Zone-Aware routing resolves that cost-versus-resilience trade-off.
- Requests are preferentially routed to endpoints in the same AZ as the originating task
- Traffic weights adjust dynamically as endpoints scale
- If local endpoints become unhealthy or fall below capacity, traffic automatically redistributes across healthy AZs
In short, it keeps traffic within the same AZ under normal conditions to save cost and latency, while still failing over gracefully to other AZs when needed.
Dive Deep
The rollout is friction-free — no extra infrastructure or application code changes required.
- Enablement: on by default for new services; existing services just need a one-time redeployment
- Pricing: no additional cost
- Region availability: all AWS commercial Regions and AWS GovCloud (US) Regions where ECS Service Connect is supported
- Monitoring: use Amazon VPC Flow Logs with AZ metadata to check cross-AZ traffic patterns and validate routing effectiveness
You get the benefit without writing any special configuration, and existing services only need a single redeployment — a low bar for adoption.
Wrap-up
- ECS Service Connect now supports Zone-Aware routing, prioritizing same-AZ traffic
- It cuts cross-AZ data transfer costs and latency at no extra cost and with no code changes
- New services get it by default, existing services need one redeployment, and VPC Flow Logs let you verify the effect
If you're running ECS across multiple AZs and cross-AZ traffic costs have been bugging you, this is worth trying right away!
