Vpc Peering Explained

It is a special link for carrying l2 traffic between the vpc peer switches when there is a link failure.

Vpc peering explained. Once the peer connectivity is established resources in one vpc can access resources in the other. Aws vpc peering connections can be used to route traffic from one vpc to another vpc network or to provide access to resources of one network to another. This allows one vpc to communicate with another vpc.

For vpc you would likely connect the two switches together by 10 g links preferably one on each of two different line cards for robustness and declaring that link to be a port channel and a vpc peer link. Traffic stays within google s network and doesn t traverse the public. Vpc peering allows you to request a peering connection with another vpc in your own account or within another amazon account and then route between those vpcs by simply adding routes to the.

A vpc peering is a 1 to 1 peering and many not be hub and spoke or mesh topology. Additionally vpcs with overlapping cidrs cannot be paired. Normally it should get little use.

Once done your vpc s will behave as if they are on the exact same network. In other words vpc a can connect to b and c in the above diagram but c cannot communicate with b unless directly paired. A vpc can have multiple peering connections to other vpcs but transitive peering is not supported.

However only vpcs in the same region can communicate with each other. Let me start by explaining what vpc peering is at a high level. An amazon vpc peering allows to vpcs regardless of account talk to each other.

This achieved with something called a direct network route and a private ip address. Vpc peering allows you to connect two or more vpcs together using ipv4 or ipv6 as if they were a part of the same network. Aws vpc peering is a functionality that enables two private networks to communicate with each other by building fast and reliable connections.