Cloud Enterprise Network (CEN) creates private connections between VPCs, enabling cross-VPC resource sharing over internal networks.
Connect two VPCs in the same region through CEN. The same approach scales to additional VPCs.
Example scenario
This example assumes two VPCs in the China (Hangzhou) region:
-
VPC1
-
IPv4 CIDR block: 10.0.0.0/16
-
vSwitch 1 in Zone J, CIDR block 10.0.0.0/24
-
vSwitch 2 in Zone K, CIDR block 10.0.1.0/24 (two zones for high availability)
-
ECS1 address: 10.0.0.1 (used to test connectivity)
-
-
VPC2
-
IPv4 CIDR block: 172.16.0.0/16
-
vSwitch 1 in Zone J, CIDR block 172.16.0.0/24
-
vSwitch 2 in Zone K, CIDR block 172.16.1.0/24
-
ECS2 address: 172.16.0.1
-
Connecting both VPCs to a CEN transit router enables private communication between them.
Ensure the CIDR blocks of the VPCs you want to connect do not overlap.
Procedure
Step 1: Create a CEN instance
|
|
|
|
|
|
Step 2: Create a transit router
|
|
|
|
|
|
|
|
Step 3: Connect VPCs to the transit router
|
|
|
|
|
|
|
|
|
|
Step 4: Test the connection
Ensure the security group rules for both ECS instances allow traffic between them. View security group rules and Add security group rules.
Log on to ECS1 and run ping to test connectivity to ECS2:
ping 172.16.0.1

A successful ping confirms that VPC1 and VPC2 are connected.
Next steps
-
View the network topology of your CEN instance.
-
Use flow logs to analyze transit router traffic.











