S3-Compatible Storage Providers: The Complete List (90+ Providers)
This is a practical list of well-known S3-compatible storage providers. If a service speaks the Amazon S3 API, the same tools, SDKs, and apps that work with AWS S3 usually work with it by changing two things: the endpoint URL and the access keys. That portability is why so many S3-compatible services exist, from global clouds to storage you run on your own hardware.
We have grouped them into six categories so the list stays usable. Each provider below links to a detailed entry with its endpoint format, regions, addressing style, and notes. Whatever S3-compatible store you are searching for, there is a good chance it is on this page.
Every endpoint format here comes from the provider's own documentation, cross-checked against current S3 client references and the per-provider sources in the category pages[1]. The tables show endpoint hostnames for readability. In Blober, enter the full URL with https:// unless you are connecting to a local/self-hosted server that explicitly uses http://.
What S3-Compatible Means Here
Section titled "What S3-Compatible Means Here"S3-compatible means the service exposes the same HTTP API as Amazon S3, so an S3 client points at it by URL. It does not mean the service is run by Amazon, and it does not promise every advanced feature is identical. For the full explanation, see What S3-Compatible Really Means.
For common S3 operations, the custom endpoint is the portability layer. Once your tool can set that endpoint, the provider becomes much easier to swap.
How Blober Connects to Any of These
Section titled "How Blober Connects to Any of These"Blober has preconfigured connectors for the most common S3 services (Amazon S3, Wasabi, Cloudflare R2, Backblaze B2, DigitalOcean Spaces, and Rabata). For everything else on this list, Blober has a single generic S3-Compatible connector: you paste the endpoint URL and keys, and Blober can use the common browse, upload, download, copy, and delete operations when the provider implements them.
That connector covers both addressing styles (bucket in the subdomain, or bucket in the path), single-bucket or full-account access, a custom region, and a free-text storage class, so it reaches the long tail of providers, self-hosted servers, and local test setups. You point Blober at a source and a destination and it copies between them directly, without staging a full copy on your disk.
The Six Categories
Section titled "The Six Categories"| Category | What is in it | Open the list |
|---|---|---|
| Cloud object storage | S3 services from large platform clouds (Alibaba, Tencent, Huawei, IBM, Oracle, Google, Yandex, and more) | Cloud providers |
| Object storage specialists | Independent clouds built only for object storage (Wasabi, Backblaze, Storj, IDrive e2, Cubbit, and more) | Specialists |
| Hosting and VPS object storage | S3 storage bundled with a hosting or VPS platform (DigitalOcean, Linode, Vultr, OVHcloud, Hetzner, Scaleway, and more) | Hosting and VPS |
| Self-hosted and open source | S3 servers you run yourself (MinIO, Ceph, SeaweedFS, Garage, and more) | Self-hosted |
| Enterprise and on-premises | Appliances and enterprise platforms (NetApp StorageGRID, Dell ECS, Cloudian, Pure FlashBlade, and more) | Enterprise |
| Decentralized and Web3 | Object storage backed by decentralized networks (Storj, Filebase, 4everland, and more) | Decentralized |
Master Index of S3-Compatible Providers
Section titled "Master Index of S3-Compatible Providers"Every provider, alphabetical, with its endpoint format. The endpoint is the host you give your S3 client; the bucket name is then added either as a subdomain or in the path. Replace any bracketed value (<region>, <account>, <namespace>) with your own. A check in the last column means Blober ships a preconfigured connector; everything else uses the generic S3-Compatible connector. When you enter one of these in Blober, include the URL scheme, for example https://s3.example.com.
| Provider | Endpoint format | Preconfigured |
|---|---|---|
| Alibaba Cloud OSS | oss-<region>.aliyuncs.com | |
| Amazon S3 | s3.<region>.amazonaws.com | Yes |
| Apache Ozone | self-hosted S3 Gateway | |
| ArvanCloud | s3.<region>.arvanstorage.ir | |
| Backblaze B2 | s3.<region>.backblazeb2.com | Yes |
| Baidu AI Cloud BOS | s3.<region>.bcebos.com | |
| BizflyCloud | <region>.ss.bfcplatform.vn | |
| Ceph (RADOS Gateway) | self-hosted | |
| China Mobile Ecloud EOS | eos-<city>-1.cmecloud.cn | |
| China Telecom CTYun OOS | oos-<region>.ctyunapi.cn | |
| Cloudflare R2 | <account>.r2.cloudflarestorage.com | Yes |
| Cloudian HyperStore | appliance or software | |
| cloudscale.ch | objects.<region>.cloudscale.ch | |
| Contabo Object Storage | <region>.contabostorage.com | |
| Cubbit DS3 | s3.cubbit.eu | |
| DataCore Swarm | on-premises | |
| Dell ECS / ObjectScale | on-premises | |
| DigitalOcean Spaces | <region>.digitaloceanspaces.com | Yes |
| DreamHost DreamObjects | objects-<region>.dream.io | |
| Exaba | self-hosted | |
| Exoscale SOS | sos-<zone>.exo.io | |
| Fastly Object Storage | <region>.object.fastlystorage.app | |
| FileLu S5 | s5lu.com | |
| Filebase | s3.filebase.io | |
| 4everland | endpoint.4everland.co | |
| Fuga Cloud Object Store | core.fuga.cloud | |
| Garage | self-hosted | |
| Gcore Object Storage | regional endpoint | |
| Google Cloud Storage | storage.googleapis.com | |
| Hitachi Content Platform | on-premises | |
| Hetzner Object Storage | <region>.your-objectstorage.com | |
| Huawei Cloud OBS | obs.<region>.myhuaweicloud.com | |
| IBM Cloud Object Storage | s3.<region>.cloud-object-storage.appdomain.cloud | |
| IDrive e2 | <region>.idrivee2-XX.com | |
| Impossible Cloud | <region>.storage.impossibleapi.net | |
| Infomaniak Public Cloud | s3.<region>.infomaniak.cloud | |
| Intercolo Object Storage | de-fra.i3storage.com | |
| IONOS Cloud S3 | s3-<region>.ionoscloud.com | |
| JD Cloud Object Storage | s3.<region>.jdcloud-oss.com | |
| Kingsoft Cloud KS3 | ks3-<region>.ksyuncloud.com | |
| Leaseweb Object Storage | regional endpoint | |
| Leviia | s3.leviia.com | |
| Liara | storage.iran.liara.space | |
| Linode / Akamai | <region>.linodeobjects.com | |
| MEGA S4 | s3.<region>.s4.mega.io | |
| MinIO | self-hosted | |
| NAVER Cloud Object Storage | <region>.object.ncloudstorage.com | |
| NetApp StorageGRID | on-premises | |
| NetApp ONTAP S3 | on-premises | |
| Netease NOS | nos-<region>.126.net | |
| Nutanix Objects | on-premises | |
| OpenIO | self-hosted | |
| OpenStack Swift (s3api) | self-hosted | |
| Open Telekom Cloud OBS | obs.<region>.otc.t-systems.com | |
| Oracle Cloud OCI | <namespace>.compat.objectstorage.<region>.oci.customer-oci.com | |
| Outscale OOS | oos.<region>.outscale.com | |
| OVHcloud Object Storage | s3.<region>.io.cloud.ovh.net | |
| Petabox | s3.<region>.petabox.io | |
| Pure Storage FlashBlade | on-premises | |
| Qiniu Kodo | s3-<region>.qiniucs.com | |
| Quantum ActiveScale | on-premises | |
| Rabata | s3.<region>.rabata.io | Yes |
| RackCorp | <region>.s3.rackcorp.com | |
| Riak CS | self-hosted | |
| Scality RING / ARTESCA | on-premises | |
| Scaleway Object Storage | s3.<region>.scw.cloud | |
| Seagate Lyve Cloud | s3.<region>.<account>.lyve.seagate.com | |
| SeaweedFS | self-hosted | |
| Selectel | s3.<region>.storage.selcloud.ru | |
| Servercore | s3.<region>.storage.selcloud.ru | |
| SberCloud OBS | obs.<region>.hc.sbercloud.ru | |
| Spectra Logic BlackPearl | on-premises | |
| Storadera | <region>.s3.storadera.com | |
| Storj | gateway.storjshare.io | |
| Synology C2 | <region>.s3.synologyc2.net | |
| Tebi | s3.tebi.io | |
| Telnyx Cloud Storage | <region>.telnyxcloudstorage.com | |
| Tencent Cloud COS | cos.<region>.myqcloud.com | |
| Tigris | t3.storage.dev | |
| UpCloud Object Storage | <region>.upcloudobjects.com | |
| US3 (UCloud) | s3-<region>.ufileos.com | |
| VAST Data | on-premises | |
| Versity Gateway | self-hosted | |
| VK Cloud Object Storage | hb.bizmrg.com | |
| Vultr Object Storage | <region>.vultrobjects.com | |
| Wasabi | s3.<region>.wasabisys.com | Yes |
| Yandex Object Storage | storage.yandexcloud.net | |
| Zadara | <vsa-id>.zadarazios.com | |
| Zata | idr01.zata.ai |
This index is a starting point. Providers add regions and change hostnames over time, so always confirm the exact endpoint in your provider's console before you connect. The detailed group articles explain each provider's regions, addressing style (path or subdomain), and any quirks.
Subdomain vs Path: The One Setting That Trips People Up
Section titled "Subdomain vs Path: The One Setting That Trips People Up"S3 supports two ways of putting the bucket name into the request:
- Virtual-hosted (bucket in the subdomain):
https://my-bucket.s3.example.com. This is the AWS default and what most hosted providers expect. - Path-style (bucket in the path):
https://s3.example.com/my-bucket. This is what MinIO, Ceph, and most self-hosted servers expect.
If browsing or uploads fail against a self-hosted server, switch to path-style. In Blober, you pick the style implicitly by which endpoint field you fill in. Everything else is the same.
Frequently Asked Questions
Section titled "Frequently Asked Questions"How many S3-compatible storage providers are there? There is no official registry. This page indexes more than ninety well-known hosted providers, hosting platforms, self-hosted servers, enterprise systems, and decentralized gateways across six categories.
Is Azure Blob Storage S3-compatible? Not natively. Azure Blob uses its own API. The concepts map across (a container is like a bucket, a blob like an object), but an S3 tool needs a translation layer to talk to it. See How to Transfer AWS S3 to Azure Blob for moving data between the two.
Can I move data between two different S3-compatible providers? Yes. Because they share the core API, moving between them is usually a straightforward copy. Blober connects to a source and a destination and transfers directly between them. Check provider-specific feature gaps if your workflow depends on object lock, lifecycle, metadata edge cases, or server-side copy.
Do I need a preconfigured connector, or does the generic one work? The generic S3-Compatible connector works with S3-compatible endpoints that support the common operations Blober uses. The preconfigured connectors (S3, Wasabi, R2, B2, Spaces, Rabata) just save you from pasting the endpoint.
Which S3-compatible provider is the cheapest? It depends on your access pattern. Flat-rate, zero-egress providers win for data you read often; the lowest per-GB storage rate wins for cold archives. The pricing model (egress fees and minimum storage duration) usually matters more than the headline storage rate.
Related Guides
Section titled "Related Guides"- What S3-Compatible Really Means
- Azure Blob Tiers vs AWS S3 Storage Classes
- S3-Compatible Connector Setup
- How to Switch Wasabi to Backblaze B2
- How to Transfer AWS S3 to Azure Blob
Get Blober
Section titled "Get Blober"Connect to S3-compatible stores on this list and move data between them directly, without filling your local disk. Blober handles S3, Wasabi, R2, B2, Spaces, Rabata, and generic S3 endpoints by URL, plus non-S3 services like Azure Blob, Dropbox, and Google Drive.