/// CONNECT A PROVIDER / WASABI
Wasabi
Wasabi is S3-compatible, so you connect it as an access-key Fleet with a custom endpoint. Create a dedicated key in the Wasabi console, point storafleet at the regional endpoint, and you're done.
What you need
- An Access Key and Secret Key generated from the Wasabi console under Access Keys. Create a dedicated key for storafleet rather than reusing a personal one.
- The bucket name and the region the bucket lives in.
- The regional endpoint:
https://s3.<REGION>.wasabisys.com— for example,https://s3.us-east-1.wasabisys.com. The region in the endpoint must match the bucket's region.
Connect the Fleet
From the Fleet page, click Create Fleet and pick Access Keys. Then:
- Enter a display name, the bucket name, and the region.
- Paste the Access Key and Secret Key.
- Set the endpoint to
https://s3.<REGION>.wasabisys.comwith your region. - Click Connect Fleet. storafleet uses path-style addressing against Wasabi, so bucket names are placed in the request path rather than the hostname.
CORS
You don't need to configure CORS for Wasabi. Wasabi automatically serves a permissive CORS response for objects and does not expose a PutBucketCors API, so there is nothing to set up on the bucket. Browser uploads and downloads through storafleet work out of the box.
Billing minimums
Wasabi has billing minimums that make it best suited for data you keep around. Be aware of all three before you connect:
- 90-day minimum storage duration — objects deleted before 90 days are still billed for the remainder of that window.
- 4 KB minimum object size — objects smaller than 4 KB are billed as 4 KB.
- 1 TB account minimum — storage is billed at a 1 TB floor even if you store less.
Supported features
Wasabi supports Object Lock and bucket policies, so retention and access controls behave the way you'd expect on S3. storafleet exposes these where the connected key has permission to use them.