ECS Can Canary Through VPC Lattice Now

If your service-to-service traffic already lives on VPC Lattice, ECS just grew a traffic shifter.

On 2 October 2026 Amazon added built-in blue/green, linear, and canary deployments for ECS services that use Lattice. That covers calls across VPCs and accounts, which is the whole point of Lattice. You pick how fast traffic moves: all at once, in equal steps, or a small percentage first. You can send test traffic before production traffic. Lifecycle hooks include Lambda and pause. CloudWatch alarms and the ECS circuit breaker can roll back. Bake time keeps the previous version warm.

Image: Amazon Web Services, Amazon ECS adds Amazon VPC Lattice support for blue/green, linear, and canary deployments, 2 October 2026.

Why this is not just another CodeDeploy checkbox

Plenty of ECS teams already do blue/green on load balancers. Lattice is the mesh for the services that never see an ALB: internal APIs, agent runtimes, the thing that calls the thing. Until this week, updating those often meant DNS tricks or a custom weighted target group. Native strategies in the ECS service config — console, CLI, SDK, or IaC — close that gap for new and existing services in every region where Lattice exists.

The architecture question is rollback. Bake time is the feature to actually configure. A canary that flips 100% the moment the first health check passes is a blue/green with extra YAML. Pair the circuit breaker with an alarm on p99 and error rate, not on CPU. If your agent fleet is the client of this service, a bad canary is a fleet-wide prompt failure, not a 502 on a browser.

Sources

Amazon Web Services, Amazon ECS adds Amazon VPC Lattice support for blue/green, linear, and canary deployments, 2 October 2026. https://aws.amazon.com/about-aws/whats-new/2026/10/amazon-ecs-vpc-lattice-blue-green-deployments/