Configuring GCS Cloud Storage

Mon, 01 Jan 0001 00:00:00 +0000

This page provides guidance for configuring GCS Cloud Storage provider for use with Polaris. It covers credential vending, IAM roles, ACL requirements, and best practices to ensure secure and reliable integration.

All catalog operations in Polaris for Google Cloud Storage (GCS)—including listing, reading, and writing objects—are performed using credential vending, which issues scoped (vended) tokens for secure access.

Polaris requires both IAM roles and Hierarchical Namespace (HNS) ACLs (if HNS is enabled) to be properly configured. Even with the correct IAM role (e.g., roles/storage.objectAdmin), access to paths such as gs://<bucket>/idsp_ns/sample_table4/ may fail with 403 errors if HNS ACLs are missing for scoped tokens. The original access token may work, but scoped (vended) tokens require HNS ACLs on the base path or relevant subpath.

Configuring Polaris for Production on Apache Polaris

Configuring GCS Cloud Storage