Backblaze B2
Backblaze B2 exposes an S3-compatible API alongside its own native one. The catch is the endpoint: it carries a cluster identifier that differs between accounts, so the generic pattern is only a starting point — the exact value is printed in your bucket details.
Connection settings
- Endpoint
- https://s3.{region}.backblazeb2.com
- Default region
- us-west-004
- Addressing
- Virtual-hosted
- Temporary credentials
- Not applicable
A filled-in example
Every value below is fabricated — they are shaped like real Backblaze B2 credentials so you can recognise yours, and they authenticate nothing.
- Endpoint
- https://s3.us-west-004.backblazeb2.com
- Region
- us-west-004
- Access key
- 005example0b2keyid000001
- Secret key
- K005EXAMPLEapplicationKeyDoNotUse00
- Addressing
- Virtual-hosted
In the B2 console the keyID is your access key and the applicationKey is your secret — they are labelled differently from every other provider here.
Where each value comes from
Endpoint
Format: https://s3.{region}.backblazeb2.com — The exact endpoint (including cluster ID) is shown in your B2 bucket details.
Credentials
In B2 Console → App Keys, create a new application key. The keyID is your Access Key, the applicationKey is your Secret Key.
Notes
Each bucket shows its specific S3 endpoint in the console. B2 supports both virtual-hosted and path-style addressing.
What usually goes wrong
The cluster number is part of the region
us-west-004 is not a typo of us-west-2. The trailing digits identify the storage cluster your account lives on, and they differ between accounts created at different times. Copy the endpoint from your bucket page rather than guessing.
The application key is shown once
B2 displays the applicationKey at creation and never again. If it was not saved, the key has to be deleted and recreated — there is no way to reveal it afterwards.
Master keys cannot be scoped
The account master key works but grants everything. For a client you leave connected, create a per-bucket application key instead; B2 lets you restrict both the bucket and the prefix.
Regions available in the app
us-west-004eu-central-003