Regions and Domain Names
US3 object storage provides two access methods: external network domain names and internal network domain names. External network domain names can respond to all access requests from the Internet, while internal network domain names can respond to access requests from UCloud public cloud services in the same region (such as UHost cloud hosts, UK8S container clouds, etc.).
Accessing data using an external network domain name will incur external network outgoing traffic fees.
After you create a storage space, the access domain name format of your storage space is: <Bucket Name>.<Endpoint>
. The <Endpoint>
is consists of <region_code>.<custom_domain>
.
Access Domain (Endpoint)
The general syntax of the access domain is as follows:
protocol://<region_code>.<custom_domain>
For example, http://cn-sh2.example.com is an public network access domain name in Shanghai, China. In this, cn-sh2 is <region_code>
, .example.com is <custom_domain>
.
For private network access domain names, you can use the following format:
protocol://internal.<region_code>.<custom_domain>
The private network requires adding the private network access identifier internal. in front of <region_code>
. The above example access domain name is changed to http://internal.cn-sh2.example.com
Explanation about region_code.custom_domain
Enter the Object Storage module in the console, and find the following tag <Bucket Domain>
under the single-region space management paging.
The tag is composed of <bucket name>.<region_code>.<custom_domain>
.
Access Domain Names (Endpoints) for US3 Protocol in Public Cloud by Region:
Region | External Domain | Internal Domain |
---|---|---|
North China 1 | cn-bj.ufileos.com | internal-cn-bj.ufileos.com |
North China 2 | cn-wlcb.ufileos.com | internal-cn-wlcb.ufileos.com |
Shanghai 2 | cn-sh2.ufileos.com | internal-cn-sh2-01.ufileos.com |
Guangzhou | cn-gd.ufileos.com | internal-cn-gd-02.ufileos.com |
Hong Kong | hk.ufileos.com | internal-hk-01.ufileos.com |
Los Angeles | us-ca.ufileos.com | internal-us-ca-01.ufileos.com |
Singapore | sg.ufileos.com | internal-sg-01.ufileos.com |
Jakarta | idn-jakarta.ufileos.com | internal-idn-jakarta-01.ufileos.com |
Taipei | tw-tp.ufileos.com | internal-tw-tp.ufileos.com |
Lagos | afr-nigeria.ufileos.com | internal-afr-nigeria.ufileos.com |
São Paulo | bra-saopaulo.ufileos.com | internal-bra-saopaulo.ufileos.com |
Dubai | uae-dubai.ufileos.com | internal-uae-dubai.ufileos.com |
Frankfurt | ge-fra.ufileos.com | internal-ge-fra.ufileos.com |
Ho Chi Minh City | vn-sng.ufileos.com | internal-vn-sng.ufileos.com |
Washington | us-ws.ufileos.com | internal-us-ws.ufileos.com |
Mumbai | ind-mumbai.ufileos.com | internal-ind-mumbai.ufileos.com |
Seoul | kr-seoul.ufileos.com | internal-kr-seoul.ufileos.com |
Tokyo | jpn-tky.ufileos.com | internal-jpn-tky.ufileos.com |
Bangkok | th-bkk.ufileos.com | internal-th-bkk.ufileos.com |
UK | uk-london.ufileos.com | internal-uk-london.ufileos.com |
Moscow | rus-mosc.ufileos.com | internal-rus-mosc.ufileos.com |
Access Domain Names (Endpoints) for AWS S3 Protocol in Public Cloud by Region:
No. | Region | External Network Endpoint | Internal Network Endpoint |
---|---|---|---|
1 | North China 1 | s3-cn-bj.ufileos.com | internal.s3-cn-bj.ufileos.com |
2 | North China 2 | s3-cn-wlcb.ufileos.com | internal.s3-cn-wlcb.ufileos.com |
3 | Shanghai | s3-cn-sh2.ufileos.com | internal.s3-cn-sh2.ufileos.com |
4 | Guangzhou | s3-cn-gd.ufileos.com | internal.s3-cn-gd.ufileos.com |
5 | Hong Kong | s3-hk.ufileos.com | internal.s3-hk.ufileos.com |
6 | Los Angeles | s3-us-ca.ufileos.com | internal.s3-us-ca.ufileos.com |
7 | Singapore | s3-sg.ufileos.com | internal.s3-sg.ufileos.com |
8 | Jakarta | s3-idn-jakarta.ufileos.com | internal.s3-idn-jakarta.ufileos.com |
9 | Taipei | s3-tw-tp.ufileos.com | internal.s3-tw-tp.ufileos.com |
10 | Lagos | s3-afr-nigeria.ufileos.com | internal.s3-afr-nigeria.ufileos.com |
11 | São Paulo | s3-bra-saopaulo.ufileos.com | internal.s3-bra-saopaulo.ufileos.com |
12 | Dubai | s3-uae-dubai.ufileos.com | internal.s3-uae-dubai.ufileos.com |
13 | Frankfurt | s3-ge-fra.ufileos.com | internal.s3-ge-fra.ufileos.com |
14 | Ho Chi Minh City | s3-vn-sng.ufileos.com | internal.s3-vn-sng.ufileos.com |
15 | Washington | s3-us-ws.ufileos.com | internal.s3-us-ws.ufileos.com |
16 | Mumbai | s3-ind-mumbai.ufileos.com | internal.s3-ind-mumbai.ufileos.com |
17 | Seoul | s3-kr-seoul.ufileos.com | internal.s3-kr-seoul.ufileos.com |
18 | Tokyo | s3-jpn-tky.ufileos.com | internal.s3-jpn-tky.ufileos.com |
19 | Bangkok | s3-th-bkk.ufileos.com | internal.s3-th-bkk.ufileos.com |
20 | London | s3-uk-london.ufileos.com | internal.s3-uk-london.ufileos.com |
21 | Moscow | s3-rus-mosc.ufileos.com | internal.s3-rus-mosc.ufileos.com |
Note:
1. Due to different regions of storage clusters, cross-border access may experience response delays or failures. The overseas acceleration service feature is in the internal testing stage, if you need to use it, please contact technical support.
2. For domain names compatible with the AWS S3 protocol, please refer to the “AWS S3 Protocol Support Description”.
3. The default external network domain of US3 has limitations on speed and file types in download scenarios; it is recommended to use a custom domain for external network download scenarios.