To access Object Storage Service (OSS) data in a bucket by calling API operations or by using OSS SDKs, ossutil, and ossfs, you must use an endpoint of the region in which the bucket is located. This topic describes terms, such as regions and endpoints, and provides endpoints of different regions.
Terms
Before you use endpoints, make sure that you are familiar with the following terms:
Region: the physical location in which data is stored, such as China (Hangzhou). When you create a bucket, you must select a region. To reduce latency, we recommend that you select a region that is closest to users. When you select a region, we recommend that you consider factors such as physical locations, relationships between cloud services, resource prices, and features.
Region ID: the ID of the region. For example, the region ID of China (Hangzhou) is
cn-hangzhou. In the public cloud, when you use OSS SDKs to obtain a V4 signature, you must use the Region ID. The OSS region ID is used in the request parameters, response parameters, and OSS endpoints of OSS API operations. The OSS region ID is in theoss-{region-id}format. For example, the region ID of China (Hangzhou) iscn-hangzhou, whereas the OSS region ID of China (Hangzhou) isoss-cn-hangzhou.Endpoint: the endpoint used to access OSS data. Each region has its own endpoints. To access data in a bucket by calling API operations or by using OSS SDKs, ossutil, and ossfs, you must use an endpoint of the region in which the bucket is located. By default, OSS provides a public endpoint and an internal endpoint for each region in the public cloud.
Public endpoint: allows you to access data in a bucket from anywhere over the Internet. A public endpoint is suitable for the distribution of static resources on websites, file sharing, and cross-region access of data by using cloud services. For example, you can use an Elastic Compute Service (ECS) instance to access OSS data by using a public endpoint. You are charged outbound traffic fees when you use a public endpoint to access data.
Internal endpoint: allows you to access OSS data in a bucket over the internal network of Alibaba Cloud. By default, internal networks of different regions are isolated and cannot communicate with each other. An internal endpoint is suitable for scenarios in which you want to use Alibaba Cloud services in the same region in which the bucket is located to access OSS. For example, you can use an ECS instance to access OSS data by using an internal endpoint. You are not charged outbound traffic fees when you use an internal endpoint to access data. When you use internal endpoints of OSS, you must use the internal DNS addresses of Alibaba Cloud (
100.100.2.136and100.100.2.138). Otherwise, you may not be able to obtain valid VIPs of the internal endpoints. As a result, access to OSS fails.
NoteFor example, if you are located in the Chinese mainland, when you use a public endpoint to upload an object to or download an object from a bucket in the US (Silicon Valley) region, upload or download failures may occur or you may experience slow upload and download. For these cross-border transmission network exceptions, OSS provides transfer acceleration for buckets in specific regions. After you enable transfer acceleration for a bucket, you can use an acceleration endpoint instead of the public endpoint to accelerate data transfers.
Protocol :OSS endpoints support two application-layer protocols: HTTP and HTTPS. To ensure data security during transmission, we recommend that you use HTTPS. In terms of network layer protocols, OSS supports IPv4 in all regions. Dual-stack endpoints are provided in specific regions to allow an IPv6 client to access OSS by using an endpoint that supports IPv6.
Alibaba Cloud public cloud
Asia Pacific - China
Region | Region ID | OSS Region ID | Public 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) | 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 regions
Region | Region ID | OSS Region ID | Public 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 |
Australia (Sydney) (Closing down) | ap-southeast-2 | oss-ap-southeast-2 | oss-ap-southeast-2.aliyuncs.com | oss-ap-southeast-2-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 Region ID | Public 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 |
Middle East
Region | Region ID | OSS Region ID | Public 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 |