Creating a VPC Peering Connection with Another VPC in Your Account

Scenarios

If two VPCs from the same region cannot communicate with each other, you can use a VPC peering connection. This section describes how to create a VPC peering connection between two VPCs in the same account.

This following describes how to create a VPC peering connection between VPC-A and VPC-B in account A to enable communications between ECS-A01 and RDS-B01.

Procedure:

Step 1: Create a VPC Peering Connection

Step 2: Add Routes for the VPC Peering Connection

Step 3: Verify Network Connectivity

Figure 1 Networking diagram of a VPC peering connection between VPCs in the same account

Notes and Constraints

• Only one VPC peering connection can be created between two VPCs at the same time.
• A VPC peering connection can only connect VPCs in the same region.
• If the local and peer VPCs have overlapping CIDR blocks, the VPC peering connection may not take effect.

Prerequisites

You have two VPCs from the same account in the same region. If you want to create one, see Creating a VPC.

Step 1: Create a VPC Peering Connection

1. Log in to the management console.

2. Click in the upper left corner and select the desired region and project.
3. Click in the upper left corner and choose Network > Virtual Private Cloud.

   The Virtual Private Cloud page is displayed.

4. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

   The VPC peering connection list is displayed.

5. In the upper right corner of the page, click Create VPC Peering Connection.

   The Create VPC Peering Connection dialog box is displayed.

6. Configure the parameters as prompted.

   For details, see Table 1.

   Figure 2 Create VPC Peering Connection
   

   Table 1 Parameters for creating a VPC peering connection

   Parameter	Description	Example Value
   VPC Peering Connection Name	Mandatory Enter a name for the VPC peering connection. The name can contain a maximum of 64 characters, including letters, digits, hyphens (-), and underscores (_).	peering-AB
   Local VPC	Mandatory VPC at one end of the VPC peering connection. You can select one from the drop-down list.	VPC-A
   Local VPC CIDR Block	CIDR block of the selected local VPC	172.16.0.0/16
   Account	Mandatory Options: My account and Another account Select My account.	My account
   Peer Project	The system fills in the corresponding project by default because My account is set to Account. For example, if VPC-A and VPC-B are in account A and region A, the system fills in the correspond project of account A in region A by default.	ab-cdef-1
   Peer VPC	This parameter is mandatory if Account is set to My account. VPC at the other end of the VPC peering connection. You can select one from the drop-down list.	VPC-B
   Peer VPC CIDR Block	CIDR block of the selected peer VPC If the local and peer VPCs have overlapping CIDR blocks, the VPC peering connection may not take effect. For details, see VPC Peering Connection Usage Examples.	172.17.0.0/16

7. Click OK.

   A dialog box for adding routes is displayed.

8. In the displayed dialog box, click Add Now. On the displayed Local Routes page, go to Step 2: Add Routes for the VPC Peering Connection to add a route.

Step 2: Add Routes for the VPC Peering Connection

To enable communications between VPCs connected by a VPC peering connection, you need to add forward and return routes to the route tables of the VPCs. For details, see VPC Peering Connection Usage Examples.

1. Add routes to the route table of the local VPC:
   1. On the Local Routes tab of the VPC peering connection, click the Route Tables hyperlink.

      The Summary tab of the default route table for the local VPC is displayed.

      Figure 3 Hyperlink to route table-Local VPC
      
   2. Click Add Route.

      Table 2 describes the route parameters.

      Table 2 Parameter description

      Parameter	Description	Example Value
      Destination	The peer VPC CIDR block, subnet CIDR block, or ECS IP address. For details, see VPC Peering Connection Usage Examples.	VPC-B CIDR block: 172.17.0.0/16
      Next Hop Type	The next hop type. Select VPC peering connection.	VPC peering connection
      Next Hop	The next hop address. Select the name of the current VPC peering connection.	peering-AB
      Description	Supplementary information about the route. This parameter is optional. The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).	-

   3. Click OK.

      You can view the route in the route list.

      Figure 4 Route for the local VPC
      

2. Add routes to the route table of the peer VPC:
   1. On the Peer Routes tab of the VPC peering connection, click the Route Tables hyperlink.

      The Summary tab of the default route table for the peer VPC is displayed.

      Figure 5 Hyperlink to route table-Peer VPC
      
   2. Click Add Route.

      Table 3 describes the route parameters.

      Table 3 Parameter description

      Parameter	Description	Example Value
      Destination	The local VPC CIDR block, subnet CIDR block, or ECS IP address. For details, see VPC Peering Connection Usage Examples.	VPC-A CIDR block: 172.16.0.0/16
      Next Hop Type	The next hop type. Select VPC peering connection.	VPC peering connection
      Next Hop	The next hop address. Select the name of the current VPC peering connection.	peering-AB
      Description	Supplementary information about the route. This parameter is optional. The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).	-

   3. Click OK.

      You can view the route in the route list.

      Figure 6 Route for the peer VPC
      

Step 3: Verify Network Connectivity