How-to guideApplies to: Unified engine deployments
Use a Google runtime identity to authenticate to the BigLake Iceberg REST API.
Before you start
Use an existing catalog with at least one readable Iceberg table. The engine and
workers must reach the catalog and its table storage. Have the remote identity
and permissions ready before creating the Unified registration. Replace the
namespace and table with one you know has data.
Application default credentials must be available where the credential service
runs. Grant the identity the required BigLake, billing-project, and
table-storage access. The server must provide supported storage access for the
selected table.
Values to collect
- BigLake REST URI, warehouse, billing project ID, namespace, and table.
Run the SQL
Replace every <placeholder> before running. Use unused names for the resources
below. Run the statements in order in Workbench.
Check the result
The SELECT should return up to five rows from the chosen table. Use a nonempty
table for this check. This verifies both metadata and table-file access;
creating the registration alone does not verify either.
The billing project is a catalog request setting. It does not replace the Google
identity or grant that identity permissions.
Clean up
This removes only the Unified registrations. It leaves the remote catalog and
its tables in place.
Last modified on November 4, 2026
