# Use Iceberg Catalogs > For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [streaming-full.txt](https://docs.redpanda.com/streaming-full.txt) --- title: Use Iceberg Catalogs latest-redpanda-tag: v25.2.1 latest-console-tag: v3.7.3 latest-operator-version: v26.1.4 # EOL = End-of-Life (support lifecycle status) page-is-nearing-eol: "true" page-is-past-eol: "false" page-eol-date: July 31, 2026 latest-connect-version: 4.93.0 docname: iceberg/use-iceberg-catalogs page-component-name: streaming page-version: "25.2" page-component-version: "25.2" page-component-title: Streaming page-relative-src-path: iceberg/use-iceberg-catalogs.adoc page-edit-url: https://github.com/redpanda-data/docs/edit/v/25.2/modules/manage/pages/iceberg/use-iceberg-catalogs.adoc description: Learn how to access Redpanda topic data stored in Iceberg tables, using table metadata or a catalog integration. page-git-created-date: "2025-04-07" page-git-modified-date: "2026-05-26" support-status: nearing end-of-life --- > ๐Ÿ“ **NOTE** > > This feature requires an [enterprise license](https://docs.redpanda.com/streaming/25.2/get-started/licensing/). To get a trial license key or extend your trial period, [generate a new trial license key](https://redpanda.com/try-enterprise). To purchase a license, contact [Redpanda Sales](https://redpanda.com/upgrade). > > If Redpanda has enterprise features enabled and it cannot find a valid license, [restrictions](https://docs.redpanda.com/streaming/25.2/get-started/licensing/#self-managed) apply. To read from the Redpanda-generated [Iceberg table](https://docs.redpanda.com/streaming/25.2/manage/iceberg/about-iceberg-topics/), your Iceberg-compatible client or tool needs access to the catalog to retrieve the table metadata and know the current state of the table. The catalog provides the current table metadata, which includes locations for all the tableโ€™s data files. You can configure Redpanda to either connect to a REST-based catalog, or use a filesystem-based catalog. For production deployments, Redpanda recommends [using an external REST catalog](#rest) to manage Iceberg metadata. This enables built-in table maintenance, safely handles multiple engines and tools accessing tables at the same time, facilitates data governance, and maximizes data discovery. However, if it is not possible to use a REST catalog, you can [use the filesystem-based catalog](#object-storage) (`object_storage` catalog type), which does not require you to maintain a separate service to access the Iceberg data. In either case, you use the catalog to load, query, or refresh the Iceberg table as you produce to the Redpanda topic. See the documentation for your query engine or Iceberg-compatible tool for specific guidance on adding the Iceberg tables to your data warehouse or lakehouse using the catalog. After you have selected a catalog type at the cluster level and [enabled the Iceberg integration](https://docs.redpanda.com/streaming/25.2/manage/iceberg/about-iceberg-topics/#enable-iceberg-integration) for a topic, you cannot switch to another catalog type. ## [](#rest)Connect to a REST catalog Connect to an Iceberg REST catalog using the standard [REST API](https://github.com/apache/iceberg/blob/main/open-api/rest-catalog-open-api.yaml) supported by many catalog providers. Use this catalog integration type with REST-enabled Iceberg catalog services, such as [Databricks Unity](https://docs.databricks.com/en/data-governance/unity-catalog/index.html) and [Snowflake Open Catalog](https://other-docs.snowflake.com/en/opencatalog/overview). > ๐Ÿ’ก **TIP** > > This section provides general guidance on using REST catalogs with Redpanda. For instructions on integrating with specific REST catalog services, see the following: > > - [AWS Glue Data Catalog](https://docs.redpanda.com/streaming/25.2/manage/iceberg/iceberg-topics-aws-glue/) > > - [Databricks Unity Catalog](https://docs.redpanda.com/streaming/25.2/manage/iceberg/iceberg-topics-databricks-unity/) > > - [Snowflake with Open Catalog](https://docs.redpanda.com/streaming/25.2/manage/iceberg/redpanda-topics-iceberg-snowflake-catalog/) ### [](#limitations)Limitations The Iceberg integration for Redpanda Streaming supports multiple Iceberg catalogs, with progressive levels of release maturity. Each catalog integration is tested and released independently. The following shows the current status of Iceberg catalog integrations. Check this list regularly as Redpanda continues to expand GA coverage for Iceberg topics. | Catalog service | Status | | --- | --- | | Databricks Unity Catalog | Supported | | Snowflake Open Catalog | Supported | | AWS Glue Data Catalog | Beta | | Google BigQuery | Beta | Other REST catalogs, such as Apache Polaris, Dremio Nessie (to be [merged with Polaris](https://www.dremio.com/newsroom/polaris-catalog-to-be-merged-with-nessie-now-available-on-github/)), and the Apache reference implementation, have been tested but are not regularly verified. For more information, contact [Redpanda Support](https://support.redpanda.com/hc/en-us/requests/new). ### [](#set-cluster-properties)Set cluster properties To connect to a REST catalog, set the following cluster configuration properties: - `[iceberg_catalog_type](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_catalog_type)`: `rest` - `[iceberg_rest_catalog_endpoint](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_rest_catalog_endpoint)`: The endpoint URL for your Iceberg catalog. You either manage this directly, or you have this managed by an external catalog service. > ๐Ÿ“ **NOTE** > > You must set `iceberg_rest_catalog_endpoint` at the same time that you set `iceberg_catalog_type` to `rest`. #### [](#configure-authentication)Configure authentication To authenticate with the REST catalog, set the following cluster properties: - `[iceberg_rest_catalog_authentication_mode](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_rest_catalog_authentication_mode)`: The authentication mode to use for the REST catalog. Choose from `oauth2`, `aws_sigv4`, `bearer`, or `none` (default). You must use `aws_sigv4` for [AWS Glue Data Catalog](https://docs.redpanda.com/streaming/25.2/manage/iceberg/iceberg-topics-aws-glue/). - For `oauth2`, also configure the following properties: - `[iceberg_rest_catalog_oauth2_server_uri](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_rest_catalog_oauth2_server_uri)`: The OAuth endpoint URI used to retrieve tokens for REST catalog authentication. If left unset, the deprecated catalog endpoint `/v1/oauth/tokens` is used as the token endpoint instead. - `[iceberg_rest_catalog_client_id](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_rest_catalog_client_id)`: The ID used to query the OAuth token endpoint for REST catalog authentication. - `[iceberg_rest_catalog_client_secret](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_rest_catalog_client_secret)`: The secret used with the client ID to query the OAuth token endpoint for REST catalog authentication. - For `bearer`, configure the `[iceberg_rest_catalog_token](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_rest_catalog_token)` property with your bearer token. Redpanda uses the bearer token unconditionally and does not attempt to refresh the token. Only use the bearer authentication mode for ad hoc or testing purposes. For REST catalogs that use self-signed certificates, also configure these properties: - `[iceberg_rest_catalog_trust](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_rest_catalog_trust)`: The contents of a certificate chain to trust for the REST catalog. - Or, use `[iceberg_rest_catalog_trust_file](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_rest_catalog_trust_file)` to specify the path to the certificate chain file. - `[iceberg_rest_catalog_crl](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_rest_catalog_crl)`: The contents of a certificate revocation list for `iceberg_rest_catalog_trust`. - Or, use `[iceberg_rest_catalog_crl_file](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_rest_catalog_crl_file)` to specify the path to the certificate revocation list file. See [Cluster Configuration Properties](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/) for the full list of cluster properties to configure for a catalog integration. ### [](#example-rest-catalog-configuration)Example REST catalog configuration Suppose you configure the following Redpanda cluster properties for connecting to a REST catalog: ```yaml iceberg_catalog_type: rest iceberg_rest_catalog_endpoint: http://catalog-service:8181 iceberg_rest_catalog_authentication_mode: oauth2 iceberg_rest_catalog_oauth2_server_uri: iceberg_rest_catalog_client_id: iceberg_rest_catalog_client_secret: ``` If you use Apache Spark as a processing engine, your Spark configuration might look like the following. This example uses a catalog named `streaming`: ```spark spark.sql.catalog.streaming = org.apache.iceberg.spark.SparkCatalog spark.sql.catalog.streaming.type = rest spark.sql.catalog.streaming.uri = http://catalog-service:8181 spark.sql.catalog.streaming.warehouse = # You may need to configure additional properties based on your object storage provider. # See https://iceberg.apache.org/docs/latest/spark-configuration/#catalog-configuration and https://spark.apache.org/docs/latest/configuration.html # For example, for AWS S3: # spark.sql.catalog.streaming.io-impl = org.apache.iceberg.aws.s3.S3FileIO # spark.sql.catalog.streaming.s3.endpoint = http:// ``` > ๐Ÿ“ **NOTE** > > Redpanda recommends setting credentials in environment variables so Spark can securely access your Iceberg data in object storage. For example, for AWS, use `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. The Spark engine can use the REST catalog to automatically discover the topicโ€™s Iceberg table. Using Spark SQL, you can query the Iceberg table directly by specifying the catalog name, the namespace, and the table name: ```sql SELECT * FROM streaming.redpanda.; ``` The Iceberg table name is the name of your Redpanda topic. Redpanda puts the Iceberg table into a namespace called `redpanda`, creating the namespace if necessary. > ๐Ÿ’ก **TIP** > > You may need to explicitly create a table for the Iceberg data in your query engine. For an example, see [Query Iceberg Topics using Snowflake and Open Catalog](https://docs.redpanda.com/streaming/25.2/manage/iceberg/redpanda-topics-iceberg-snowflake-catalog/). ## [](#object-storage)Integrate filesystem-based catalog (`object_storage`) By default, Iceberg topics use the filesystem-based catalog (`[iceberg_catalog_type](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_catalog_type)` cluster property set to `object_storage`). Redpanda stores the table metadata in [HadoopCatalog](https://iceberg.apache.org/docs/latest/java-api-quickstart/#using-a-hadoop-catalog) format in the same object storage bucket or container as the data files. If using the `object_storage` catalog type, you provide the object storage URI of the tableโ€™s `metadata.json` file to an Iceberg client so it can access the catalog and data files for your Redpanda Iceberg tables. > ๐Ÿ“ **NOTE** > > The `metadata.json` file points to a specific Iceberg table snapshot. In your query engine, you must update your tables whenever a new snapshot is created so that they point to the latest snapshot. See the [official Iceberg documentation](https://iceberg.apache.org/docs/latest/maintenance/) for more information, and refer to the documentation for your query engine or Iceberg-compatible tool for specific guidance on Iceberg table update or refresh. ### [](#example-filesystem-based-catalog-configuration)Example filesystem-based catalog configuration To configure Apache Spark to use a filesystem-based catalog, specify at least the following properties: ```spark spark.sql.catalog.streaming = org.apache.iceberg.spark.SparkCatalog spark.sql.catalog.streaming.type = hadoop # URI for table metadata: AWS S3 example spark.sql.catalog.streaming.warehouse = s3a:///redpanda-iceberg-catalog # You may need to configure additional properties based on your object storage provider. # See https://iceberg.apache.org/docs/latest/spark-configuration/#spark-configuration and https://spark.apache.org/docs/latest/configuration.html # For example, for AWS S3: # spark.hadoop.fs.s3.impl = org.apache.hadoop.fs.s3a.S3AFileSystem # spark.hadoop.fs.s3a.endpoint = http:// # spark.sql.catalog.streaming.s3.endpoint = http:// ``` > ๐Ÿ“ **NOTE** > > Redpanda recommends setting credentials in environment variables so Spark can securely access your Iceberg data in object storage. For example, for AWS, use `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. Depending on your processing engine, you may need to also create a new table to point the data lakehouse to the table location. ### [](#specify-metadata-location)Specify metadata location The `[iceberg_catalog_base_location](https://docs.redpanda.com/streaming/25.2/reference/properties/cluster-properties/#iceberg_catalog_base_location)` property stores the base path for the filesystem-based catalog if using the `object_storage` catalog type. The default value is `redpanda-iceberg-catalog`. > โš ๏ธ **CAUTION** > > Do not change the `iceberg_catalog_base_location` value after you have enabled Iceberg integration for a topic. ## [](#next-steps)Next steps - [Query Iceberg Topics](https://docs.redpanda.com/streaming/25.2/manage/iceberg/query-iceberg-topics/) - [Query Iceberg Topics using AWS Glue](https://docs.redpanda.com/streaming/25.2/manage/iceberg/iceberg-topics-aws-glue/) - [Query Iceberg Topics using Databricks and Unity Catalog](https://docs.redpanda.com/streaming/25.2/manage/iceberg/iceberg-topics-databricks-unity/) - [Query Iceberg Topics using Snowflake and Open Catalog](https://docs.redpanda.com/streaming/25.2/manage/iceberg/redpanda-topics-iceberg-snowflake-catalog/) ## Suggested labs - [Redpanda Iceberg Docker Compose Example](https://docs.redpanda.com/labs/docker-compose/iceberg/) - [Iceberg Streaming on Kubernetes with Redpanda, MinIO, and Spark](https://docs.redpanda.com/labs/kubernetes/iceberg/) [Search all labs](https://docs.redpanda.com/labs)