Google Cloud Storage Destination Config Reference Beta
- free
- growth
- enterprise
4 minute read
Google Cloud Storage is an object storage destination. RudderStack batches events and writes them as files into a GCS bucket you own.
In a Google Cloud Storage destination spec:
type: gcsdefinition_version: 1
Sample configuration
version: rudder/v1
kind: destination
metadata:
name: gcs-events-prod
spec:
id: gcs-events-prod
display_name: GCS Events Production
type: gcs
definition_version: 1
enabled: true
config:
bucket_name: rudder-events-prod
prefix: rudder/events
credentials: "{{ .GCS_CREDENTIALS }}"
connection_mode:
web: cloud
cloud: cloud
consent_management:
web:
- provider: oneTrust
consents:
- analyticsThe above example supplies the service account key through a variable, which is how you should always set credentials — see Secrets.
Config keys
config accepts only the keys listed below. The shared config key rules cover unknown keys, defaults, and immutability.
Bucket
bucket_name
RequiredType:
string
Description: Name of the GCS bucket RudderStack writes event files to. The bucket must already exist.
Notes:
- At most 100 characters, and must not contain line breaks.
- A
{{ path || fallback }}template is accepted in place of a literal, and isn’t measured against the length limit.
prefix
Type:
string
Description: Folder prefix inside the bucket. RudderStack writes all files beneath it.
Notes:
- At most 100 characters, and must not contain line breaks.
- Templates are accepted on the same terms as
bucket_name.
Authentication
credentials
SecretType:
string
Description: Contents of the JSON key file for a GCP service account that can create objects in the bucket.
Notes:
- Rudder CLI doesn’t require this key and doesn’t validate its content.
Supply it as a {{ .VAR }} reference rather than a literal — see Secrets.
See Setting up Google Cloud Storage for how to create the service account and its key.
Per-source keys
Both keys are objects keyed by the local source type — the tokens listed under Source types. A key naming a source type this destination doesn’t support fails validation.
connection_mode
Type:
object
Description: Maps each source type you connect to the mode its events reach GCS in, using the modes in Source types.
Notes:
- An entry is required for each source type you connect — see Connect a source.
connection_mode:
web: cloud
cloud: cloudconsent_management
Type:
object
Description:
Consent provider configuration per source type. The entry shape, accepted providers, and the rules on resolution_strategy and consents are shared across all destination types — see Consent management.
Source types
Google Cloud Storage accepts events from these source types in the mentioned connection modes:
| Source type | Connection mode |
|---|---|
android | cloud |
android_kotlin | cloud |
ios | cloud |
ios_swift | cloud |
web | cloud |
unity | cloud |
react_native | cloud |
flutter | cloud |
cordova | cloud |
cloud | cloud |
Every source type is cloud only — events reach the bucket from RudderStack’s servers, never in device mode.
The dashboard additionally offers Google Cloud Storage to AMP, Shopify, and Reverse ETL sources. Rudder CLI doesn’t manage those connections, soamp,shopify, andwarehouseare invalid here.
Connect a source
An event stream connection to this destination is checked against two rules at validate time.
The source’s type must be supported. A source’s type resolves to one of the tokens above before the check — a JavaScript source resolves to web, and webhook and server-side SDK sources resolve to cloud. An unsupported type reports:
destination 'gcs-events-prod' (type 'gcs') does not support source 'my-source':
source type 'amp' is not among supported source types: android, android_kotlin, ...The destination config must carry a connection_mode entry for that source type. This lives on the destination spec, not on the connection spec. Without it:
destination 'gcs-events-prod' config has no 'connection_mode' entry for source type 'web'Google Cloud Storage needs no additional config keys to connect a source of any type.
Secrets
credentials is the only secret key. Write it as a {{ .VAR }} reference and supply the value at apply time:
config:
credentials: "{{ .GCS_CREDENTIALS }}"export RUDDER_GCS_CREDENTIALS="$(cat service-account.json)"
rudder-cli apply
# or
rudder-cli apply --var-file secrets.vars.yamlNote that:
- The YAML that
rudder-cli importwrites may or may not include secret keys. Before you apply, make sure every secret key your configuration needs is present and populated through variable substitution.
See How to Use Variable Substitution in Rudder CLI.
See more
- Google Cloud Storage Destination for bucket and service account setup
- Destination Type Reference for Rudder CLI for the rules shared across destination types
- Destination YAML Reference for the spec envelope