Docs

Direct Connect

On-premises to Cloud migration

Connecting an on-premises data center to a VPC across accounts and regions

Virtual Private Clouds (VPCs) in different accounts and regions are isolated from on-premises data center networks. This section describes how to enable network connectivity between an on-premises data center and a VPC across accounts and regions.

Background introduction

A data center in Beijing is connected to the cloud via a Direct Connect (DC) Connection in the nearest region. Now, you want to access from the data center to resources in a VPC in a different region and account via DC Connection.

Prerequisites

You have created a VPC (name: vpc-test) and its subnet in China (Shanghai) under Account B (account ID: 200****02), and purchased an Elastic Compute Service (ECS) instance within that VPC. For procedures, see Creating a VPC and Buying ECS instances.

Procedure

Step 1: Create a DC Connection

In this example, the creation of DC Connection is completed. The DC Connection under the current account (Account B, ID: 200****01) is marked as "Opened". For procedure, see Creating a Direct Connect Connection. DAS230_port01_conn is the DC Connection in China (Beijing).

Step 2: Create a DC Gateway

Use Account A to log in to the Direct Connect Gateway console.

Click Create DC Gateway to create a DC Gateway with the following configuration.

Parameters	Description	Value
Regions	Select the region where the DC Gateway is deployed. It must match the region of the DC Connection.	China (Beijing)
Name	Set a name for the DC Gateway.	dcg-test
ASN	Set an ASN for the DC Gateway. This example does not require a custom ASN and directly uses the Volcano Engine ASN.	137718
IPv6	Enable IPv6 as needed.	Disable
Affiliated project	Select the project to which the new DC Gateway belongs.	Project-test
Agreement	Follow the console guidance to review and accept Legal.	Check

Click Buy now to complete the action.

Click Go to console to return to the Direct Connect Gateway console. You can view the new DC Gateway (dcg-test) in the DC Gateway list.

Step 3: Create a Virtual Interface

Use Account A to log in to the DC Virtual Interface console.

Click Create DC Virtual Interface.

Configure the Virtual Interface based on the table below.

Parameters	Description	Sample value
Basic information
Resource ownership	Select the account to which the Virtual Interface belongs. tip The feature of creating a Shared Virtual Interface for another account is currently in the beta stage. If you need a trial, please contact your account manager.	My account
Regions	Select the region where the Virtual Interface is deployed. It must be the same as the region of the DC Connection and the DC Gateway.	China (Beijing)
Name	Set a name for the Ethernet Virtual Interface.	VIF-weo4
DC Connection	Filter the DC Connection by project to associate with the Virtual Interface.	Project-test\|DAS230_port01_conn
Direct Connect Gateway	Filter the DC Gateway by project to associate with the Virtual Interface.	Project-test\|dcg-test
Bandwidth limit	Enable bandwidth limit as needed.	Disable
Interconnection information
IPv4 interconnect IP	Set the IPv4 IP for interconnection. Cloud gateway peer IP: Set an IPv4 address and mask for the cloud DC gateway. You may customize the interconnect IP according to network planning, but confirm that the cloud gateway peer IP and your gateway peer IP are in the same CIDR block without duplication. Use a private IP address that does not conflict with cloud or on-premises IP addresses. Your gateway peer IP: Set an IPv4 address and mask for the gateway on your on-premises data center. You may customize the interconnect IP according to network planning, but confirm that the cloud gateway peer IP and your gateway peer IP are in the same CIDR block without duplication. Use a private IP address that does not conflict with cloud or on-premises IP addresses.	Cloud gateway peer IP: 10.0.0.1/30 Your gateway IP: 10.0.0.2/30
IPv6 interconnect IP	Enable IPv6 IP for interconnection as needed.	Disable
VLAN ID	Set a VLAN ID for connecting to the data center. Confirm that this VLAN ID is unoccupied.	10
Routing information
Route type	Support two route types: BGP and Static. This example uses BGP routes.	BGP
Peer ASN	Set the ASN for the IPv4 BGP Peer. The valid range for ASN is 1 to 4294960000. The ASN of the BGP Peer can neither be the same as that of the DC Gateway, nor be the VolcanoEngine ASN (137718).	483600
BGP key	Type the key for the IPv4 BGP Peer.	00300
Detection method	Select a detection method for the line. After enabling BFD, periodic packets are sent between VolcanoEngine and on-premises devices to detect the link status. This enables rapid switching to the secondary connection upon failure and completing route convergence in the from-cloud direction.	BFD
BFD mode	Select a mode for the BFD detection. The mode is BFD control packet in this example.	BFD control packet
Detect interval	The time interval for BFD to send consecutive packets.	2000
Detect multiplier	The number of BFD detection attempts. If a BFD session fails to receive the defined number of consecutive packets, the system declares a route failure.	8

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.

Configure data center routing. For reference commands, see Configure the routing for a data center.

Step 4: Create a Cloud Enterprise Network

Use Account A to log in to the CEN console.

Click Create CEN.

Configure the CEN based on the table below.

Parameters	Value
Basic information
Name	cen-01
Main account	A parameter that only appears on the O&M-side. Select the account of the resource.
Network Instances
Attach Network Instance	Disable
More information
Project	Project-test

Click Create to complete the action. The ID of the new CEN is cen-rrhx580****1ri7. Record this ID, which is required for cross-account authorization.

Step 5: Authorize cross-account CEN

Use Account B to log in to the Virtual Private Cloud console.

In the VPC list, click the name of the target VPC: vpc-test.

Click the CEN cross-account authorization tab, and then click CEN cross-account authorization.

In the pop-up dialog box, type the information of the CEN under another account.

Parameters
Value
Owner account ID
200****01
Peer CEN instance ID
cen-rrhx580****1ri7

After completion, click Attach.

Step 6: Load a network instance to the CEN

Load a VPC of another account

Use Account A to log in to the CEN console. In the CEN instance list, click the name of the 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 to be loaded.

Parameters
Value
Account
Cross-account
Owner account ID
200****02
Regions
China (Shanghai)
Instance type
Virtual Private Cloud (VPC)
Network Instances
vpc-test

Load a DC Gateway of my account

Use Account A to log in to the CEN console. In the CEN instance list, click the name of the 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 to be loaded.

Parameters
Value
Account
My account
Regions
China (Beijing)
Instance type
DC Gateway
Network Instances
dcg-test

Step 7: Purchase a bandwidth package and allocate inter-region bandwidth.

tip

This example is accessing resources in a VPC across accounts and regions. Cross-region access requires purchasing a CEN bandwidth package. If you are accessing resources in a VPC across accounts but in the same region, you can skip this step.

Use Account A to log in to the CEN console. In the left-side navigation pane, click Bandwidth Package.

Click Create BWP, and configure the bandwidth package based on the table below.

Parameters	Value
Basic information
Billing method	Subscription
Name	package-test
Bandwidth configuration
CEN	Project-test\|cen-01
Interoperability area	Chinese mainland - Chinese mainland
Bandwidth	300Mbps
Duration	1 month
More information
Affiliated project	Project-test

Click Confirm order. After confirming the order is correct on its details page, follow the console guidance to review and accept the legal terms.

Click Buy now to complete the bandwidth package creation.

In the left-side navigation pane, click CEN Instances.

Click the CEN Instance name (cen-01), and then click the Inter-region bandwidth tab in the details page.

In the Inter-region bandwidth zone, click Allocate inter-region bandwidth. Allocate bandwidth across regions based on the table below.

Parameters
Value
Bandwidth package
package-test
Interconnected regions
China (Beijing) - China (Shanghai)
Bandwidth
200Mbps

Click Create to complete configuration.

Step 8: Configure local routing and BFD

Configure routing and BFD on a local switch.

tip

Configuration commands are vendor-specific. These commands are for reference only. Adjust commands based on your device model. For details, consult your device vendor.

Reference commands

Step 9: Test connectivity

Run the following command. A successful Ping indicates the data center is properly connected to the VPC network across accounts and regions.

ping 192.168.2.10

Last updated: 2026.08.24 11:30:48

Parameters	Value
Owner account ID	200****01
Peer CEN instance ID	cen-rrhx580****1ri7

Parameters	Value
Account	Cross-account
Owner account ID	200****02
Regions	China (Shanghai)
Instance type	Virtual Private Cloud (VPC)
Network Instances	vpc-test

Parameters	Value
Bandwidth package	package-test
Interconnected regions	China (Beijing) - China (Shanghai)
Bandwidth	200Mbps