- Updates and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- 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
- API Documentation
- Practical Tutorial
- FAQ
- Service Agreement
- Glossary
- Updates and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- 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
- API Documentation
- Practical Tutorial
- FAQ
- Service Agreement
- Glossary
Is the connectivity of a peering connection transitive?
A peering connection enables connectivity between two VPCs, but the connectivity cannot be transited.
For example, peering connections are created between VPC 1 and VPC 2, and between VPC 1 and VPC 3. However, due to the non-transitivity of peering connections, traffic cannot flow between VPC 2 and VPC 3.
Note:
Even if a peering connection is created, both ends of the connection cannot communicate with each other if routes for sending and returning packets are not configured at both ends.
What is the difference between intra-region and cross-region peering connections?
Intra-region peering connections are used to connect applications located in different VPCs within the same region.
Cross-regional peering connections are used to implement connectivity between VPCs in different regions.
Can I set bandwidth limits for peering connections?
For a cross-region peering connection: you can set a bandwidth limit when you create the connection using an API. Setting bandwidth limits in the console will be supported in the near future.
For an intra-region peering connection: you do not need to set a bandwidth limit for the connection because bandwidth is free of charge and is unlimited.
If a peering connection is deleted at one end, is the VPC at the other end still accessible from the peer end?
No. The peering connection can be disconnected at either end at any time. The connection is ineffective immediately upon disconnection. The VPC at either end is accessible only after the connection is created again.
Can I create a peering connection between VPCs of different accounts?
Yes. This is possible as long as the owner of the other VPC accepts your peering connection request.
Can I create a peering connection between two VPCs with overlapped IP ranges?
No. The IP ranges of VPCs at the two ends of a peering connection cannot overlap.
Is traffic encrypted over a peering connection?
No. After a peering connection is created, access between two VPCs is similar to that between two CVMs in the same VPC, without additional encryption. Network traffic within a VPC is always isolated from other networks.
Is a single point of failure possible?
Single points of failure or bandwidth bottlenecks cannot occur because a peering connection between VPCs is not a gateway or a VPN connection and it does not depend on separate hardware.
Yes
No
Was this page helpful?