AWS Outposts rack now supports intra-VPC communication across multiple Outposts
You can now add routes in your AWS Outposts rack subnet route table to forward traffic between subnets within the same VPC spanning across disparate Outposts, using the Outpost local gateways (LGW). The LGW enables connectivity between your Outpost subnets and your on-premises network. With this enhancement, you can establish intra-VPC instance-to-instance IP communication across Outposts through your on-premise network, via direct VPC routing (DVR).
You can now add routes in your AWS Outposts rack subnet route table to forward traffic between subnets within the same VPC spanning across disparate Outposts, using the Outpost local gateways (LGW). The LGW enables connectivity between your Outpost subnets and your on-premises network. With this enhancement, you can establish intra-VPC instance-to-instance IP communication across Outposts through your on-premise network, via direct VPC routing (DVR).
Until today, in order to establish communication between instances across Outposts, you needed to create subnets in different VPCs or use separate IP address range/CIDR, known as a CoIP pool. With this launch, you can leverage single VPC architecture for communications between instances across Outposts and utilize DVR, removing complexity of managing separate VPC and CoIP pools. You can use this feature to build multi-AZ like architectures for your on-premise applications running on Outposts racks that are anchored to two different AZs.
Intra-VPC communication across multiple Outposts is available in all AWS Regions where Outposts rack is available. Your existing Outposts racks may require an update to enable support for intra-VPC communication across multiple Outposts. If this feature does not work for you, please contact AWS Support.
To learn more, check out this blog post, the Outposts rack feature page, and the Outposts documentation.