Connect Google Cloud Storage (GCS) data with any data source.

Create a GCS bucket, or select an existing bucket. The connection check writes, lists, and deletes a probe object. Ensure that retention policies and object holds permit this deletion.

Create a dedicated service account for Airbyte and create an HMAC key for it. If your organization uses the constraints/storage.restrictAuthTypes organization policy, it must allow HMAC authentication. Save the HMAC secret when you create the key because Google Cloud doesn't provide it again.

Grant the service account the Storage Object User role (roles/storage.objectUser) on the bucket. If you use a custom role, include these permissions: text storage.multipartUploads.abort storage.multipartUploads.create storage.objects.create storage.objects.delete storage.objects.list Delete access is required because the connection check deletes its probe object and Full Refresh - Overwrite syncs delete existing objects under the stream's output prefix.

In Airbyte, enter the bucket name, bucket path, bucket region, HMAC access key, HMAC secret, and output format.

Test the connection. If your deployment restricts outbound network traffic, allow access to the GCS XML API endpoint at https://storage.googleapis.com.