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 once you change 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.

The providers are grouped into six categories, and each category page covers its providers in detail: endpoint format, regions, addressing style, and notes.

Endpoint formats come from each provider's own documentation, checked against current S3 client references^[1] and the per-provider sources on the category pages. The tables show only the hostname. In Blober, enter the full URL with https:// unless you are connecting to a local or self-hosted server that explicitly uses http://.

S3-compatible means the service exposes the same HTTP API as Amazon S3, so an S3 client points at it by URL. Amazon doesn't run these services, and advanced features can behave differently from AWS. What S3-Compatible Really Means has the full explanation.

For common S3 operations, the custom endpoint is what makes a tool portable: once your tool can set it, swapping providers gets much easier.

Blober has the most common S3 services built in as their own providers (Amazon S3, Wasabi, Cloudflare R2, Backblaze B2, DigitalOcean Spaces, Rabata, and STRG). For everything else on this list, it has a single generic S3-Compatible provider: 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. Blober also connects to services that don't use S3 at all, such as Azure Blob, Dropbox, and Google Drive.

The generic provider 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, which lets it reach the long tail of providers, self-hosted servers, and local test setups. You choose a source and a destination, and Blober streams each file from one to the other through your computer, so it never keeps a full copy of the bucket on your disk.

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. "Yes" in the last column means the provider is built into Blober. "S3-Compatible" means it connects through the generic S3-Compatible provider. Each one links to its setup guide. When you enter an endpoint in Blober, include the URL scheme, for example https://s3.example.com.

Providers add regions and change hostnames over time, so confirm the exact endpoint in your provider's console before you connect.

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, most self-hosted servers, and a few hosted providers such as American Cloud expect.

If browsing or uploads fail against a self-hosted server, switch to path-style. In Blober, the endpoint field you fill in sets the style, and the rest of the setup is the same.

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.

Why isn't Azure Blob Storage on this list? Azure Blob uses its own API, so S3 tools can't talk to it without a translation layer, even though its containers and blobs map to buckets and objects. 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, and since both sides use the same core API it is usually a plain copy. Blober connects to the source and the destination and copies the files across. If your workflow depends on object lock, lifecycle, metadata edge cases, or server-side copy, check each provider for gaps first.

Do I need a built-in provider, or does the generic S3-Compatible one work? The generic S3-Compatible provider works with S3-compatible endpoints that support the common operations Blober uses. The built-in providers (S3, Wasabi, R2, B2, Spaces, Rabata, STRG) 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, and the lowest per-GB storage rate wins for cold archives. Egress fees and minimum storage duration usually change the bill more than the headline storage rate. Which S3-Compatible Storage Has No Egress Fees? compares the providers that don't bill egress.

• What S3-Compatible Really Means
• Azure Blob Tiers vs AWS S3 Storage Classes
• S3-Compatible Storage Setup Guide
• How to Switch Wasabi to Backblaze B2
• How to Transfer AWS S3 to Azure Blob