Google Cloud Storage (GCS) Permissions
Last updated
Was this helpful?
Last updated
Was this helpful?
Configuring Google Cloud Storage (GCS) permissions establishes secure access between and your cloud storage resources. These permissions define how Publisher can interact with your buckets and objects, using service accounts and custom roles to ensure controlled access.
This guide outlines the minimum permissions needed to connect Publisher to specific GCS resources, including credential creation and bucket-level access configuration.
Service Account (SA): This is an identity generated in Google Cloud that can be used to interact with GCP services. Each SA has a unique email (identity) and one or more JSON keys.
Data Project: A project that houses the target dataset.
Quota project: A project that you would like to bill BigQuery to and consume quota resources.
Permission: Granular actions that a user can perform on a given resource.
Role: A collection of permissions typically needed for specific interactions against one or more resources: “Data Viewer,” “Storage Reader,” etc.
Create a new Service Account (SA) in any project.
Generate a new JSON key and download it.
Create a role that has permission to list buckets:
Assign that role to the SA you created in "Creating Credentials":
For each bucket that you want to connect to , assign the Storage Object Viewer policy to the service account: