Google Cloud Storage 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.

Service account

In Google Cloud, an account for a program rather than a person. You give it one role and download a key file for 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.

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. Open Cloud Storage and create a bucket. Keep public access prevented.
2. In IAM & Admin → Service accounts, create a service account named spine-storage. Skip the project role step.
3. Back on your bucket’s Permissions tab, click Grant access, add the service account and give it the role Storage Object User. This applies to this bucket only.
4. Open Cloud Storage → Settings → Interoperability and click Create a key for a service account. Pick spine-storage and copy the access key and secret.
5. Set a CORS rule on the bucket for your app’s web address (for example with gcloud storage buckets update gs://your-bucket --cors-file=cors.json).
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

• Granting the role on the bucket, not on the whole project, keeps the key away from 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

• Google Cloud Storage: HMAC keys

← All setup guides