Enable the feature cluster-wide with `iceberg_enabled: true` (Redpanda 25.1+, GA for Enterprise Edition, public beta only for BYOC)
Set `redpanda.iceberg.mode` on the target topic to `key_value`, `value_schema_id_prefix`, or `value_schema_latest` (default is `disabled`)
For AWS Glue catalog integration (Redpanda 25.2+), set `iceberg_rest_catalog_authentication_mode: aws_sigv4`, configure an S3 base URI, and grant IAM access to the Glue Data Catalog
Set a unique `iceberg_default_catalog_namespace` per cluster if multiple Redpanda clusters write into the same Glue catalog
If using `value_schema_id_prefix` or `value_schema_latest`, ensure producers write Schema-Registry wire-format encoded messages
Query the resulting Iceberg table from a catalog-integrated engine (e.g. Athena, Spark) and confirm schema evolution reflects Schema Registry changes
Known gotchas
Glue provides one catalog per AWS account — clusters sharing a Glue catalog must use distinct `iceberg_default_catalog_namespace` values or table names collide
BYOC deployments only get public beta status for Iceberg Topics, not GA (GA is Enterprise Edition only as of the 25.1 announcement)
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?