Frequently Asked Questions

What is VPC Peering?

VPC Peering is a service that lets you connect two or more Virtual Private Clouds (VPCs) through an internal private network so resources across the VPCs can communicate directly as if they were on the same network. The connection does not traverse the public internet, ensuring strong security, low latency, and consistent performance for inter-VPC data exchange.

How does VPC Peering work?

VPC Peering works by establishing a private network connection between two or more VPCs, allowing resources inside those VPCs to communicate directly over the internal network without going through the internet. Once the Peering Connection is established and Route Tables are configured appropriately, traffic flows over the peering link to maintain stable, low-latency, secure performance between VPCs.

What is the purpose of using VPC Peering?

The main purpose of VPC Peering is to let VPCs connect and communicate directly over a private internal network, enabling resource sharing and secure data transfer. The service is typically used to connect application environments, databases, internal services, or systems across multiple VPCs while preserving security and avoiding the public internet.

After creating a VPC Peering, the two VPCs still cannot ping each other — what should I do?

Re-check the Route Table, the Security Group / Firewall rules, and the status of the Peering Connection. Also ensure CIDR ranges across the VPCs do not overlap, and that the VM / Instance configuration allows ICMP or the required traffic types so the two VPCs can communicate.

How do I check service permissions on the FPT Cloud Portal?

Service permissions are enabled per VPC. When you open the service — if you do not yet have access, the portal displays a message that the service has not been enabled. In that case, please contact FPT Cloud to request access.