VPC Peering Overview
Introduction
VPC Peering is a service that lets you connect two Virtual Private Clouds (VPCs) within the same Region so resources such as VMs, databases, and Load Balancers can communicate privately over internal IP without traversing the public internet.
VPC Peering connects VPCs through FPT Cloud's internal infrastructure, ensuring that traffic does not have to cross the public internet — strengthening overall security. The service also delivers high performance with low latency and large bandwidth between VPCs, supporting demanding internal data transfer workloads. All peering connections and route tables can be managed centrally from the FPT Cloud Portal, making it easy to create, update, or delete configurations in a single, consistent place.
What to check before creating a VPC Peering
-
No overlapping CIDR: The two VPCs participating in a VPC Peering must use different CIDR ranges. If CIDR blocks overlap, the system cannot route traffic correctly between the VPCs.
-
Check VPC status: Make sure both the Requester VPC and the Accepter VPC are in an enabled state before creating a Peering Connection.
-
Check service quota: Verify that there is still available VPC Peering Connection quota to avoid errors during creation.
-
Configure the Route Table: After the Peering Connection is created, you must update the Route Table to route traffic between the two VPCs through the Peering Connection.
-
Check Security Group and Firewall rules: Security Groups or Firewall rules must allow appropriate inbound/outbound traffic between the two VPCs so resources can communicate successfully.
-
Check the connectivity scope: Currently VPC Peering only supports connections between VPCs within the same Region.