Company A's Beijing Branch and Company B's Beijing Branch have two VPCs in isolated Intranets. The network segment of VPC A is 10.0.0.0/8, including subnet a 10.0.0.0/24, while ECS a is created under subnet a; The network segment of VPC B is 192.168.0.0/16, including subnet b 192.168.0.0/24, while ECS b is created under subnet b. The two VPCs can be connected through a Peering, and the VPCs at both ends of the Peering use private IP to communicate with each other. The configuration process is as follows:

Step 1: Creating a Peering Instance

Log in to the [VPC] Management Console, and click Peering.
Enter the [Peering] homepage, and click Create Peering.
The [Peering Creation] pop-up window appears. Fill in the corresponding parameters according to the prompts on the page, input the name of the Peering, and select the local VPC A of the current account and the corresponding VPC B of the peer account.
Click OK. The creation of a Peering across accounts is completed after the peer account accepts the request.

Step 2: Configuring Routes

Since a local tenant does not have the rights of the peer tenant, local tenant A can only add local route information, and the destination address is the peer VPC network segment (192.168.0.0/24 ). Tenant B needs to add the peer route information which is the destination address of VPC A ( 10.0.0.0/24 ). The operation to add route information of the local tenant is the same as that of the peer tenant.

Step 3: Verification Test

After completing the above configuration, you can perform a ping testing from ECS a to ECS b to test the connectivity.

VPC Peering Connection

Peering Networking Across Accounts