OSS regions and endpoints - Object Storage Service - Alibaba Cloud Documentation Center

To access Object Storage Service (OSS) through REST APIs using tools such as the software development kit (SDK) or ossutil, you must use the endpoint that corresponds to the OSS region. This topic describes basic concepts, such as regions and endpoints, and lists the regions and endpoints that OSS supports.

Terms

Before you use OSS endpoints, understand the following concepts:

Region

A region is the physical location of an Alibaba Cloud data center where data is stored, such as China (Hangzhou). You must select a region when you create a bucket. When you select an OSS region, consider the following factors:

User location

If other users access your OSS resources, you must consider network latency to ensure a good user experience. In addition to the quality of communication lines, distance is a major factor that affects network latency.

For example, a user in Hangzhou can run the curl command to test the latency when accessing OSS data centers in different regions.

region="Hangzhou"
domain="oss-cn-hangzhou.aliyuncs.com"
curl -o /dev/null -s -w "Region: ${region}\nDomain: ${domain}\nConnect: %{time_connect}s\nStart Transfer: %{time_starttransfer}s\nTotal: %{time_total}s\n" https://${domain}

region="Chengdu"
domain="oss-cn-chengdu.aliyuncs.com"
curl -o /dev/null -s -w "Region: ${region}\nDomain: ${domain}\nConnect: %{time_connect}s\nStart Transfer: %{time_starttransfer}s\nTotal: %{time_total}s\n" https://${domain}

The following test results are returned:

Region: Hangzhou
Domain: oss-cn-hangzhou.aliyuncs.com
Connect: 0.062289s
Start Transfer: 0.110251s
Total: 0.111032s
Region: Chengdu
Domain: oss-cn-chengdu.aliyuncs.com
Connect: 0.113452s
Start Transfer: 0.280528s
Total: 0.281272s

The results show that latency increases with the distance to the data center. Therefore, select a region that is geographically closest to your users.

Relationship between cloud products

If you use OSS as a data source for other Alibaba Cloud services, select an OSS region based on the regions of the other services. If other Alibaba Cloud services and OSS are in the same region, you can access OSS over a VPC endpoint. This method is faster than accessing OSS over the Internet and does not incur data transfer fees.

Resource prices

Resource plan prices may be lower in some regions due to different discount policies. When you select an OSS region, prioritize regions with lower resource plan prices.

Product features

New OSS features are first released for public preview in selected regions. If you want to try these new features, you must create a bucket in a specified region. For more information, see Release Notes.

Region ID

A region ID is the code for a region. For example, the region ID for China (Hangzhou) is cn-hangzhou. You can use the region ID to initialize a V4 signature with the SDK or ossutil.

OSS-specific region ID

The request parameters and responses of OSS APIs and OSS endpoints use OSS-specific region IDs. The format is oss-{region-id}. For example, the OSS-specific region ID that corresponds to cn-hangzhou is oss-cn-hangzhou.

Endpoint

An endpoint is an entry point for accessing OSS. Each region has its own endpoints. To access OSS through REST APIs using tools such as the SDK or ossutil, you must use an endpoint. The endpoint must correspond to the region that you selected when you created the bucket. In the public cloud, OSS provides two types of default endpoints for each region: Internet endpoints and internal endpoints.

Internet endpoints: Allow you to access OSS from anywhere over the Internet. These endpoints are suitable for scenarios such as static resource distribution for websites, file sharing, and cross-region access to OSS from other Alibaba Cloud services. An example is an ECS instance accessing OSS in another region over an Internet endpoint. Data transfer costs are incurred for outbound traffic.
Internal endpoints: Allow you to access OSS through the Alibaba Cloud internal network. By default, internal networks in different regions are isolated and cannot directly communicate with each other. These endpoints are suitable for scenarios in which an Alibaba Cloud service accesses OSS within the same region, for example, an ECS instance accessing OSS using an internal endpoint. Using an internal endpoint does not incur outbound data transfer fees. When you use an OSS internal endpoint, you must use the Alibaba Cloud private DNS addresses (100.100.2.136 and 100.100.2.138). Otherwise, you may not be able to obtain the correct virtual IP address (VIP) for the OSS internal endpoint, and as a result, you cannot access OSS.

Note

To address network abnormalities during long-distance transfers, such as failures or slow speeds when you upload or download files from the Chinese mainland to an OSS bucket in the US (Silicon Valley) over a public endpoint, you can enable transfer acceleration for buckets in specific regions. After you enable this feature, your bucket supports a transfer acceleration endpoint. You can then replace the public endpoint with the transfer acceleration endpoint to accelerate long-distance data transfers. For more information, see Accessing OSS over the IPv6 protocol.

Protocol

You can access OSS endpoints using the HTTP and HTTPS application-layer protocols. To ensure the security of data in transit, we recommend that you use HTTPS. For network-layer protocols, all OSS regions support IPv4. In addition, some regions provide dual-stack endpoints that allow clients to access OSS using IPv6 addresses.

Public cloud

Asia Pacific - China

Region	Region ID	OSS-specific region ID	Internet Endpoint	Internal Endpoint	Protocol
China (Hangzhou)	cn-hangzhou	oss-cn-hangzhou	oss-cn-hangzhou.aliyuncs.com	oss-cn-hangzhou-internal.aliyuncs.com	HTTP HTTPS
China (Shanghai)	cn-shanghai	oss-cn-shanghai	oss-cn-shanghai.aliyuncs.com	oss-cn-shanghai-internal.aliyuncs.com	HTTP HTTPS
China (Nanjing - Local Region) (Closing Down)	cn-nanjing	oss-cn-nanjing	oss-cn-nanjing.aliyuncs.com	oss-cn-nanjing-internal.aliyuncs.com	HTTP HTTPS
China (Qingdao)	cn-qingdao	oss-cn-qingdao	oss-cn-qingdao.aliyuncs.com	oss-cn-qingdao-internal.aliyuncs.com	HTTP HTTPS
China (Beijing)	cn-beijing	oss-cn-beijing	oss-cn-beijing.aliyuncs.com	oss-cn-beijing-internal.aliyuncs.com	HTTP HTTPS
China (Zhangjiakou)	cn-zhangjiakou	oss-cn-zhangjiakou	oss-cn-zhangjiakou.aliyuncs.com	oss-cn-zhangjiakou-internal.aliyuncs.com	HTTP HTTPS
China (Hohhot)	cn-huhehaote	oss-cn-huhehaote	oss-cn-huhehaote.aliyuncs.com	oss-cn-huhehaote-internal.aliyuncs.com	HTTP HTTPS
China (Ulanqab)	cn-wulanchabu	oss-cn-wulanchabu	oss-cn-wulanchabu.aliyuncs.com	oss-cn-wulanchabu-internal.aliyuncs.com	HTTP HTTPS
China (Shenzhen)	cn-shenzhen	oss-cn-shenzhen	oss-cn-shenzhen.aliyuncs.com	oss-cn-shenzhen-internal.aliyuncs.com	HTTP HTTPS
China (Heyuan)	cn-heyuan	oss-cn-heyuan	oss-cn-heyuan.aliyuncs.com	oss-cn-heyuan-internal.aliyuncs.com	HTTP HTTPS
China (Guangzhou)	cn-guangzhou	oss-cn-guangzhou	oss-cn-guangzhou.aliyuncs.com	oss-cn-guangzhou-internal.aliyuncs.com	HTTP HTTPS
China (Chengdu)	cn-chengdu	oss-cn-chengdu	oss-cn-chengdu.aliyuncs.com	oss-cn-chengdu-internal.aliyuncs.com	HTTP HTTPS
China (Hong Kong)	cn-hongkong	oss-cn-hongkong	oss-cn-hongkong.aliyuncs.com	oss-cn-hongkong-internal.aliyuncs.com	HTTP HTTPS

Asia Pacific - Other

Region	Region ID	OSS-specific region ID	Internet Endpoint	Internal Endpoint	Protocol
Japan (Tokyo)	ap-northeast-1	oss-ap-northeast-1	oss-ap-northeast-1.aliyuncs.com	oss-ap-northeast-1-internal.aliyuncs.com	HTTP HTTPS
South Korea (Seoul)	ap-northeast-2	oss-ap-northeast-2	oss-ap-northeast-2.aliyuncs.com	oss-ap-northeast-2-internal.aliyuncs.com	HTTP HTTPS
Singapore	ap-southeast-1	oss-ap-southeast-1	oss-ap-southeast-1.aliyuncs.com	oss-ap-southeast-1-internal.aliyuncs.com	HTTP HTTPS
Malaysia (Kuala Lumpur)	ap-southeast-3	oss-ap-southeast-3	oss-ap-southeast-3.aliyuncs.com	oss-ap-southeast-3-internal.aliyuncs.com	HTTP HTTPS
Indonesia (Jakarta)	ap-southeast-5	oss-ap-southeast-5	oss-ap-southeast-5.aliyuncs.com	oss-ap-southeast-5-internal.aliyuncs.com	HTTP HTTPS
Philippines (Manila)	ap-southeast-6	oss-ap-southeast-6	oss-ap-southeast-6.aliyuncs.com	oss-ap-southeast-6-internal.aliyuncs.com	HTTP HTTPS
Thailand (Bangkok)	ap-southeast-7	oss-ap-southeast-7	oss-ap-southeast-7.aliyuncs.com	oss-ap-southeast-7-internal.aliyuncs.com	HTTP HTTPS

Europe and Americas

Region	Region ID	OSS-specific region ID	Internet Endpoint	Internal Endpoint	Protocol
Germany (Frankfurt)	eu-central-1	oss-eu-central-1	oss-eu-central-1.aliyuncs.com	oss-eu-central-1-internal.aliyuncs.com	HTTP HTTPS
UK (London)	eu-west-1	oss-eu-west-1	oss-eu-west-1.aliyuncs.com	oss-eu-west-1-internal.aliyuncs.com	HTTP HTTPS
US (Silicon Valley)	us-west-1	oss-us-west-1	oss-us-west-1.aliyuncs.com	oss-us-west-1-internal.aliyuncs.com	HTTP HTTPS
US (Virginia)	us-east-1	oss-us-east-1	oss-us-east-1.aliyuncs.com	oss-us-east-1-internal.aliyuncs.com	HTTP HTTPS
Mexico	na-south-1	oss-na-south-1	oss-na-south-1.aliyuncs.com	oss-na-south-1-internal.aliyuncs.com	HTTP HTTPS

Middle East

Region

Region ID

OSS-specific region ID

Internet Endpoint

Internal Endpoint

Protocol

UAE (Dubai)

me-east-1

oss-me-east-1

oss-me-east-1.aliyuncs.com

oss-me-east-1-internal.aliyuncs.com

HTTP

HTTPS

SAU (Riyadh - Partner Region)

Important

The SAU (Riyadh - Partner Region) region is operated by a partner.

me-central-1

oss-me-central-1

oss-me-central-1.aliyuncs.com

oss-me-central-1-internal.aliyuncs.com

HTTP

HTTPS