Scenarios
To reduce access latency and meet data compliance requirements, your service data may be stored in OBS buckets across regions. In addition, you may need to centrally access, process, and analyze data in these buckets. For example, your ECS is deployed in CN East-Shanghai1, while the OBS bucket for storing data may reside in another region like CN North-Beijing4. In this case, the ECS needs to access the OBS bucket across regions. If Cloud Connect is not used, cross-region access relies on public networks. This can lead to high network latency, unstable bandwidth, and high public network traffic costs. By using Cloud Connect, you can establish an intranet channel to enable cross-region access to OBS buckets. The Cloud Connect–based solution has the following advantages:
- High-speed transmission: The high-quality intranet backbone network of Huawei Cloud provides faster data transmission, lower latency, and higher stability than public networks.
- Lower costs: There are no traffic costs for across-region access to OBS over an intranet.
- Enhanced data security: Data is securely transmitted over the intranet of Huawei Cloud.
This section describes how to use Cloud Connect to access OBS across regions. In this solution, the Direct Connect domain names and IP addresses of buckets are used. When accessing a bucket, you only need to access its Direct Connect domain name, and Cloud Connect will automatically route your request to the bucket in the target region.
Background
Before using Cloud Connect to access OBS across regions, you may want to know:
- Cloud Connect: Cloud Connect allows you to build high-speed, high-quality, and stable networks between VPCs across regions. For more information, see Cloud Connect.
- OBS bucket domain name: After a bucket is created, OBS generates a default domain name in the BucketName.obs.RegionID.myhuaweicloud.com format. For example, the domain name of bucket test-zcy-abc in CN North-Beijing4 is test-zcy-abc.obs.cn-north-4.myhuaweicloud.com.
- Private IP address of an OBS bucket: The address for accessing an OBS bucket over the Huawei Cloud intranet. Resolving a bucket's domain name through private DNS returns a private IP address, whereas resolving it through public DNS returns a public IP address.
- Direct Connect domain name: In multi-cloud scenarios, IP address conflicts can occur when an IDC accesses OBS through Direct Connect. To solve this problem, OBS provides Direct Connect domain names in the BucketName.obs-private.RegionID.myhuaweicloud.com format. For example, the Direct Connect domain name of bucket test-zcy-abc in CN North-Beijing4 is test-zcy-abc.obs-private.cn-north-4.myhuaweicloud.com.
- Direct Connect IP address: Resolving a Direct Connect domain name through public DNS will return the corresponding Direct Connect IP address, but it can only be used to access OBS over an intranet. According to the Internet Engineering Task Force (IETF) and Internet Assigned Numbers Authority (IANA) standards, OBS reserves the 100.125.0.0/16 network segment for intranet access. This network segment is mainly used for interconnection between IDCs and cloud services. However, in multi-cloud scenarios, this shared segment can lead to IP address conflicts when routes of different cloud vendors are configured in the same IDC. To address this issue, OBS reserves a Direct Connect IP address segment for each Huawei Cloud region.
Solution Architecture
Figure 1 Logical architecture for accessing OBS across regions
The process of using Cloud Connect to access an OBS bucket across regions is as follows:
- An ECS accesses the Direct Connect domain name (test-zcy-abc.obs-private.cn-north-4.myhuaweicloud.com) of bucket test-zcy-abc.
- DNS returns the Direct Connect IP address resolved from the Direct Connect domain name to the ECS. Huawei Cloud has internally mapped the Direct Connect domain name to its corresponding IP address. Therefore, you do not need to configure DNS resolution in this practice.
- The ECS sends a request to the Direct Connect IP address, and the request passes through the Cloud Connect network instance in the same region.
- The cloud connection routes the request to the Cloud Connect network instance in the region where the OBS bucket is located.
- The Cloud Connect network instance routes the request to the VPC endpoint (OBS Gateway Endpoint) in the same VPC. The OBS Gateway Endpoint provides high-bandwidth, low-latency access to OBS buckets.
- The request reaches OBS through the VPC endpoint. Cross-region access to the OBS bucket is complete.
Advantages
- Simplified architecture: There is no need to purchase or configure DNS to resolve OBS domain names. Direct Connect domain names provided by OBS can be resolved by the public DNS to return the Direct Connect IP addresses. You can directly use these IP addresses to access OBS.
- Efficient transmission: Data is transmitted via a dedicated connection, which ensures high network performance and low latency. The OBS Gateway Endpoint enables high-bandwidth, low-latency access to OBS buckets.
- High security and reliability: Cloud Connect uses a dedicated private channel to connect to Huawei Cloud VPCs, ensuring network isolation and high security.
Constraints
Currently, Direct Connect domain names are only available in CN East-Shanghai1 and CN North-Beijing4. For other regions, you can submit a service ticket to contact technical support.
Resource and Cost Planning
Table 1 Resource planning | Region | Resource | Resource Name | Description | Quantity | Billing |
| CN East-Shanghai1 | VPC | VPC-B-test | VPC CIDR block: 172.16.0.0/16 Create a VPC on the VPC console. | 1 | Free |
| VPC subnet | subnet-VPC-B | Subnet CIDR block: 172.16.0.0/24 Configure a subnet when creating the VPC on the VPC console. | 1 | Free |
| ECS | ecs-test | Create an ECS in the VPC-B-test VPC on the ECS console. This ECS will be used to access an OBS bucket. | 1 | In this practice, the ECS is billed on a pay-per-use basis. The billing items include the ECS itself, an image, and disks. For details, see ECS Pay-per-Use Billing. |
| Cloud Connect network instance | - | Load the network instance of VPC-B-test in CN East-Shanghai1 to the cloud connection on the Cloud Connect console. | 1 | Free |
| N/A (global resources are not region-specific) | Cloud connection | cloudconnect-test | Create a cloud connection on the Cloud Connect console. | 1 | Free |
| Bandwidth package | bandwidthPackge-test | A bandwidth package is required for the cloud connection to work properly. | 1 | In this practice, the bandwidth package is billed on a pay-per-use basis. For details, see Cloud Connect Pay-per-Use Billing. |
| CN North-Beijing4 | Cloud Connect network instance | - | Load the network instance of VPC-A-test in CN North-Beijing4 to the cloud connection on the Cloud Connect console. | 1 | Free |
| VPC | VPC-A-test | VPC CIDR block: 192.168.0.0/16 Create a VPC on the VPC console. | 1 | Free |
| VPC subnet | subnet-VPC-A | Subnet CIDR block: 192.168.0.0/24 Configure a subnet when creating the VPC on the VPC console. | 1 | Free |
| VPC endpoint | - | Purchase a VPC endpoint (OBS Gateway Endpoint) for the cluster where the OBS bucket resides on the VPC Endpoint console in CN North-Beijing4. | 1 | Free |
| OBS bucket | test-zcy-abc | The bucket that will be accessed by the ECS Create a bucket on OBS Console. | 1 | You will be billed for the storage space occupied by objects uploaded to the bucket. For details, see Storage Space. |
Operation Process
Figure 2 Using Cloud Connect to access an OBS bucket across regions
Procedure
Step 1: Create VPCs, an ECS, and an OBS Bucket
1. Create VPCs.
Create VPC-A-test in CN North-Beijing4 and VPC-B-test in CN East-Shanghai1 to isolate resources.
- Go to the page for creating a VPC.
- On the Create VPC page, set the following parameters and retain the default settings for other parameters.
For more information about creating a VPC, see Creating a VPC with a Subnet.

Table 2 VPC parameters | Parameter | Example Value | Description |
| Region | CN North-Beijing4 | The region where the VPC will be created. For lower latency and faster access, select the region nearest to you. |
| Name | VPC-A-test | The VPC name. The name: - Can contain 1 to 64 characters.
- Can only include letters, digits, underscores (_), hyphens (-), and periods (.).
|
| IPv4 CIDR Block | 192.168.0.0/16 | The IP address range for the VPC. All subnets in the VPC must be within this range. The following CIDR blocks are supported: - 10.0.0.0/8–24
- 172.16.0.0/12–24
- 192.168.0.0/16–24
If the IPv4/IPv6 dual-stack is disabled, the CIDR Block parameter is displayed. If the IPv4/IPv6 dual-stack is enabled, the IPv4 CIDR Block parameter is displayed. |
| Enterprise Project | default | The enterprise project to which the VPC belongs An enterprise project makes it easy to manage projects and group cloud resources and users. The default enterprise project is default. If you do not have any specific needs for enterprise project division and management, choose the default enterprise project. For details about creating and managing enterprise projects, see Enterprise Management User Guide. |
| Subnet Name | subnet-VPC-A | The subnet name. The name: - Can contain 1 to 64 characters.
- Can only include letters, digits, underscores (_), hyphens (-), and periods (.).
|
- Click Create Now.
Return to the VPC list and view the created VPC.
- Repeat 1 to 3 to create the second VPC. Set the parameters as follows:
- Region: CN East-Shanghai1
- Name: VPC-B-test
- IPv4 CIDR Block: 172.16.0.0/16
- Enterprise Project: default
- Subnet Name: subnet-VPC-B
2. Create an ECS.
Create an ECS in VPC-B-test in CN East-Shanghai1. This ECS will be used to access an OBS bucket.
- Log in to the console and go to the Buy ECS page. Click the Custom Config tab.
- Set Basic Configuration.

Table 3 Basic configuration parameters | Parameter | Example Value | Description |
| Billing Mode | Pay-per-use | Select a billing mode for the ECS. Pay-per-use: postpaid billing mode. You pay as you go and just pay for what you use. Pay-per-use ECSs are billed by the second and settled by the hour. This mode is applicable to scenarios where compute resource requirements fluctuate. You can enable and delete resources at any time. For more information, see Billing Overview. |
| Region | CN East-Shanghai1 | Select the region where the ECS is located. For lower latency and faster access, select the region nearest to you. Once an ECS is purchased, its region cannot be changed. For more information, see Region and AZ. |
- Set OS.

Table 4 OS parameters | Parameter | Example Value | Description |
| Image | CentOS 6.10 64bit(40 GiB) | A public Linux image provided by Huawei Cloud |
- Set Storage & Backup.

Table 5 Storage & backup parameters | Parameter | Example Value | Description |
| Enable backup | Do not select this option. | Optional. Cloud Backup and Recovery (CBR) lets you restore data to any point in the past if there is a virus attack, accidental deletion, or software or hardware fault. In this practice, backup is not required, but you can enable it later if needed. For more information, see CBR Overview. |
- Set Network.

Table 6 Network parameters | Parameter | Example Value | Description |
| VPC | VPC-B-test | Select the VPC where the ECS belongs to isolate the network environment of the ECS. For more information, see VPC and Subnet Planning. |
| Primary NIC | - subnet-VPC-B
- Automatically assign IP address
| Select a VPC subnet. |
- Set Public Network Access.
Table 7 Public network access parameters | Parameter | Example Value | Description |
| EIP | Not required | If public network access is needed, purchase an EIP and attach it to the ECS. For more information, see EIP Overview. |
- Set Instance Management.

Table 8 Instance management parameters | Parameter | Example Value | Description |
| ECS Name | ecs-test | Specify an ECS name based on naming rules. |
| Login Mode | Password | Select the password login mode. Set a password and confirm it. |
| Enterprise Project | default | This parameter is displayed only when you use an enterprise account to purchase an ECS. You can use enterprise projects for unified management of cloud resources. |
- In the Configuration Summary panel on the right, confirm the ECS details.
- Read and agree to the agreement, and click Submit.
- Pay for the order.
- Go back to the ECS list to view the purchased ECS.
3. Create an OBS bucket.
Create an OBS bucket in CN North-Beijing4. This bucket will be accessed by the ECS.
- In the navigation pane of OBS Console, choose Buckets.
- Click Create Bucket in the upper right corner of the page.
- Set the following parameters and retain the default settings for other parameters.
For more information about creating an OBS bucket, see Creating a Bucket.
Table 9 Parameters for creating a bucket | Parameter | Example Value | Description |
| Region | CN North-Beijing4 | The region where the bucket is created - Once the bucket is created, its region cannot be changed.
- For lower latency and faster access, select the region nearest to where the data will be accessed.
|
| Bucket Name | test-zcy-abc | When creating a bucket, you need to set a proper bucket name. Once a bucket is created, its name cannot be changed. In accordance with the globally applied DNS naming rules, an OBS bucket name: - Must be unique. It cannot be the same as the name of any existing bucket or parallel file system (including those created by others). You must wait at least 30 minutes before you can reuse the name of a deleted bucket or parallel file system.
- Must be 3 to 63 characters long.
- Can contain only lowercase letters, digits, hyphens (-), and periods (.). It cannot start or end with a hyphen (-) or period (.).
- Cannot contain two consecutive periods (..) or contain a period (.) and a hyphen (-) adjacent to each other.
- Cannot be formatted as an IP address.
|
| Enterprise Project | default | You can add the bucket to an enterprise project for unified management. If you do not have any specific needs for enterprise project division and management, choose the default enterprise project. To learn more about how to manage OBS buckets using enterprise projects, see the Enterprise Project parameter in Creating a Bucket. |
- Click Create Now in the lower right corner of the page. Confirm the information displayed and click OK.
- In the displayed Created dialog box, click OK. View the newly created bucket in the bucket list.
- Obtain the Direct Connect domain name and IP address in the region where the bucket is located for later use. For details, see Table 10. To obtain the domain names and IP addresses in other regions, submit a service ticket to contact technical support.
In this practice, the Direct Connect domain name in the region where test-zcy-abc is located is obs-private.cn-north-4.myhuaweicloud.com, and the Direct Connect IP address segment is 120.46.235.0/25.
Table 10 Direct Connect domain names and IP address segments in two regions | Region Name | Region ID | Direct Connect Domain Name | Direct Connect IP Address Segment |
| CN North-Beijing4 | cn-north-4 | obs-private.cn-north-4.myhuaweicloud.com | 120.46.235.0/25 |
| CN East-Shanghai1 | cn-east-3 | obs-private.cn-east-3.myhuaweicloud.com | 123.60.199.0/25 |
Step 2: Create a Cloud Connection and Load Network Instances
Create a cloud connection and load network instances in two VPCs located in CN East-Shanghai1 and CN North-Beijing4 respectively, so that the two VPCs can communicate with each other.
- Create a cloud connection.
- Go to the cloud connection list page.
- In the upper right corner of the page, click Create Cloud Connection.
- In the displayed dialog box, set the following parameters and retain the default settings for other parameters.
For more information about creating a cloud connection, see Creating a Cloud Connection.

Table 11 Parameters for creating a cloud connection | Parameter | Example Value | Description |
| Name | cloudconnect-test | The cloud connection name |
| Enterprise Project | default | You can add the cloud connection to an enterprise project for management. An enterprise project makes it easy to manage projects and group cloud resources and users. If you do not have any specific needs for enterprise project division and management, choose the default enterprise project. For details about creating and managing enterprise projects, see Enterprise Management User Guide. |
| Scenario | VPC | The application scenario of the cloud connection If you select VPC here, only VPCs or virtual gateways can use this cloud connection. |
- Click OK.
- Load network instances.
- Click the name of the created cloud connection to go to the basic information page.
- Click the Network Instances tab and click Load Network Instance.
- In the Load Network Instance dialog box, set the following parameters and retain the default settings for other parameters.
For more information, see Loading a Network Instance to a Cloud Connection.

Table 12 Parameters for loading network instances in the same account to the cloud connection | Parameter | Example Value | Description |
| Region | CN East-Shanghai1 | The region where the VPC to be connected is located Select the region where the ECS is located, which is CN East-Shanghai1. |
| VPC | VPC-B-test | The VPC that needs to be loaded to the cloud connection for interconnection This parameter is mandatory if you have set Instance Type to VPC. |
| VPC CIDR Block | subnet-VPC-B | The subnets of the VPC you want to load and the CIDR blocks If you have set Instance Type to VPC, you need to configure the following two parameters: - Subnet: The subnet of the VPC. In this practice, select subnet-VPC-B, the subnet of the VPC in CN East-Shanghai1.
- Other CIDR Block: Leave the parameter empty.
|
- Click OK.
- Repeat 2.b to 2.d to load the network instance in CN North-Beijing4. Set the parameters as follows.
- Region: CN North-Beijing4
- VPC: VPC-A-test
- VPC CIDR Block:
- Subnet: subnet-VPC-A
- Other CIDR Block: In this practice, enter the IP address segment corresponding to the Direct Connect domain name in the CN North-Beijing4 region where the bucket to be accessed is located. The value has been obtained in 6.
- Buy a bandwidth package.
- Go to the Bandwidth Packages tab page and click Buy Bandwidth Package.
- On the Buy Bandwidth Package page, set the following parameters and retain the default settings for other parameters.
For more information about buying a bandwidth package, see Buying a Bandwidth Package.


Table 13 Parameters for buying a bandwidth package | Parameter | Example Value | Description |
| Billing Mode | Pay-per-use | The billing mode of the bandwidth package Pay-per-use: You are billed based on the actual usage duration. You can enable or delete the bandwidth package at any time. For more information, see Pay-per-Use Billing. |
| Name | bandwidthPackge-test | The name of the bandwidth package The name can contain 1 to 64 characters. Only digits, letters, underscores (_), hyphens (-), and periods (.) are allowed. |
| Enterprise Project | default | You can add the bandwidth package to an enterprise project for management. An enterprise project can be used to centrally manage cloud resources and users by project. If you do not have any specific needs for enterprise project division and management, choose the default enterprise project. For details about creating and managing enterprise projects, see Enterprise Management User Guide. |
| Applicability | Single geographic region | Whether you want to use the bandwidth package for communication within a geographic region or between geographic regions There are two options: - Single geographic region: Use the bandwidth package between regions in the same geographic region.
- Across geographic regions: Use the bandwidth package between regions in different geographic regions.
In this practice, communication between CN East-Shanghai1 and CN North-Beijing4 is within a geographic region. |
| Geographic Region | Chinese mainland | The geographic region |
| Bandwidth | 5 | The bandwidth you require for communication between regions, in Mbit/s. The sum of all inter-region bandwidths you assign cannot exceed the total bandwidth of the bandwidth package. Assign the bandwidth based on your network plan. |
| Cloud Connection | cloudconnect-test | The cloud connection you want to attach the bandwidth package to In this practice, attach the bandwidth package to the cloud connection cloudconnect-test created in 1. |
- Click Next.
- Confirm the configuration and submit your order.
- Assign inter-region bandwidths.
- Go to the Cloud Connections page.
- Click the name of the cloud connection created in 1 to go to the basic information page.
- Click the Inter-Region Bandwidths tab and click Assign Inter-Region Bandwidth.
- In the Assign Inter-Region Bandwidth dialog box, set the following parameters:

Table 14 Parameters for assigning an inter-region bandwidth | Parameter | Example Value | Description |
| Regions | CN East-Shanghai1, CN North-Beijing4 | The regions that need to communicate with each other In this practice, select CN East-Shanghai1 and CN North-Beijing4. |
| Bandwidth Package | bandwidthPackge-test | The bandwidth package that is attached to the cloud connection Select the bandwidth package purchased in 3. |
| Bandwidth | 5 | The bandwidth you require for communication between regions, in Mbit/s The bandwidth has been set when you purchased the bandwidth package in 3. You do not need to set it again. |
- Click OK.
Step 3: Buy a VPC Endpoint
Buy an OBS Gateway Endpoint in CN North-Beijing4 to allow cloud resources in VPC-A-test to access OBS without using EIPs.
- Go to the VPC endpoint list page.
- Click Buy VPC Endpoint.
- On the Buy VPC Endpoint page, set the following parameters and retain the default settings for other parameters.
For more information about buying a VPC endpoint, see Buying a VPC Endpoint.

Table 15 Parameters for buying a VPC endpoint | Parameter | Example Value | Description |
| Region | CN North-Beijing4 | The region where the VPC endpoint is located Resources in different regions cannot communicate with each other over an intranet. For lower latency and faster access, select the region nearest to you. |
| Service Category | Find a service by name | Select Find a service by name if the VPC endpoint service to be accessed is a private service of your own. |
| VPC Endpoint Service Name | - | This parameter is mandatory when you select Find a service by name for Service Category. In this practice, enter the name of the VPC endpoint service in the cluster where the bucket in CN North-Beijing4 to be accessed is located. Submit a service ticket to obtain the name. Enter the service name and click Verify. - If "Service name found" is displayed, proceed with subsequent operations.
- If "Service name not found" is displayed, check whether the region is the same as that of the VPC endpoint service or whether the entered service name is correct.
|
| VPC | VPC-A-test | The VPC where the VPC endpoint is to be deployed In this practice, select the VPC-A-test VPC in CN North-Beijing4 where the bucket to be accessed is located. |
- Click Next in the lower right corner.
- Confirm the information and click Submit.
- Go back to the VPC endpoint list to view the created VPC endpoint.
Step 4: Verify the Result
Use the ECS to access the Direct Connect domain name of the OBS bucket to test the connectivity.
- On the ECS list page, click Remote Login in the Operation column of the ECS purchased in 1.
- Enter the password to log in to the ECS. Then, run the following command to check whether the ECS can access the OBS bucket across regions:
ping Direct Connect domain name of the bucket
In this practice, run the ping test-zcy-abc.obs-private.cn-north-4.myhuaweicloud.com command.

As shown in the figure, the ECS can access the OBS bucket across regions even if no EIP is attached to the ECS.