Skip to main content
The Google BigLake integration in Elementary allows you to automatically monitor volume & freshness anomalies in your Iceberg tables managed by a BigLake Metastore catalog, by continuously syncing metadata about Iceberg snapshots.
BigLake Iceberg is only supported for BigQuery environments. The same service account used for your BigQuery warehouse connection is reused — no separate credentials are required.

​
GCP Setup

​
1. Grant additional IAM roles

Elementary reuses the service account that is already connected to your BigQuery environment. You only need to grant three additional roles to that service account: On the GCP project that owns the BigLake catalog:

​
2. Scope the Storage Object Viewer role to metadata files only

For security, restrict the Storage Object Viewer role to Iceberg metadata files rather than granting access to all objects in the bucket. When assigning the role on the GCS bucket, add a condition:
This ensures the service account can only read *.metadata.json files — the Iceberg snapshot metadata — and nothing else in the bucket.

​
Elementary Configuration

Navigate to Account settings > Environments, choose your BigQuery environment, and scroll to the Metadata Layer section. Select BigLake.

​
Connection Settings