Overview¶
Background¶
Four VPCs are created in region A on the public cloud and they need to communicate with each other.
You can create an enterprise router in region A and attach the four VPCs to the enterprise router. The enterprise router can route traffic among the VPCs so that they can communicate with each other.
![**Figure 1** Communications among VPCs in the same region](../../_images/en-us_image_0000001295153022.png)
Figure 1 Communications among VPCs in the same region¶
Note
This document describes how to use an enterprise router to quickly allow multiple VPCs in the same region to communicate with each other.
You can share an enterprise router with different accounts to attach VPCs of these accounts to the same enterprise router for communication.
Procedure¶
Figure 2 shows the procedure for using an enterprise router to allow multiple VPCs in the same region to communicate with each other.
![**Figure 2** Flowchart for connecting VPCs in the same region](../../_images/en-us_image_0000001160921916.png)
Figure 2 Flowchart for connecting VPCs in the same region¶
No. | Step | Description |
---|---|---|
1 | Plan CIDR blocks and the number of resources. | |
2 | Create one enterprise router for connecting VPCs in the same region. | |
3 | Create four VPCs and four ECSs. You can change the resource quantity and specifications as needed. If you already have these resources, skip this step. | |
4 | Attach the four VPCs to the enterprise router. | |
5 | Add routes to the route tables of the VPCs for communication with the enterprise router.
| |
6 | Log in to the ECS and run the ping command to verify the connectivity among VPCs. |