Running on Wasabi?

Wasabi minimum retention or S3 errors biting? We unstick it.

A batch delete that was meant to clean up a stale bucket has produced a surprise charge because Wasabi's minimum storage retention was not understood, a client that works against S3 keeps failing with 400 Bad Request against the Wasabi endpoint, and the rclone job that migrated the archive has stalled a third of the way through. We read the billing anomalies, work out which S3 compatibility detail has shifted, and bring the storage tier back to a state that reads cleanly.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

wasabi-s3.log

still broken

What it is

Wasabi at a glance

Wasabi is a US-based object storage company founded in 2015 by David Friend and Jeff Flowers, the same pair behind Carbonite. It runs a hot, S3-compatible object store across a growing set of regions in North America, Europe and Asia-Pacific, at a flat per-terabyte price with no egress or API-call charges. The pitch is deliberately simple: cheaper than S3, free egress, same API, no tiers to reason about.

Wasabi is popular as a backup destination, a media archive and a Cloudflare-fronted content store. The S3 compatibility is close but not perfect, and the business model has two quirks that trip teams up regularly: a 90-day minimum storage charge on every object that discourages churn, and bucket-level naming rules that differ subtly from AWS. Trouble in production usually involves S3 clients that assume AWS-specific behavior, lifecycle rules that interact badly with Compliance or Governance Object Lock, incomplete multipart uploads that silently accumulate on the bill, and migrations whose throughput expectations do not match the real transfer path.

Type
Hot object storage with S3-compatible API, flat pricing
First released
2017 (general availability)
License
Proprietary service, open-source SDKs and compatible tooling
Maintained by
Wasabi Technologies, Inc.
Typically used for
Backup destinations, media archives, content delivery behind a CDN, long-term retention, hybrid primary and secondary storage

The honest version

Wasabi pros and cons

No technology is all upside. This is where Wasabi earns its place and where it tends to cause trouble.

Where Wasabi is strong

  • Flat per-terabyte pricingNo separate storage class, no tiering, no egress fees, no API call charges. The invoice is close to what the capacity meter says the account is holding.
  • No egress fees, within fair useA bucket that is read as much as it is written does not add a second large line item to the bill, which changes the economics of restore testing and CDN origin fronting.
  • S3-compatible APIExisting SDKs, Terraform providers, aws s3 commands and rclone configurations work against Wasabi with a different endpoint, which keeps most migrations short rather than a rewrite.
  • Compliance and Governance Object LockWORM retention through Object Lock is a first-class feature, with Compliance mode for workloads where even root cannot shorten a retention period. Useful for regulated backups and legal hold.
  • Multiple global regionsRegions across the US, Europe and Asia-Pacific mean data residency choices for most customer bases without a second provider.
  • Reasonable throughput for a secondary tierWasabi is designed as hot storage, so restores and media reads come back at speeds comparable to other S3-style stores, rather than at the pace of a true cold archive.

Where Wasabi bites

  • The 90-day minimum storage charge is a real costAn object deleted before 90 days is still billed for the full 90 days. Workloads that write short-lived data to Wasabi can produce bills that feel like a bug and are not.
  • S3 compatibility has sharp edgesSigning details, bucket naming, some lifecycle semantics and specific multipart edge cases differ enough to break automation that silently assumed AWS behavior.
  • No managed services around the storageThere is no Lambda, no queue, no database and no managed CDN. Wasabi is deliberately just storage, and surrounding stacks live elsewhere and treat it as a tier.
  • Compliance mode cannot be undoneAn Object Lock retention set in Compliance mode cannot be shortened, by anyone, until it expires. Misconfigured retention has a cost in dollars and wall-clock calendar time.
  • Access keys do not expire unless managedApplication Access Keys are created without an expiry. A key that leaked into a repository two years ago is still live until someone rotates it.
  • Status and support cadence variesIncidents are usually handled well and sometimes announced later than customers would like. Support reaches real engineers; response time at odd hours is not hyperscaler enterprise speed.

Sound familiar?

Common Wasabi problems we fix

The Wasabi problems that bring people to us, and what you have once each one is fixed.

TooManyBuckets, limit 1000

Bucket creation is failing at the account cap

A design that created a bucket per customer or per project that has crossed the limit. Raising the ceiling helps temporarily; the sustainable fix is usually consolidating into fewer buckets with prefixes.

Bucket plan consolidated to real tenancy

object deleted before 90-day minimum

Bills are higher than storage suggests

A workload writing and deleting short-lived objects on Wasabi, incurring early-delete charges that are not obvious in the usage dashboard. Over a month those charges can dwarf the storage line.

Short-lived data routed off Wasabi

SignatureDoesNotMatch

S3 clients cannot sign requests against Wasabi

A region or endpoint copied from AWS, a client assuming path-style vs virtual-hosted-style access, or clock skew. Wasabi checks signatures strictly and the error is easy to misread.

Endpoint, region and signing style aligned

multipart upload: 14 incomplete parts

Incomplete multipart uploads are being billed

A job that aborted without cleaning up its parts, so chunks sit in the bucket invisible to listings but very much on the bill. A lifecycle rule to expire incomplete uploads is not on by default.

Lifecycle for incomplete multiparts in place

lifecycle expiration conflicts with Object Lock

Lifecycle rules do not delete as expected

An expiration rule that is prevented from firing because Object Lock retention has not yet elapsed. The console says the rule is active, and nothing actually goes away.

Lifecycle and Object Lock reconciled

rclone InvalidArgument during migration

Large migrations stall mid-way

A multi-terabyte migration whose part size, concurrency or multipart threshold does not match Wasabi's limits, so a specific object fails and the whole job stops at the error.

Transfer settings tuned to Wasabi

Access Key still active after 2 years

Credentials have not been rotated in years

Long-lived Application Access Keys that never expired, sometimes referenced in deploys that nobody owns anymore, sometimes checked into forgotten repositories.

Keys rotated and scoped

503 SlowDown

A region returns transient throttling

A region under load, or a workload pushing more concurrent requests than the account's rate budget. Clients without retry and backoff surface the error to users or fail batch jobs.

Backoff and concurrency inside limits

What we do

Wasabi help, from migration to steady running

Call us for one failing migration, or let us own the whole secondary-storage tier.

Migration onto Wasabi
Moving backups, archives or media buckets from S3, GCS or Azure Blob to Wasabi with aws s3 sync or rclone, honoring Object Lock intent and avoiding the 90-day trap.
S3 compatibility fixes
Clients and SDKs that work on AWS and fail on Wasabi brought into alignment by addressing endpoint, region, signing style and multipart settings.
Backup and retention design
Buckets, prefixes, lifecycle rules and Object Lock mode chosen deliberately so backups hold the right length, restores run cleanly, and bills do not surprise.
Cost review
Usage, incomplete multipart parts, early-delete charges and bucket count reviewed against the real access pattern, with a before and after estimate.
CDN and Cloudflare integration
Wasabi as a cheap origin behind Cloudflare or another CDN, with cache rules, signed URLs and failover paths so content serves fast without spiking egress.
Managed Tech
Key rotation, lifecycle verification, restore drills and someone to page when throttling climbs during a scheduled backup.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Wasabi alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Wasabi questions

Something else? Call+1 737 727 7327

Should we move our backups from S3 to Wasabi?

For infrequently-churning backups and archives, often yes. The flat storage price and the lack of egress fees dominate the bill above a few terabytes. For hot application data that lives close to AWS compute or depends on S3 features like Transfer Acceleration or specific IAM conditions, Wasabi is a worse fit. We model the real bill on both sides before recommending the move.

Why is our Wasabi bill higher than the storage dashboard suggests?

Usually one of three things. Objects deleted before the 90-day minimum still incur charges to the 90-day mark, so a write-heavy workload with short retention can pay for data it no longer holds. Incomplete multipart uploads accumulate invisibly and are billed until a lifecycle rule expires them. And bucket counts beyond the default produce support costs rather than storage costs, but they feel the same when a procurement report lands.

Why does our S3 SDK work on AWS and fail on Wasabi?

Usually an endpoint, region or signing-style mismatch. Wasabi uses region names like us-east-1, us-east-2 and eu-central-1 that overlap with AWS names but point at a different endpoint. Some SDKs default to virtual-hosted-style URLs that Wasabi handles slightly differently. We work the client configuration until the compatibility edges stop biting and write down what the correct settings should be for every environment.

Should we use Compliance or Governance mode for Object Lock?

Compliance mode is for workloads where the retention period legally must not be shortened by anyone, including account root. That is powerful and irreversible. Governance mode allows a privileged role to lift a retention, which is often what is actually wanted. We help teams match the legal or policy requirement to the right mode rather than picking Compliance by default and regretting it a year later.

Can you take over a Wasabi account from a previous team?

Yes. We inventory buckets, Access Keys and lifecycle rules, rotate every key, test that restores actually succeed from the current state, and bring the account under Terraform or a documented runbook so the handover is complete rather than hopeful.

How much does Wasabi help cost?

The quote is free. Send us the bucket layout, which clients talk to it and what is going wrong, and we return a fixed price before any changes touch the account.

Free estimate

Wasabi giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.