Backblaze B2 bucket

Words you’ll see

Bucket

A storage container for files at a storage provider, like a top-level folder in the cloud. Your app’s uploads go into it.

Access key ID and secret access key

A pair of values that works like a username and password for programs. The ID can be shown; the secret is shown once when you create it.

Endpoint

The web address Claspine uses to reach your storage provider, such as https://s3.us-east-1.amazonaws.com.

Region

The part of the world where the provider runs your service, such as us-east-1 (Virginia) or europe-west4 (Netherlands). Use the region where you set things up.

CORS

A browser safety setting on the bucket that says which websites may upload or download directly. Without it, browsers block uploads from your app.

Steps

1. In Backblaze, open Buckets → Create a Bucket, keep it Private, and create it.
2. Note the bucket’s Endpoint shown in its details (for example s3.us-west-004.backblazeb2.com).
3. Open Application Keys → Add a New Application Key. Allow access to this bucket only with Read and Write.
4. Copy the keyID and applicationKey. The application key is shown only once.
5. Add a CORS rule on the bucket for your app’s web address (bucket settings → CORS Rules).
6. Open the Claspine console, choose your project and go to File Storage.
7. Pick this provider in the list, then fill in the fields as shown in “What goes where in Claspine” below.
8. Click Save & test. Claspine writes one tiny test file into your bucket, reads it back and deletes it. A green result means everything is connected.

What goes where in Claspine

Keep it safe

• A key limited to one bucket cannot touch your other buckets.

Claspine stores the values encrypted, never shows them again in full, and never sends them to your app or SDK.

Provider documentation

• Backblaze: application keys

← All setup guides