VPC Peering Connection Overview

A VPC peering connection is a network connection between two VPCs in one region that enables you to route traffic between them using private IP addresses. ECSs in either VPC can communicate with each other just as if they were in the same region. You can create a VPC peering connection between your own VPCs, or between your VPC and another account's VPC within the same region. However, you cannot create a VPC peering connection between VPCs in different regions.

To connect to VPCs from different regions, you can use Cloud Connect.

Each account can have a maximum of 50 VPC peering connections in each region by default.

VPC peering connections between VPCs in one account: Each account can create a maximum of 50 VPC peering connections in one region.
VPC peering connections between VPCs of different accounts: Accepted VPC peering connections use the quotas of both accounts. To-be-accepted VPC peering connections only use the quotas of accounts that request the connections.
An account can create VPC peering connections with different accounts if the account has enough quota.

Notes and Constraints

If two VPCs connected by a VPC peering connection overlap with each other, there will be route conflicts and the VPC peering connection may not be usable.
After a VPC peering connection is created, the ping command can be used to check whether two VPCs can communicate with each other, but cannot be used to check whether the gateway of the peer subnet is connected.
If two VPCs overlap with each other, you can only create a VPC peering connection to enable communication between specific (non-overlapping) subnets in the VPCs. Ensure that the subnets to be peered do not overlap.
If there are three VPCs, A, B, and C, and VPC A is peered with both VPC B and VPC C, but VPC B and VPC C overlap with each other, you cannot configure routes with the same destinations for VPC A.
You cannot have more than one VPC peering connection between the same two VPCs at the same time.
VPC peering does not support transitive peering relationships. In a VPC peering connection, your VPC does not have access to any other VPCs that the peer VPC may be peered with. For example, if VPC A is peered with both VPC B and VPC C, VPC B and VPC C cannot communicate with each other through VPC A. To enable communication between them, you need to create a VPC peering connection between VPC B and VPC C.
A VPC peering connection between VPCs in different regions will not take effect.
- To enable VPCs in different regions to communicate with each other, you can use Cloud Connect. For details, see Communication Among VPCs Across Regions.
- If you need only few ECSs in different regions to communicate with each other, you can assign and bind EIPs to the ECSs.
Even if VPC 1 and VPC 2 are connected using a VPC peering connection, ECSs in VPC 2 cannot access the Internet through the EIP of VPC 1. If you want to allow the ECSs in VPC 2 to access the Internet through the EIP of VPC 1, you can use a NAT gateway or configure an SNAT server. For details, see Having an ECS Without a Public IP Address Access the Internet.
If you request a VPC peering connection with a VPC of another account, the connection takes effect only after the peer account accept the request. If you request a VPC peering connection with a VPC of your own, the system automatically accepts the request and activates the connection.
To ensure security, do not accept VPC peering connections from unknown accounts.
The owner either of a VPC in a peering connection can delete the VPC peering connection at any time. If a VPC peering connection is deleted by one of its owners, all information about this connection will also be deleted immediately, including routes added for the VPC peering connection.
After a VPC peering connection is established, the local and peer accounts must add routes to the route tables of the local and peer VPCs to enable communication between the two VPCs.
You cannot delete a VPC that has routes configured for a VPC peering connection.
A VPC peering connection can be created between VPCs in same region even if one is created on the HUAWEI CLOUD Chinese Mainland console and another on the HUAWEI CLOUD international console.

Parent topic: VPC Peering Connection

Last Article：VPC Peering Connection

Next Article：VPC Peering Connection Configuration Plans

Did you find this page helpful?

Failed to submit the feedback. Please try again later.

VPC Peering Connection Overview

Notes and Constraints

Did you find this page helpful?

Submit successfully!

Which of the following issues have you encountered?