Manage Iceberg REST catalog resources

Lakehouse for Apache Iceberg lets you manage the Apache Iceberg REST catalog endpoint within the Lakehouse runtime catalog. You can use the Google Cloud console or the REST API to create, configure, and monitor these catalogs to establish the metadata layer required for query engine connections.

Before you begin

  1. Verify that billing is enabled for your Google Cloud project.

  2. Enable the BigLake API.

    Roles required to enable APIs

    To enable APIs, you need the Service Usage Admin IAM role (roles/serviceusage.serviceUsageAdmin), which contains the serviceusage.services.enable permission. Learn how to grant roles.

    Enable the API

Required roles

To get the permissions that you need to use the Lakehouse runtime catalog, ask your administrator to grant you the following IAM roles on your project:

For more information about granting roles, see Manage access to projects, folders, and organizations.

You might also be able to get the required permissions through custom roles or other predefined roles.

Management actions

You can perform the following management actions on your Apache Iceberg REST catalog resources using the Google Cloud console or the REST API:

  • Create a catalog: Create an Apache Iceberg REST catalog management endpoint pointing to an underlying Cloud Storage bucket warehouse (CreateIcebergCatalog).
  • Create a namespace: Create a namespace within an Iceberg REST catalog to group related tables (CreateIcebergNamespace).
  • Enable credential vending: Switch an existing catalog's authentication method to credential vending mode to vend short-lived storage tokens directly to query engines (UpdateIcebergCatalog).
  • Get catalog details: View properties and metadata for your catalog, including the REST catalog URI required for client connections (GetIcebergCatalog).
  • Delete a catalog: Unregister a catalog metadata management endpoint from the Lakehouse runtime catalog (DeleteIcebergCatalog).
  • Delete a namespace: Delete a namespace from your Iceberg REST catalog when it is no longer needed (DeleteIcebergNamespace).
  • View audit logs: Inspect Cloud Audit Logs for verifiable records of administrative and data access activities.

Pricing

For pricing details, see Lakehouse for Apache Iceberg pricing.

What's next

Learn more about the Apache Iceberg REST catalog endpoint.