Creating Intra-account Peering Connection

[Oct. 31, 2023] - Discontinuing Cross-region Connections of Peering Connection

Upgrading Migration of the Cross-Region Interconnection Service from Peering Connection to CCN

Updates and Announcements

Overview

Features

Use Limits

Relevant Products

Product Introduction

Billing Overview

Purchasing Method

Overdue Payment Policies

Purchase Guide

Creating Cross-account Peering Connection

Getting Started

Operation Overview

Configuring the Route to Peering Connection

Creating and Deleting Peering Connection

Viewing Relevant Routing Policies

Viewing Monitoring Data of Network Traffic Over a Cross-region Peering Connection

Configuring the Bandwidth Cap for a Cross-region Peering Connection

Rejecting a Peering Connection

Deleting a Peering Connection

Viewing the Peer Account ID

Enabling Cross-region Connectivity for Basic Networks

Operation Guide

API Documentation

Migrating the Cross-Region Interconnection Service to CCN

Practical Tutorial

Concepts

Service Level Agreement

Service Agreement

Glossary

Peering Connection

Both cross-region and cross-account communication of VPCs are advanced features of peering connections. This document describes how to implement 

Perform the two steps below to implement communication between IP ranges 1 and 2 over a peering connection under the same account:


Select a region and a VPC (for example, Guangzhou and 

Enter a name (for example, PeerConn), select the local region and network, and select the peer region (for example, Beijing), account type, and VPC. Then, accept the service agreement.

, select the account from the drop-down list.

, enter the account ID and VPC ID of the peer account.

For an intra-region peering connection, there is no bandwidth cap. Therefore, this 

For a cross-region peering connection, the bandwidth cap can be selected. The bandwidth cap supports 10Mbps, 20Mbps, 50Mbps, 100Mbps, 200Mbps, 500Mbps, and 1Gbps. If you need higher cross-region bandwidth, please 

https://console.tencentcloud.com/workorder/category

. A peering connection between two VPCs under the same account takes effect immediately after its creation.

You must configure routes on both sides to implement communication over a peering connection.

Please directly add routing policies to the original route table associated with the subnet at both ends. There is no need to create a new route table, because if you use a new route table to add routing policies, the original route table of the subnet will be replaced, and the original routing policies will become invalid. All instances under the subnet use the new routing table policy, which may affect services.

To enable communication between multiple IP ranges of the two VPCs, you simply need to add route table entries, instead of creating multiple peering connections.

https://console.tencentcloud.com/

 to access the Virtual Private Cloud (VPC) console.

Click the ID of the route table (route table A) associated with the local subnet (subnet A) of the peering connection to access the route table details page.

 for the next hop type, and select the created peering connection (PeerConn) for the next hop.

. After the route table is configured, communication is enabled between the IP ranges of the two VPCs.


The peer route table is configured in the same way as that at the local end.

tencent cloud