VPC Peering
AWS VPC Peering is a powerful feature that allows for connecting two Virtual Private
A VPC peering connection is a networking connection between two VPC that enables you to route traffic between them using private IPv4 address or IPv6 address.
It enables private communication between resources in peered VPC. Instance in either VPC can communicate with each other as if they are within the same network.
You can create AVPC peering connection between your own VPC, or with a VPC in another AWS account. The VPC can be in a different region or account.
Transitive peering is not allowed that is if there are three VPCs in such a way that VPC A and VPC B are peered and VPC B and VPC C are peered. That doesn't mean VPC A can communicate with VPC C
Points to remember
- Connect multiple VPC using a direct routing connection
- Resources act as they're in a same network
- Works within and across accounts and regions
- No hardware or Single point failure
- 50 (soft limit), Max limit is 125
- To establish relationship the owners send request
- Subnets should not overlap
- VPC peering name always start with
pcx-XXXXXXX
Implementation
Step 1: Go to console ➡️ VPC ➡️ VPC ➡️ VPC Peering ➡️ Create Peering Connection
Step 2: Configure the following:
- Name
- Requester VPC
- Acceptor VPC (either in same account or different)
Step 3: Click on create
Step 4: Accept the request / Wait for the other user to accept the request
Step 5: Update the RT in the following manner
VPC Sharing
- Sharing VPC resources with our account within your organization using VPC Peering.
- Multiple projects or account can leverage single VPC to securely connect and communicate with each other using internal IP address
- It established a hierarchical relationship
- One project act as host and share its VPC resources with other projects (also called service project) within same Organization
- It established the centralized and scalable network architecture for multiple projects within the same organization.