What Are the Differences Between Cloud Connect and VPC Peering?
Cloud Connect differs from VPC Peering in the following ways:
- Interworking capabilities: VPC Peering can only connect two VPCs in the same region, but Cloud Connect can connect multiple VPCs either in the same region or in different regions.
- Network capabilities: After you create a VPC peering connection, you need to manually configure routes. With Cloud Connect, you do not need to configure routes.
- The bearer network: VPC Peering uses the data center network, but Cloud Connect uses a DCI backbone network.
- Billing: VPC Peering is free. With Cloud Connect, communications between VPCs in the same region is also free, but cross-region communications require a bandwidth package, which is not free.
Table 1 compares these differences.
Item |
VPC Peering |
Cloud Connect |
|
---|---|---|---|
Interworking capability |
VPCs within a region |
Supported |
Supported |
VPCs across regions |
Not supported |
Supported |
|
Cross-border compliance |
Not supported |
Supported |
|
Networking capability |
Manual routing configuration |
Automatic routing configuration |
|
Bearer network |
Data center network in the region |
Inter-region DCI backbone network |
|
Pricing |
Free of charge |
Free of charge within a region and billed based on standard pricing across regions |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot