ECS Service Connect adds zone-aware routing by default
Amazon ECS Service Connect now automatically prefers same-AZ endpoints, reducing cross-zone data transfer costs without requiring code changes.
Does ECS Service Connect now route traffic within the same availability zone automatically?
Yes. As of July 23, 2026, ECS Service Connect preferentially routes service-to-service requests to endpoints in the same availability zone as the originating task. The feature is on by default for all new and existing services and carries no additional cost.
What problem does this solve?
When teams distribute ECS workloads across multiple availability zones for fault tolerance, inter-service calls frequently cross AZ boundaries. That cross-zone traffic incurs data transfer charges and adds latency, forcing architects to choose between resilience and cost. Zone-aware routing removes that tradeoff by keeping traffic local whenever possible.
The routing logic is dynamic, not static. As services scale up or down, ECS Service Connect adjusts traffic weights to maintain a balanced load across target service instances, so one AZ does not absorb a disproportionate share of requests simply because it happens to be local.
What happens when local endpoints are unhealthy?
The feature includes an automatic fallback mechanism. If endpoints in the originating task's AZ become unhealthy or drop below a capacity threshold, Service Connect redistributes traffic across healthy AZs. That redistribution is designed to avoid overloading any single zone, preserving availability without manual intervention.
Do existing services need to be redeployed?
Existing services require a one-time redeployment to activate the new routing behavior. No application code changes and no additional infrastructure are needed beyond that deployment. New services pick up zone-aware routing automatically.
How can teams validate the change is working?
AWS recommends using Amazon VPC Flow Logs with AZ metadata to observe cross-AZ traffic patterns before and after enabling the feature. Comparing those patterns provides a concrete measure of how much traffic has shifted to same-zone paths.
Availability and pricing
| Attribute | Detail |
|---|---|
| Feature | Zone-aware routing for ECS Service Connect |
| Default state | Enabled for all new and existing services |
| Existing service action required | One-time redeployment |
| Code or infrastructure changes | None |
| Additional cost | None |
| Regions | All AWS commercial regions and AWS GovCloud (US) where ECS Service Connect is supported |
Why this matters for service mesh architecture
Service Connect, ECS's built-in service discovery and communication layer, has previously handled health-based routing and load balancing. Zone-aware routing extends that intelligence to the topology of the underlying infrastructure, giving teams a cost and latency benefit that was previously only achievable through custom routing logic or third-party service mesh tooling.
For workloads with high call volumes between microservices, the reduction in cross-AZ data transfer can translate into meaningful cost savings at scale, particularly in regions where inter-AZ transfer fees apply. Because the feature requires no application-level changes, adoption is largely an operational step rather than a development effort.