- 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
- Best Practices
- 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
- Best Practices
- FAQ
- Service Agreement
- Glossary
For information on related products, see the following table.
Product name | Relationship with peering connections |
The CVMs at either end of a peering connection can access all the resources at the peer end, including CVMs, databases, and CLBs. | |
CVMs at either end of a peering connection can access all resources of at the peer end, including CVMs, databases, and CLBs. | |
A peering connection enables communication between two VPCs. | |
A peer connection enables communication only after route tables are correctly configured at both ends. | |
A peering connection enables communication between two VPCs, while Classiclink enables communication between a basic network and a VPC. | |
You can log in to the Cloud Monitoring console to set alarm policies. |
예
아니오
문제 해결에 도움이 되었나요?