Skip to content

s3 compatible

3 posts with the tag "s3 compatible"

What S3-Compatible Really Means (and Why It Matters When You Switch)

What S3-compatible means and why it matters when switching providers

What "S3-Compatible" Actually Means

Section titled "What "S3-Compatible" Actually Means"

S3-compatible means a storage service speaks the same API language as Amazon S3. Tools, SDKs, and apps built for S3 work with it without code changes. It does not mean the service is run by Amazon, and it does not promise every feature is identical.

The S3 API became a de facto standard. Once enough tools spoke it, new providers had a choice: invent their own interface and ask everyone to re-tool, or speak S3 and work on day one with the entire existing ecosystem. Most chose S3.

The API Is the Standard, Not the Company

Section titled "The API Is the Standard, Not the Company"

Think of it like a power socket. The plug shape is the standard, and any device with that plug works in the wall, regardless of which utility generates the electricity. S3 compatibility is the plug shape. Backblaze B2, Wasabi, Cloudflare R2, and DigitalOcean Spaces all expose an S3-compatible endpoint, so the same aws s3 commands, the same rclone config, and the same desktop tools point at any of them by changing the endpoint and the keys.

This is the quiet superpower of S3 compatibility: it makes providers swappable. If your app reads and writes through the S3 API, moving from one S3-compatible store to another is mostly a matter of changing the endpoint and the credentials, not rewriting code. That keeps you from being locked in by your tooling, and it means a provider's pricing model or a new egress policy does not trap your data with them.

What Compatibility Does Not Guarantee

Section titled "What Compatibility Does Not Guarantee"

Compatible is not identical. A few things still vary between S3-compatible providers, so check them before you commit:

  • Feature coverage. Lifecycle rules, versioning, object lock, and multipart limits differ. Most common operations are covered; the long tail is not always.
  • Performance and consistency. Throughput, latency, and edge-case consistency behavior are the provider's own.
  • Regions and durability. Where your data physically sits, and how many copies are kept, is a provider decision.
  • The pricing model. Egress and minimum storage duration are where S3-compatible providers differ most, and those terms decide the real cost of an archive far more than the headline storage rate.

Azure Blob Storage uses its own API rather than the S3 API, so it is not S3-compatible in the same drop-in way. The concepts line up (an S3 bucket maps to a container, an object to a blob), but a tool pointed at S3 will not talk to Azure Blob without a translation layer. That is worth knowing if your stack assumes S3 everywhere.

When you do need S3-compatible applications to run against Azure, an S3 gateway sits in front of Azure Blob and converts S3 API calls to Azure Blob calls on the fly:

  • Flexify.IO runs an S3 gateway in front of Azure Blob Storage.
  • s3proxy is an open-source proxy that presents an S3 API backed by Azure Blob and other stores.
  • VersityGW is an open-source S3 gateway with pluggable backends.
  • MinIO is S3-compatible storage that has been used to put an S3 API in front of other backends.

For .NET projects, FluentStorage takes a different route. Rather than a gateway, it is a polymorphic cloud storage abstraction layer, so one codebase targets S3, Azure Blob, and other stores without per-provider code.

Moving Between S3-Compatible Stores

Section titled "Moving Between S3-Compatible Stores"

Because the API is shared, moving data between S3-compatible providers is a clean operation. Blober connects to S3, Backblaze B2, Wasabi, Cloudflare R2, and DigitalOcean Spaces, and its generic S3 connector points at any other S3-compatible endpoint by URL, so a provider it does not list by name still works. It also bridges to non-S3 services like Azure Blob, Dropbox, and Google Drive. You point it at a source and a destination and it copies between them directly, without staging a full copy on your disk.

Is Backblaze B2 S3-compatible? Yes. B2 exposes an S3-compatible API, so S3 tools and SDKs work against it by changing the endpoint and keys.

Is Azure Blob Storage S3-compatible? Not natively. Azure Blob uses its own API. The concepts map across (container for bucket, blob for object), but S3 tools need a translation layer to talk to it.

Does S3-compatible mean exactly the same as AWS S3? No. It means the same API language. Features like lifecycle rules and versioning, plus performance, regions, and the pricing model, vary by provider.

Can I switch S3-compatible providers without changing my app? Usually yes, if your app uses the S3 API. You change the endpoint and credentials. Check that the specific features you rely on are supported by the new provider first.

Switch object-storage providers without the re-tooling headache. Blober moves data between S3, B2, Wasabi, R2, Spaces, and more, directly and without filling your local disk.

Download Blober at blober.io

Rabata.io: Where It Fits and Where It Doesn't

Rabata.io: Where It Fits and Where It Doesn't - benchmarks, pricing, and comparison with AWS, Backblaze, R2, Wasabi, iDrive

Rabata.io is an S3-compatible object storage provider from RCS Technologies (UK) with two products: Hot Storage, general-purpose object storage at $0.01/GB/month in us-east-1, designed for applications, media, and frequently accessed data, and Backup, bulk archival storage at $49/10TB flat in eu-west-2, intended for backups, disaster recovery, and cold data. Both use standard AWS SigV4 authentication, work with any S3 SDK or CLI, and require no code changes to migrate from AWS S3. You swap the endpoint and credentials.

That is the entire product. No compute layer, no managed databases, no dashboard file browser: you cannot preview or view objects through Rabata's web UI, so you need an S3 client or a tool like Blober to actually see what's in your buckets. Just storage with an S3 API.

Rabata published benchmarks using MinIO warp v1.0.7 (released January 2025, now superseded by v1.5.0) on a Debian 13 VM in us-east-1 with 8 concurrent threads in September 2025. The methodology is public.

According to their numbers, Rabata wins upload speed by a small margin (1,462 MB/s vs AWS's 1,444) and mixed operations by 2.3x over AWS. It loses on downloads to both Backblaze (2,075 MB/s) and AWS (1,816), and loses small object throughput to iDrive e2 (962 ops/s vs 696).

The mixed operations number is the most relevant for production workloads. Real applications read, write, list, stat, and delete concurrently. Rabata scored 2.3x higher than AWS S3 in that test.

These are same-region tests (us-east-1 to us-east-1). Performance from other geographies is unknown, and Rabata only operates in two regions. The runs are 30 seconds to 10 minutes with 8 threads, so they measure burst, not sustained multi-TB daily throughput over months. The warp version used (v1.0.7, January 2025) was already 8 months old at the time of testing and is now over a year outdated, and newer versions may produce different results. AWS S3 publishes 99.999999999% durability. Rabata publishes no durability SLA, and their terms include a broad "as is" disclaimer with zero liability for data loss.

Rabata fits a specific profile:

Write-heavy S3 workloads that need to stay cheap. If you're ingesting backup pipelines, media uploads, log aggregation, or AI training data, and your bottleneck is upload throughput plus cost, Rabata's upload speed at $0.01/GB is competitive, roughly 57% less than AWS's $0.023/GB first-tier pricing (AWS discounts at volume).

The Backup tier at $49/10TB ($0.0048/GB) is priced below Backblaze B2 ($6.95/TB, ~$0.007/GB) and Wasabi ($6.99/TB, ~$0.007/GB, increasing to $7.99/TB in July 2026). Wasabi enforces a 90-day minimum retention. Rabata's Backup tier has no documented minimum retention, but note: egress is capped at 2x your storage amount and billing is in 10TB increments rounded up: store 1TB and you pay for 10TB.

GDPR-compliant EU storage. The eu-west-2 Backup tier gives you EU data residency, which Rabata calls out explicitly. Worth noting: Rabata's parent company (RCS Technologies) operates under UK law, not EU law. Hetzner also offers EU-based S3-compatible storage with three EU regions (NBG1, FSN1, HEL1) versus Rabata's single EU region. For European companies that need S3-compatible storage with data residency guarantees, both are worth evaluating.

No-friction evaluation. 30-day trial, no credit card required per Rabata's signup page.

  • Download-heavy workloads. If you're serving content to users, Backblaze B2 (2,075 MB/s downloads, ~$0.007/GB) or Cloudflare R2 ($0.015/GB storage, zero egress, weak throughput but free delivery) are better choices depending on whether you're optimizing for speed or cost.
  • Global distribution. Two regions. If you need worldwide low-latency access, this is not the product.
  • Enterprise compliance requirements. No published durability SLA, no SOC 2 mention, limited public track record, benchmarks not independently verified.
  • Ecosystem depth. No lifecycle policies, no event notifications, no cross-region replication, no versioning (or at least none documented), no dashboard file browser. AWS S3 has all of these. Rabata does not.

Based on Rabata's own benchmarks (no independent verification available), they offer three things at once that no other single provider does:

  1. Fastest mixed workload performance in their published benchmarks
  2. Simple pricing at $0.01/GB with $0.01/GB egress (Backup tier: egress capped at 2x storage)
  3. No-barrier trial with no credit card required

AWS is faster on downloads but 2-3x more expensive. Backblaze is comparable on storage (~$0.007/GB) but slower on uploads. Cloudflare R2 has zero egress but performs 3-8x worse. Wasabi has no egress fees but enforces 90-day minimums. iDrive wins on small objects but falls behind on mixed workloads.

If your workload is "ingest data via S3 API, store it cheaply, occasionally read it back," Rabata is worth testing. If your workload needs more features, more regions, or a long track record, look elsewhere.

Blober supports Rabata.io as a native provider. Connect with your access key and secret key, and Blober detects your buckets across both regions (Hot Storage and Backup). You can use Rabata as a source or destination in any workflow: migrate to it from AWS S3, sync from Dropbox, back up from Google Drive, or download files from Rabata to your local machine. Since Rabata's dashboard has no built-in file browser, Blober is one of the easiest ways to actually see and manage what's in your buckets.

What Blober supports with Rabata:

  • Browse: list buckets and objects across both regions (something Rabata's own dashboard doesn't offer)
  • Upload: write files to Hot Storage or Backup buckets
  • Download: pull files from Rabata to local storage or stream to another provider
  • Copy/Move: transfer objects between buckets
  • Delete: remove objects

Blober handles the region routing automatically. If a bucket lives in eu-west-2, operations go through the eu-west-2 endpoint. No manual configuration needed.

For setup details, see the Rabata.io provider documentation.

How to Switch from Wasabi to Backblaze B2

Switch from Wasabi to Backblaze B2 with Blober

Two S3-Compatible Providers, Different Tradeoffs

Section titled "Two S3-Compatible Providers, Different Tradeoffs"

Wasabi and Backblaze B2 both position themselves as affordable alternatives to AWS S3. Both are S3-compatible. Both offer low-cost storage. But they have meaningful differences that lead people to switch from one to the other.

Wasabi charges $6.99/TB/month with no egress fees. Sounds perfect, until you read the fine print:

  • 90-day minimum retention. If you delete or overwrite a file within 90 days, you still pay for the full 90 days of storage.
  • Egress is "free" with conditions. Your monthly egress cannot exceed your stored data. If you store 1 TB and download 1.5 TB in a month, Wasabi may contact you about their "reasonable use" policy.
  • No native CDN partnerships. Wasabi does not have bandwidth alliance partnerships like Backblaze does.

Backblaze B2 charges $6.95/TB/month for storage and $0.01/GB for egress. But:

  • Free egress through Cloudflare. Through the Bandwidth Alliance, egress from B2 to Cloudflare is free. If you use Cloudflare as your CDN (many do), egress is effectively $0.
  • No minimum retention. Store and delete whenever you want.
  • Free egress allowance. B2 includes 3x your storage amount in free egress each month. If you store 1 TB, you get 3 TB of free downloads.

For most use cases, Backblaze B2 ends up cheaper or equivalent to Wasabi, with fewer restrictions.

Both Wasabi and Backblaze B2 speak the S3 protocol. This means Blober uses the same underlying S3 operations for both providers, making the transfer clean and predictable.

  1. Connect Wasabi: Add Wasabi as a provider with your Access Key, Secret Key, and region (Wasabi uses region-specific endpoints like s3.us-east-1.wasabisys.com).
  2. Connect Backblaze B2: Add B2 with your Application Key ID and Application Key. Blober auto-detects your bucket regions.
  3. Create a workflow: Source = Wasabi, Destination = B2. Browse your Wasabi buckets, select what to move.
  4. Run: Blober transfers with parallel multipart uploads and automatic resume.
  • Multi-region detection for B2. Backblaze B2 buckets can be in different regions. Blober fetches all buckets via B2's native API to determine the correct region for each, then configures the S3 endpoint accordingly.
  • Region-aware endpoints for Wasabi. Wasabi uses different endpoints per region. Blober maps your chosen region to the correct endpoint.
  • Large file support. Both providers handle multipart uploads. Blober chunks large files and uploads them in parallel.

When migrating from Wasabi, keep in mind the 90-day minimum retention policy. If you uploaded files to Wasabi less than 90 days ago, you will be charged for the full 90 days even after you delete them.

The practical approach:

  1. Transfer everything to Backblaze B2
  2. Wait until the oldest files in Wasabi pass the 90-day mark
  3. Then delete and close the Wasabi account

This avoids paying both Wasabi and B2 for the same data longer than necessary.

WasabiBackblaze B2
Storage per TB/mo$6.99$6.95
Egress per GB$0 (with conditions)$0.01 (free via Cloudflare)
Min retention90 daysNone
Free egress allowanceEqual to storage3x storage
CDN partnershipNoneCloudflare Bandwidth Alliance

One-time purchase. No recurring fees, no per-GB charges.

Download Blober at blober.io