Backblaze B2
Connect Backblaze B2 buckets to BucketMate Web with the S3-compatible API
BucketMate Web connects to Backblaze B2 through its S3-compatible endpoint. Make sure the companion browser extension is connected before testing the connection.
Prerequisites
- Backblaze account
- B2 bucket
- Application Key ID
- Application Key
- Bucket region
- BucketMate browser extension
Endpoint and region
Use the endpoint for your B2 region:
https://s3.<region>.backblazeb2.com
Examples:
| Region | Endpoint |
|---|---|
us-west-000 | https://s3.us-west-000.backblazeb2.com |
us-west-001 | https://s3.us-west-001.backblazeb2.com |
us-west-002 | https://s3.us-west-002.backblazeb2.com |
us-east-005 | https://s3.us-east-005.backblazeb2.com |
eu-central-003 | https://s3.eu-central-003.backblazeb2.com |
Connection steps
- Open the Backblaze dashboard.
- Create or copy an application key for the target bucket.
- Open BucketMate Web.
- Confirm the extension bridge is connected.
- Choose Add Connection.
- Select Backblaze B2.
- Enter the endpoint for the bucket region.
- Enter the application key ID as the access key ID.
- Enter the application key as the secret access key.
- Select the matching region.
- Use Test Connection.
- Save the connection.
Common issues and fixes
Bucket naming rules differ
Backblaze naming rules differ from AWS S3. Fix by following Backblaze naming rules before creating or connecting buckets.
ACL support is limited
Only private and public-read ACLs are supported. Fix by using those values only and avoid object-level ACL calls.
Object tagging is not supported
Object tagging APIs are not implemented. Fix by storing tags in object metadata or your application database.
Bucket list permission is restricted
If the application key is limited to one bucket, add that bucket name in Explicit Buckets.
Public URLs do not work
Private B2 buckets need presigned links. Direct copied object URLs work only for objects that are publicly reachable.