# S3-Compatible Cloud Object Storage Providers (Hyperscalers and Regional Clouds)

> S3-compatible object storage from major platform clouds: Alibaba OSS, Tencent COS, Huawei OBS, IBM COS, Oracle OCI, Google Cloud Storage, Yandex, and more, with endpoint formats, regions, and how to connect each one.

The large platform clouds all run object storage, and most expose an Amazon S3-compatible endpoint alongside their native API. That means you can point an S3 client at Alibaba, Tencent, Huawei, IBM, Oracle, Google, Yandex, and many regional clouds by changing the endpoint URL and keys. This page lists the cloud S3-compatible services, their endpoint formats, and how to connect each one.

This is one category in our [complete list of S3-compatible storage providers](/kb/articles/s3-compatible-storage-providers-complete-list/). For independent object-storage clouds, hosting platforms, self-hosted servers, enterprise appliances, and decentralized storage, see the other category pages linked at the end.

These services are intended to connect through Blober's generic [S3-Compatible connector](/kb/docs/providers/s3-compatible/) when they support the common S3 operations Blober uses. Paste the endpoint and keys, then browse to confirm. Confirm the exact endpoint in each provider's console, since regions and hostnames change over time. The endpoint formats below come from each provider's own documentation, cross-checked against current S3 client references[\[1\]](https://rclone.org/s3/ "Source: rclone.org/s3/").

Each entry notes an **addressing style**. Virtual-hosted puts the bucket in the subdomain (`https://my-bucket.s3.example.com`); path-style puts it in the URL path (`https://s3.example.com/my-bucket`). Almost every cloud here uses virtual-hosted. The endpoint formats below show hostnames; in Blober, include `https://` in the endpoint field. The [endpoint setup notes](/kb/docs/providers/s3-compatible/#endpoint) explain how Blober picks the right one.

## Alibaba Cloud OSS (Object Storage Service)

Alibaba Cloud Object Storage Service, formerly Aliyun OSS, is the dominant object store in China and across Alibaba's global regions.

* **Endpoint format:** `oss-<region>.aliyuncs.com` (for example `oss-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).
* **Notes:** OSS offers Standard, Infrequent Access, Archive, and Cold Archive tiers. Use the matching regional endpoint for your bucket[\[2\]](https://www.alibabacloud.com/product/oss "Source: www.alibabacloud.com/product/oss").

## Tencent Cloud COS (Cloud Object Storage)

Tencent Cloud Object Storage is the object store behind much of China's app ecosystem, with a global region footprint.

* **Endpoint format:** `cos.<region>.myqcloud.com` (for example `cos.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.
* **Notes:** there is also a Global Acceleration endpoint (`cos.accelerate.myqcloud.com`). Standard, Infrequent Access, and Archive tiers are available[\[3\]](https://intl.cloud.tencent.com/product/cos "Source: intl.cloud.tencent.com/product/cos").

## Huawei Cloud OBS (Object Storage Service)

Huawei Cloud OBS is a high-capacity object store with an S3-compatible interface, used widely across Asia, Latin America, and EMEA.

* **Endpoint format:** `obs.<region>.myhuaweicloud.com` (for example `obs.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.
* **Notes:** OBS underpins several rebranded regional clouds (Open Telekom Cloud and SberCloud, listed below), so the connection pattern is similar[\[4\]](https://www.huaweicloud.com/intl/en-us/product/obs.html "Source: www.huaweicloud.com/intl/en-us/product/obs.html").

## IBM Cloud Object Storage (COS)

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.

* **Endpoint format:** `s3.<region>.cloud-object-storage.appdomain.cloud` (for example `s3.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.
* **Notes:** IBM COS supports IAM API-key authentication in addition to HMAC access keys. Storage classes include Standard, Vault, Cold Vault, and Smart Tier[\[5\]](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-classes "Source: cloud.ibm.com/docs/cloud-object-storage").

## Oracle Cloud Infrastructure (OCI) Object Storage

Oracle Cloud Infrastructure Object Storage offers an Amazon S3 Compatibility API in front of its native object store.

* **Endpoint format:** `<namespace>.compat.objectstorage.<region>.oci.customer-oci.com` for path-style, or `<bucket>.vhcompat.objectstorage.<region>.oci.customer-oci.com` for 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 and virtual-hosted are supported.
* **Notes:** 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\]](https://docs.oracle.com/en-us/iaas/Content/Object/Tasks/s3compatibleapi.htm "Source: docs.oracle.com/en-us/iaas/Content/Object/Tasks/s3compatibleapi.htm").

## Google Cloud Storage (XML / S3 Interoperability)

Google Cloud Storage is not S3 by default, but its XML API has an S3-compatible interoperability mode that works with HMAC keys.

* **Endpoint format:** `storage.googleapis.com`.
* **Regions:** global; the endpoint is single, and the bucket's location is set when you create it.
* **Addressing:** virtual-hosted.
* **Notes:** 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 treat GCS as S3-compatible for the common operations (browse, upload, download, copy) rather than a perfect clone[\[7\]](https://cloud.google.com/storage/docs/interoperability "Source: cloud.google.com/storage/docs/interoperability").

## Yandex Object Storage

Yandex Cloud's object storage is S3-compatible and popular across Russia and the CIS.

* **Endpoint format:** `storage.yandexcloud.net`.
* **Regions:** `ru-central1` and its availability zones; the endpoint is single.
* **Addressing:** virtual-hosted.
* **Notes:** Standard (hot) and Cold storage classes are available. Use static access keys generated for a service account[\[8\]](https://yandex.cloud/en/services/storage "Source: yandex.cloud/en/services/storage").

## VK Cloud Object Storage (formerly Mail.ru Cloud Solutions)

VK Cloud, previously Mail.ru Cloud Solutions, runs Hotbox and Icebox object storage tiers behind an S3-compatible endpoint.

* **Endpoint format:** `hb.bizmrg.com` (Hotbox) and `ib.bizmrg.com` (Icebox), with newer `hb.<region>.vkcs.cloud` hosts.
* **Regions:** Moscow.
* **Addressing:** virtual-hosted.
* **Notes:** Hotbox is the hot tier, Icebox the cold tier. Confirm the current endpoint in the VK Cloud console.

## Baidu AI Cloud BOS (Baidu Object Storage)

Baidu Object Storage provides an S3-compatible interface for one of China's major clouds.

* **Endpoint format:** `s3.<region>.bcebos.com` (for example `s3.bj.bcebos.com` for Beijing, `s3.gz.bcebos.com` for Guangzhou).
* **Regions:** Beijing, Baoding, Suzhou, Guangzhou, Hong Kong, and more.
* **Addressing:** virtual-hosted.
* **Notes:** Standard, Infrequent Access, Cold, and Archive tiers are available.

## JD Cloud Object Storage (OSS)

JD Cloud, the cloud arm of JD.com, exposes an S3-compatible object storage service.

* **Endpoint format:** `s3.<region>.jdcloud-oss.com` (for example `s3.cn-north-1.jdcloud-oss.com`).
* **Regions:** North China, East China, and South China.
* **Addressing:** virtual-hosted.
* **Notes:** confirm the regional endpoint in the JD Cloud console.

## China Mobile Ecloud EOS (Elastic Object Storage)

China Mobile's Ecloud Elastic Object Storage is a large, region-dense S3-compatible service across mainland China.

* **Endpoint format:** `eos-<city>-1.cmecloud.cn` (for example `eos-wuxi-1.cmecloud.cn`, `eos-beijing-1.cmecloud.cn`).
* **Regions:** dozens, from Suzhou and Shanghai to Chengdu, Guiyang, and Xian.
* **Addressing:** virtual-hosted.
* **Notes:** the location constraint must match the endpoint when creating buckets[\[9\]](https://ecloud.10086.cn/home/product-introduction/eos/ "Source: ecloud.10086.cn/home/product-introduction/eos/").

## Kingsoft Cloud KS3

Kingsoft Cloud Standard Storage Service (KS3) is an S3-compatible object store widely used in China.

* **Endpoint format:** `ks3-<region>.ksyuncloud.com` or `ks3-<region>.ksyun.com` (for example `ks3-cn-beijing.ksyuncloud.com`).
* **Regions:** Beijing, Shanghai, Guangzhou, Hong Kong, and international points.
* **Addressing:** virtual-hosted.
* **Notes:** confirm the current endpoint host in the Kingsoft console.

## China Telecom CTYun OOS

China Telecom's CTYun (Tianyi Cloud) Object-Oriented Storage is an S3-compatible service across China Telecom's regions.

* **Endpoint format:** `oos-<region>.ctyunapi.cn` (for example `oos-sccd.ctyunapi.cn`).
* **Regions:** many across mainland China.
* **Addressing:** virtual-hosted.
* **Notes:** confirm the regional endpoint in the CTYun console.

## NAVER Cloud Object Storage

NAVER Cloud Platform, South Korea's major cloud, runs an S3-compatible object storage service.

* **Endpoint format:** `<region>.object.ncloudstorage.com` (for example `kr.object.ncloudstorage.com`).
* **Regions:** Korea, plus other NAVER Cloud regions.
* **Addressing:** virtual-hosted.
* **Notes:** generate API keys in the NAVER Cloud console.

## Open Telekom Cloud OBS

Open Telekom Cloud, operated by T-Systems on Huawei technology, exposes Huawei OBS under its own endpoints.

* **Endpoint format:** `obs.<region>.otc.t-systems.com` (for example `obs.eu-de.otc.t-systems.com`).
* **Regions:** Germany (Biere, Magdeburg), the Netherlands, and Switzerland.
* **Addressing:** virtual-hosted.
* **Notes:** the OBS lineage means it behaves like Huawei OBS, with European data residency.

## SberCloud OBS

SberCloud Advanced (Cloud.ru) runs object storage on Huawei OBS technology with Russian endpoints.

* **Endpoint format:** `obs.<region>.hc.sbercloud.ru` (for example `obs.ru-moscow-1.hc.sbercloud.ru`).
* **Regions:** Moscow.
* **Addressing:** virtual-hosted.
* **Notes:** behaves like Huawei OBS with Russian data residency.

## Netease NOS (Netease Object Storage)

Netease Object Storage offers an S3-compatible interface used by Netease's services and third parties.

* **Endpoint format:** regional NOS endpoints (for example `nos-eastchina1.126.net`).
* **Regions:** several across China.
* **Addressing:** virtual-hosted (path-style addressing is disabled by the provider).
* **Notes:** confirm the exact endpoint in the Netease console.

## A Note on Microsoft Azure Blob Storage

Azure Blob Storage is the obvious omission here, and it is deliberate. Azure Blob uses its own API, not the S3 API, so it is not S3-compatible in the drop-in sense. The concepts line up (a container maps to a bucket, a blob to an object), but an S3 client cannot talk to Azure Blob without a translation gateway. If you need to move data between S3 and Azure, Blober bridges the two directly. See [How to Transfer AWS S3 to Azure Blob](/kb/articles/how-to-transfer-aws-s3-to-azure-blob/).

## Frequently Asked Questions

**Is Google Cloud Storage S3-compatible?** Through its XML API interoperability mode, yes, for the common operations. You 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 by changing the endpoint and keys. It is run by Alibaba, not Amazon, and its tier names and some features are its own.

**Why do Open Telekom Cloud and SberCloud look like Huawei OBS?** Because they are built on Huawei OBS technology and rebranded for their regions. The S3-compatible connection pattern is the same, with different endpoints and data residency.

**Can Blober move data from one cloud's object storage to another?** Yes. Point Blober at a source endpoint and a destination endpoint and it copies between them directly for normal object transfers. Provider-specific S3 feature gaps can still matter for advanced workflows.

## Related Guides

* [The Complete List of S3-Compatible Providers](/kb/articles/s3-compatible-storage-providers-complete-list/)
* [Object Storage Specialists](/kb/articles/best-s3-compatible-object-storage-specialists/)
* [Hosting and VPS Object Storage](/kb/articles/s3-compatible-storage-hosting-vps-providers/)
* [What S3-Compatible Really Means](/kb/articles/what-s3-compatible-really-means/)

## Get Blober

Connect to any cloud's S3-compatible object storage by URL and move data between providers directly, without filling your local disk.

**[Download Blober at blober.io](https://blober.io)**