S3-Compatible Cloud Object Storage Providers (Hyperscalers and Regional Clouds)
· 7 min read · Updated

The large platform clouds all run object storage, and most expose an Amazon S3-compatible endpoint alongside their native API. An S3 client can talk to Alibaba, Tencent, Huawei, IBM, Oracle, Google, Yandex, and many regional clouds once you change the endpoint URL and keys.
These are the platform clouds from our complete list of S3-compatible storage providers. Independent object-storage clouds, hosting platforms, self-hosted servers, enterprise appliances, and decentralized storage each have their own category page in that list.
Blober connects to these services through its generic S3-Compatible provider when they support the common S3 operations it uses: paste the endpoint and keys, then browse to confirm the connection. Regions and hostnames change over time, so take the exact endpoint from the provider's console. Each format below is taken from the provider's documentation and compared with the rclone S3 docs[1].
Almost every cloud here uses virtual-hosted addressing, which puts the bucket in the subdomain (https://my-bucket.s3.example.com). Path-style addressing puts it in the URL path instead (https://s3.example.com/my-bucket). The formats below are hostnames only, so add https:// when you enter one in Blober's endpoint field. The endpoint setup notes explain how Blober picks the style.
Alibaba Cloud Object Storage Service, formerly Aliyun OSS, is the dominant object store in China and across Alibaba's global regions. It has Standard, Infrequent Access, Archive, and Cold Archive tiers. Use the regional endpoint that matches your bucket[2].
- Endpoint format:
oss-<region>.aliyuncs.com(for exampleoss-cn-hangzhou.aliyuncs.com,oss-us-east-1.aliyuncs.com,oss-eu-central-1.aliyuncs.com). - Regions: dozens across mainland China, plus Singapore, Tokyo, Frankfurt, London, Dubai, Silicon Valley, and Virginia.
- Addressing: virtual-hosted (bucket in subdomain).
Tencent Cloud Object Storage is the object store behind much of China's app ecosystem, with a global region footprint. It has Standard, Infrequent Access, and Archive tiers, plus a Global Acceleration endpoint (cos.accelerate.myqcloud.com)[3].
- Endpoint format:
cos.<region>.myqcloud.com(for examplecos.ap-guangzhou.myqcloud.com,cos.ap-singapore.myqcloud.com,cos.na-ashburn.myqcloud.com). - Regions: Beijing, Shanghai, Guangzhou, Chengdu, Hong Kong, Singapore, Mumbai, Seoul, Bangkok, Tokyo, Silicon Valley, Virginia, Toronto, Frankfurt.
- Addressing: virtual-hosted.
Huawei Cloud OBS is a high-capacity object store with an S3-compatible interface, used widely across Asia, Latin America, and EMEA. Several rebranded regional clouds run on OBS (Open Telekom Cloud and SberCloud, listed below), so you connect to them in a similar way[4].
- Endpoint format:
obs.<region>.myhuaweicloud.com(for exampleobs.af-south-1.myhuaweicloud.com,obs.ap-southeast-3.myhuaweicloud.com). - Regions: Johannesburg, Bangkok, Singapore, Hong Kong, Shanghai, Beijing, Guangzhou, plus Latin America (Sao Paulo, Mexico City, Santiago, Buenos Aires, Lima) and Moscow.
- Addressing: virtual-hosted.
IBM Cloud Object Storage, descended from Cleversafe, disperses data across locations and is accessed through an S3-compatible API. It is also sold as on-premises software. Besides HMAC access keys, IBM COS supports IAM API-key authentication, and its storage classes are Standard, Vault, Cold Vault, and Smart Tier[5].
- Endpoint format:
s3.<region>.cloud-object-storage.appdomain.cloud(for examples3.us-east.cloud-object-storage.appdomain.cloud,s3.eu-de.cloud-object-storage.appdomain.cloud). - Regions: US East and South, EU (Frankfurt, Amsterdam, Milan), Great Britain, plus single-site endpoints in many cities. Private endpoints exist for in-cloud traffic.
- Addressing: virtual-hosted.
Oracle Cloud Infrastructure Object Storage has an Amazon S3 Compatibility API in front of its native object store. Authenticate with a Customer Secret Key (an access key and secret pair). If your tool cannot set the region identifier, set it to us-east-1 or leave it blank to use your home region. SigV2 is not supported[6].
- Endpoint format:
<namespace>.compat.objectstorage.<region>.oci.customer-oci.comfor path-style, or<bucket>.vhcompat.objectstorage.<region>.oci.customer-oci.comfor virtual-hosted. The<namespace>is your tenancy's unique Object Storage namespace. - Regions: Ashburn, Phoenix, Frankfurt, London, Tokyo, and the rest of OCI's global regions.
- Addressing: both path-style and virtual-hosted are supported.
Google Cloud Storage uses its own API by default. Its XML API also has an S3-compatible interoperability mode that works with HMAC keys: create an HMAC key for a service account to get an access key and secret. Object versioning listing and a few advanced behaviors differ from AWS, so count on the common operations (browse, upload, download, copy) and check anything more advanced before you rely on it[7].
- Endpoint format:
storage.googleapis.com. - Regions: global. There is one endpoint, and the bucket's location is set when you create it.
- Addressing: virtual-hosted.
Yandex Cloud's object storage is S3-compatible and popular across Russia and the CIS. It has Standard (hot) and Cold storage classes. Use static access keys generated for a service account[8].
- Endpoint format:
storage.yandexcloud.net. - Regions:
ru-central1and its availability zones; the endpoint is single. - Addressing: virtual-hosted.
VK Cloud, previously Mail.ru Cloud Solutions, runs two object storage tiers behind an S3-compatible endpoint: Hotbox for hot data and Icebox for cold. Confirm the current endpoint in the VK Cloud console.
- Endpoint format:
hb.bizmrg.com(Hotbox) andib.bizmrg.com(Icebox), with newerhb.<region>.vkcs.cloudhosts. - Regions: Moscow.
- Addressing: virtual-hosted.
Baidu Object Storage provides an S3-compatible interface for one of China's major clouds, with Standard, Infrequent Access, Cold, and Archive tiers.
- Endpoint format:
s3.<region>.bcebos.com(for examples3.bj.bcebos.comfor Beijing,s3.gz.bcebos.comfor Guangzhou). - Regions: Beijing, Baoding, Suzhou, Guangzhou, Hong Kong, and more.
- Addressing: virtual-hosted.
JD Cloud, the cloud arm of JD.com, has an S3-compatible object storage service. Check the regional endpoint in the JD Cloud console.
- Endpoint format:
s3.<region>.jdcloud-oss.com(for examples3.cn-north-1.jdcloud-oss.com). - Regions: North China, East China, and South China.
- Addressing: virtual-hosted.
China Mobile's Ecloud Elastic Object Storage is a large S3-compatible service with many regions across mainland China. When you create a bucket, its location constraint must match the endpoint[9].
- Endpoint format:
eos-<city>-1.cmecloud.cn(for exampleeos-wuxi-1.cmecloud.cn,eos-beijing-1.cmecloud.cn). - Regions: dozens, from Suzhou and Shanghai to Chengdu, Guiyang, and Xian.
- Addressing: virtual-hosted.
Kingsoft Cloud Standard Storage Service (KS3) is an S3-compatible object store widely used in China. The Kingsoft console shows the current endpoint host.
- Endpoint format:
ks3-<region>.ksyuncloud.comorks3-<region>.ksyun.com(for exampleks3-cn-beijing.ksyuncloud.com). - Regions: Beijing, Shanghai, Guangzhou, Hong Kong, and international points.
- Addressing: virtual-hosted.
China Telecom's CTYun (Tianyi Cloud) Object-Oriented Storage is an S3-compatible service across China Telecom's regions. Get the regional endpoint from the CTYun console.
- Endpoint format:
oos-<region>.ctyunapi.cn(for exampleoos-sccd.ctyunapi.cn). - Regions: many across mainland China.
- Addressing: virtual-hosted.
NAVER Cloud Platform, South Korea's major cloud, runs an S3-compatible object storage service. Generate API keys in the NAVER Cloud console.
- Endpoint format:
<region>.object.ncloudstorage.com(for examplekr.object.ncloudstorage.com). - Regions: Korea, plus other NAVER Cloud regions.
- Addressing: virtual-hosted.
Open Telekom Cloud, operated by T-Systems on Huawei technology, exposes Huawei OBS under its own endpoints. Because of that lineage it behaves like Huawei OBS, with European data residency.
- Endpoint format:
obs.<region>.otc.t-systems.com(for exampleobs.eu-de.otc.t-systems.com). - Regions: Germany (Biere, Magdeburg), the Netherlands, and Switzerland.
- Addressing: virtual-hosted.
SberCloud Advanced (Cloud.ru) runs object storage on Huawei OBS technology with Russian endpoints, so it behaves like Huawei OBS with Russian data residency.
- Endpoint format:
obs.<region>.hc.sbercloud.ru(for exampleobs.ru-moscow-1.hc.sbercloud.ru). - Regions: Moscow.
- Addressing: virtual-hosted.
Netease Object Storage has an S3-compatible interface used by Netease's services and third parties. Confirm the exact endpoint in the Netease console.
- Endpoint format: regional NOS endpoints (for example
nos-eastchina1.126.net). - Regions: several across China.
- Addressing: virtual-hosted (the provider disables path-style addressing).
Azure Blob Storage uses its own API, so it is not S3-compatible in the drop-in sense, and an S3 client cannot talk to it without a translation gateway. The concepts line up: a container maps to a bucket and a blob to an object. Blober connects to Azure Blob and to S3 storage and copies files between them, so you can move data in either direction without a gateway. See How to Transfer AWS S3 to Azure Blob.
Is Google Cloud Storage S3-compatible?
For the common operations, yes, through its XML API interoperability mode. Create an HMAC key and point your S3 client at storage.googleapis.com. A few advanced behaviors differ from AWS S3.
Is Alibaba OSS the same as AWS S3? OSS speaks the S3 API, so S3 tools work against it once you change the endpoint and keys. Alibaba runs it, and its tier names and some features are its own.
Why do Open Telekom Cloud and SberCloud look like Huawei OBS? They are built on Huawei OBS technology and rebranded for their regions. You connect over S3 the same way, with different endpoints and data residency.
Can Blober move data from one cloud's object storage to another? Yes. Set one provider's endpoint as the source and another's as the destination, and Blober copies the objects between them through your computer. That covers ordinary object transfers, though gaps in a provider's S3 features can still matter for advanced workflows.