Outposts Rack Intra-VPC routing - AWS Outposts High Availability Design and Architecture Considerations

Outposts Rack Intra-VPC routing

AWS Outposts rack supports intra-VPC communication across multiple Outposts. Resources on two separate logical Outposts can communicate with each other by routing traffic between subnets within the same VPC spanning across them using the Outpost local gateways (LGW). With intra-VPC communication across multiple Outposts, you can override the Local Route in your Outposts subnet associated route table by adding a more specific route to the other Outposts subnet using the local LGW as the next-hop. It can provide advantages to architecting applications that requires span a VPC between two logical Outposts as Amazon ECS across two Outposts racks or Amazon EKS cluster across AWS Outposts.

Diagram showing network paths for single VPC with multiple logical Outposts

Network paths for single VPC with multiple logical Outposts

Outposts-to-Outposts traffic routing through the Region is blocked as this is an anti-pattern. Such traffic would incur egress charges in both directions and significantly higher latency than routing the traffic across the customer WAN.