Connecting VPCs in the Same Account

Process Description

You can create a cloud connection and load the VPCs in the same region and the same account to enable cross-VPC communications.

Connecting VPCs in the Same Account shows an example.

Figure 1 Network communications among VPCs in the same region and the same account

Figure 2 illustrates how you can enable network communications among VPCs in the same region and the same account.

Figure 2 Process for enabling network communications among VPCs

You can use either Cloud Connect or VPC Peering to enable communications among VPCs.

• If there are two VPCs in the same region, choose VPC Peering and create a VPC peering connection between the VPCs.
• If there are multiple VPCs, use Cloud Connect, regardless of if they are in the same region or different regions.

Procedure

1. Create a cloud connection.
   1. Log in to the management console.
   2. Hover on the upper left corner to display Service List and choose Networking > Cloud Connect.
   3. On the Cloud Connections page, click Create Cloud Connection.
      Figure 3 Create Cloud Connection
      
   4. Configure the parameters based on Table 1.

      Table 1 Parameters required for creating a cloud connection

      Parameter	Description
      Name	Specifies the cloud connection name. The name can contain 1 to 64 characters, including letters, digits, underscores (_), hyphens (-), and periods (.).
      Enterprise Project	Provides a cloud resource management mode, in which cloud resources and members are centrally managed by project.
      Scenario	VPC: VPCs or virtual gateways can use this cloud connection.
      Tag	Identifies the cloud connection. A tag consists of a key and a value. You can add 10 tags to a cloud connection. Tag keys and values must meet the requirements listed in Table 2. NOTE: If a predefined tag has been created on Tag Management Service (TMS), you can directly select the corresponding tag key and value. For details about predefined tags, see Predefined Tags.
      Description	Provides supplementary information about the cloud connection. The description can contain a maximum of 255 characters.

      Table 2 Tag key and value requirements

      Parameter	Requirements
      Key	Cannot be left blank. Must be unique for each resource. Can contain a maximum of 36 characters. Can contain only letters, digits, hyphens, and underscores.
      Value	Can be left blank. Can contain a maximum of 43 characters. Can contain only letters, digits, period, hyphens, and underscores.

   5. Click OK.

2. Load network instances.

   Load the VPCs that need to communicate with each other to the cloud connection.

   1. In the cloud connection list, locate the cloud connection and click its name.
   2. Click Network Instances.
   3. Click Load Network Instance.
   4. Select the VPC you want to load.

      Configure other parameters based on Table 3 and then click OK.

      Figure 4 Loading a VPC
      

      Table 3 Parameters required for loading network instances to a cloud connection

      Parameter	Description
      Account	Specifies whether the network instances are in the current account or in another account.
      Region	Specifies the region where the VPC you want to connect is located.
      Instance Type	Specifies the type of the network instance. Two options are available, VPC and Virtual gateway.
      VPC	Specifies the VPC you want to load to the cloud connection. This parameter is mandatory if you have set Instance Type to VPC.
      VPC CIDR Block	Specifies the subnets of the VPC you want to load and the custom CIDR blocks. If you have set Instance Type to VPC, configure the following two parameters: Subnet: Select one or all subnets of the VPC. Other CIDR Block: Add one or more custom CIDR blocks as needed.
      Remarks	Provides supplementary information about the network instance.

   5. Click Load Another Instance to add all the VPCs that need to communicate with each other. Then click the Network Instances tab to view the VPCs you loaded.