VPC Peering Overview
Introduction
VPC Peering connects two VPCs in the same Region or in two different Regions, so VMs, databases and Load Balancers can talk over private IP addresses without crossing the internet. Use it when applications and data in separate VPCs need to exchange traffic securely.
Traffic stays on the FPT Cloud internal infrastructure, which gives you low latency and high bandwidth between VPCs. You manage peering connections and Route Tables in one place on the FPT Cloud Portal.
Key terms
| Term | Definition |
|---|---|
| VPC Peering connection | A private link between two VPCs that lets their resources communicate over internal IP addresses. |
| VPC Gateway | The gateway attached to a VPC. You need one before you can create a VPC Peering connection. |
| VPC Requester | The VPC that starts the peering request. |
| VPC Accepter | The VPC that receives the peering request. |
| Route Table | Defines where traffic in a VPC goes, based on the destination address. |
Before you create a VPC Peering connection
- The two VPCs must not have overlapping CIDR ranges. Overlapping ranges prevent correct routing.
- Both the VPC Requester and the VPC Accepter must be enabled.
- You must have VPC Peering connection Quota available.
- Security Group and Firewall rules must allow the inbound and outbound traffic you need between the two VPCs.
- After the connection is active, update the Route Table in both VPCs to route traffic through it.
note
Whether a request connects immediately or waits for approval depends on your permissions and on where the two VPCs sit. See How VPC Peering approval works.