Get your keys
- In the Wasabi console, open Access Keys.
- Click Create Access Key and choose whether the key is for the root user or, better, a sub-user.
- Copy the Access Key and Secret Key.
Connect
- Add a new connection and choose the Wasabi preset.
- Paste the keys and pick the region your buckets live in.
- Connect.
Regions
| Region | Endpoint |
|---|---|
| us-east-1 | https://s3.wasabisys.com |
| us-east-2 | https://s3.us-east-2.wasabisys.com |
| us-west-1 | https://s3.us-west-1.wasabisys.com |
| eu-central-1 | https://s3.eu-central-1.wasabisys.com |
| eu-west-1 | https://s3.eu-west-1.wasabisys.com |
| ap-northeast-1 | https://s3.ap-northeast-1.wasabisys.com |
Wasabi has more regions than this table; the pattern is always s3.<region>.wasabisys.com, and the console shows each bucket’s region.
Good to know
- A bucket must be addressed through its own region’s endpoint. Connecting to
us-east-1will not show a bucket created ineu-central-1. - Wasabi bills deleted objects for a minimum storage duration (90 days on most plans). Bulk cleanups in the app work fine, just know they do not immediately reduce the bill.
- Wasabi’s free egress policy assumes your monthly downloads stay below your stored volume; heavy repeated downloading may get flagged on their side.
- Versioning, lifecycle rules and policy editing in the app all work against Wasabi’s S3 implementation.