Wasabi
Step-by-step guide to connect Wasabi hot cloud storage to BucketMate Web in your browser with S3-compatible access keys and the regional endpoint.
BucketMate Web connects to Wasabi through its S3-compatible API endpoint for your region. Choose Wasabi as the provider. Make sure the companion browser extension is connected before testing the connection.
Prerequisites
- Wasabi account
- Wasabi bucket
- Access key
- Secret key
- Bucket region
- BucketMate browser extension
Endpoint and region
Use the endpoint for your Wasabi region:
https://s3.<region>.wasabisys.com
Examples:
| Region | Endpoint |
|---|---|
us-east-1 | https://s3.us-east-1.wasabisys.com |
us-east-2 | https://s3.us-east-2.wasabisys.com |
us-central-1 | https://s3.us-central-1.wasabisys.com |
us-west-1 | https://s3.us-west-1.wasabisys.com |
eu-central-1 | https://s3.eu-central-1.wasabisys.com |
ap-northeast-1 | https://s3.ap-northeast-1.wasabisys.com |
Connection steps
- Open the Wasabi console.
- Create or copy access keys.
- Open BucketMate Web.
- Confirm the extension shows Connected in Settings > Advance.
- Choose Add connection.
- Select Wasabi.
- Enter the endpoint for the bucket region.
- Enter the access key and secret key.
- In Region, choose the bucket region, such as
us-east-2. - Use Test Connection.
- Choose Save Connection.
Common issues and fixes
Region mismatch
Use the endpoint and region that match the bucket. A mismatch can cause redirect, signature, or access errors.
Bucket list permission is restricted
If the credentials can access only specific buckets, add those bucket names in Explicit buckets.
Links to private files
Copy URL in BucketMate Web creates a presigned URL that works for 1 hour, so it opens private objects. For longer access, create a share link. Plain object URLs outside BucketMate Web work only for public objects.
Bucket operations fail
Confirm the access key has bucket-level permission before using create, empty, or delete bucket actions.