Google Cloud Storage credentials
Which key type a Google Cloud Storage connector takes, and where to create it.
A Google Cloud Storage connector signs in with HMAC keys, not with a service account JSON file. Google Cloud Storage offers an S3-compatible interface, and HMAC keys are the credentials for it. You enter them under Credentials in the New connector or Edit connector dialog of Data connectors, after choosing the protocol Google Cloud Storage. Needs the integration_editor role, or another role your administrator has given access to this area — see Licences and roles.
Fields
| Field | Meaning | Valid values | Default |
|---|---|---|---|
| Bucket (connection) | The bucket to read from or write to. Required. | A bucket name without gs:// | Empty |
| Endpoint (connection) | Only change this for a non-standard endpoint. | https://storage.googleapis.com | That address |
| Access key id | The HMAC access key. Required. | Text | Empty |
| Secret access key | The HMAC secret. Required. | Text | Empty |
Credentials are write-only: once saved they cannot be viewed again, only replaced with Replace credentials. Replacing is complete: enter both keys again, because blank fields are dropped. Clear stored credentials removes them altogether.
How to create the keys
In the Google Cloud console open Cloud Storage → Settings → Interoperability and create an access key for a service account, or run gcloud storage hmac create SERVICE_ACCOUNT_EMAIL. Paste the access key into Access key id and the secret into Secret access key. Give the service account read access to the bucket for an import, and write access for an export.
Examples
A nightly export to gs://acme-exports: set Bucket to acme-exports, leave Endpoint empty, and enter the two HMAC values.
Common problems
- Pasting a service account JSON fails. That file is not accepted. Create HMAC keys instead.
- The connector cannot be saved without a bucket. Bucket is checked when you save, not at the first run.
- Access denied on the first run. The service account lacks permission on the bucket. Use Test connection on the connector's Overview tab to check.
- Keys stopped working. They were deactivated or deleted in Google Cloud. Create new ones and use Replace credentials.