This topic describes how to use Direct Connect (DC) to enable an on-premises data center accessing VolcanoEngine cloud services.
Background
Generally, a data center cannot directly access the internal cloud services of VolcanoEngine (such as Torch Object Storage (TOS)). However, in certain business scenarios where access is needed, you can use DC and Cloud Enterprise Network (CEN) products to enable an on-premises data center accessing VolcanoEngine cloud services.
Prerequisites
- One available DC Connection exists.
- You have obtained the address and region of the cloud services to be accessed. This example demonstrates accessing a cloud service at 100.XX.XX.105/32 in China (Beijing).
- You have created a Virtual Private Cloud (named VPC-01) to facilitate network communication between the DC-connected data center and cloud services. For procedure, see Creating a VPC.
Limits
- Ensure that the cloud gateway peer IP configured on the Virtual Interface is not within 100.64.0.0/10. Otherwise, network connectivity between the on-premises data center and the cloud service cannot be established.
- The on-premises data center connected through DC can only access cloud services in the same region as the DC Gateway. For example, if your on-premises data center network accesses VolcanoEngine through a DC Gateway in China (Beijing), the data center can only configure and access cloud services in China (Beijing).
- In a CEN, routes with the same destination CIDR block cannot be configured in the same region, but can be configured in separate regions.
Procedure
Step 1: Create a DC Connection
Step 2: Create a DC Gateway
- Click "Create DC Gateway" to create a DC Gateway with the following configuration.
- Click "Create" to complete the action.
- Click "Go to console" to back to the Direct Connect Gateway console. You can view the new DC gateway (Dcg-01) in the DC Gateway list.
Step 3: Create a Virtual Interface
- Click "Create DC Virtual Interface".
- Configure the Virtual Interface based on the table below.
warning
In this example, a BGP Peer is established along with the creation of the Virtual Interface. Once established, the BGP information (Peer ASN and BGP key) cannot be modified.
- Click "Create" to complete the action.
Step 4: Create a CEN and configure a cloud service
- Configure the CEN based on the table below and load "VPC-01".
- Click "Create" to complete the action.
- In the CEN instances list, click the name of target instance (Cen-01).
- In the "Network Instances" tab, click "Attach Network Instance".
- The Attach Network Instance window pops up. Configure the information of the DC Gateway instance to be loaded.
- In the CEN instances list, click "Cen-01" to enter the details page.
- In the "Cloud Services" tab, click "Configure Cloud Service Access".
- In the Configure Cloud Service Access window on the right, configure the information of the cloud service to be accessed.
- Click "Add" to complete the configuration.
Results
After completing all configurations, you can view all configured cloud service routes under the "Routing information" tab of the CEN details page. In this example, the DC uses BGP routing. Therefore, cloud service routes in the CEN will be automatically propagated into the route table of the DC Gateway, enabling the on-premises data center accessing cloud services via the CEN associated with the DC Gateway.