VPC Peering
Learn about the usage of the VPC peering service.
We'll cover the following...
So far, we have learned that a VPC is an isolated private network that is unreachable from the public internet. Let’s assume we have two VPCs in our AWS Region: VPC A (web-app-vpc), which contains the hosted web application resources, and VPC B (license-server-vpc), which includes a license server.
Let’s say that resources in the web-app-vpc need to request a license from the license-server-vpc, but both VPCs are in separate isolated private networks. How can the private resources within these VPCs communicate with each other?
To solve this problem, we can use a service provided by AWS known as VPC peering. A VPC peering is a private and secure network connection connecting two VPCs so that the resources within the VPCs can directly communicate. Using a VPC peering connection, the traffic shared between the VPCs is transferred through the encrypted AWS private network and doesn’t go through the public internet, which ensures the connectivity is always secure.
Important points about VPC peering
A VPC peering connection is a one-to-one connection and can be established only between two VPCs.
A peering connection can be created across VPCs in the same or different AWS Regions.
A peering connection can be created between VPCs in the same or different AWS accounts.
Two VPCs can only have one peering connection at a time.
Transitive peering is not supported by VPC peering. Let’s say we have three VPCs: A, B, and C. VPC A and VPC B are ...