Help Center/ Object Storage Service/ Best Practices/ Accessing Data Stored in OBS/ Using Cloud Connect to Access OBS Across Regions over an Intranet
Updated on 2026-08-14 GMT+08:00

Using Cloud Connect to Access OBS Across Regions over an Intranet

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:

  1. An ECS accesses the Direct Connect domain name (test-zcy-abc.obs-private.cn-north-4.myhuaweicloud.com) of bucket test-zcy-abc.
  2. 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.
  3. 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.
  4. The cloud connection routes the request to the Cloud Connect network instance in the region where the OBS bucket is located.
  5. 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.
  6. 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