Cross-account canary routing with Amazon VPC Lattice and Amazon API Gateway
Networking & Content Delivery Blog
This article demonstrates how to implement cross-account canary routing for microservices migrations using Amazon API Gateway and VPC Lattice for weighted traffic splitting with quick rollback.
- Combine API Gateway canary releases with VPC Lattice for per-request traffic splitting across AWS accounts
- Use a shared VPC Lattice service network to enable secure cross-account service connectivity without VPC peering
- Deploy a forwarder Lambda function in a VPC-attached fronting account to bridge API Gateway and Lattice services
- Control canary percentages at the API Gateway stage level for instant rollback and progressive traffic shifting
- Scale to multiple services by deploying one API Gateway per microservice with independent canary settings
- Eliminate custom routing code while maintaining fine-grained traffic control during monolith-to-microservices migration
This pattern enables organizations to safely migrate monolithic applications to microservices across multiple AWS accounts with precise traffic control and minimal operational complexity.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
2026
2026
2026
2025
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.