Vpc Peering Connection Route Table

Your vpc has an implicit router and you use route tables to control where network traffic is directed.

Vpc peering connection route table. Confirm its status is active. The subnet a route table in vpc p points to the relevant peering connection to access the full cidr block of vpc m. 172 31 0 0 16 or to a.

If you modify a vpc peering connection to enable communication between instances in your vpc and an ec2 classic instance that s linked to the peer vpc a static route is automatically added to your route tables with a destination of 10 0 0 0 8 and a target of local. Open the amazon vpc console. From the green account s vpc s routing table add a new route with the destination of 10 2 0 0 16 select peering connection as the target and it should resolve to the peering connection resource that we created then select save.

To add an ipv6 route for a vpc peering connection. In the confirmation dialog choose yes accept. In the navigation pane choose route tables and select the route table that s associated with your subnet.

We do this by adding a route to our routing table. Pcx 00197469 then verify the value e g. Identify the route objects routes with the vpcpeeringconnectionid attribute set to the selected vpc peering connection id i e.

Select the vpc peering connection that you ve created and choose actions accept request. You can explicitly associate a subnet with a particular route table. Vpc peering network connectivity failures are typically the result of incorrect or missing route tables or firewall rules.

If the destinationcidrblock values are set to the entire ipv4 cidr blocks of the peer vpc e g. In the navigation pane choose peering connections and choose your peering connection. Choose the route tables view and confirm that they have routes to.