Connect Wasabi

You need a Wasabi access key and the region your buckets are in.

1. Create an access key

In the Wasabi console, create a user just for quickS3 under Users, and give it a policy that covers only the buckets your team needs. For browsing, uploading, and deleting, it needs to list the bucket and read, write, and delete objects. Wasabi’s policies use the same format as AWS, so the AWS policy example works with your bucket names in it.

Then create an access key for that user and copy both parts. Wasabi only shows the secret once.

2. Add the connection

1. In quickS3, open Connections, select New connection, and pick Wasabi Hot Cloud Storage.
2. Enter a Name.
3. In Region, pick the region your buckets are in, like eu-central-1. quickS3 fills in the endpoint and shows it below the field.
4. Paste the Access key ID and Secret key.
5. If the key can’t list all buckets, type the bucket names into Bucket scopes.
6. Keep CORS updates on and select Connect provider.

Then select Test connection. You want Connection verified with “CORS allows direct uploads”.

Your region is shown next to each bucket in the Wasabi console. A connection only reaches buckets in its own region, so add one connection per region you use.

If uploads are blocked by CORS

Wasabi allows browser uploads for most accounts out of the box. If the test warns about CORS, someone has probably set a stricter CORS rule on the bucket. Open the bucket’s settings in the Wasabi console and add a CORS rule for origin https://quicks3.com with methods GET, HEAD, and PUT, all headers allowed, and ETag exposed. Keep any rules already there, then test again.

Good to know

Wasabi charges for a minimum storage period, even for files you delete early. That’s Wasabi’s billing rule, not a quickS3 limit, so check it before using a Wasabi bucket for short-lived files.