Configure a Bridge with Apache Iceberg

Last modified: September 15, 2026

Introduction

An Apache Iceberg Bridge is a one-way bridge that delivers Change Data Capture (CDC) events to Apache Iceberg tables stored in AWS S3 or Azure Blob Storage.

Configure Service

Configure the service by filling out the following:

  • Event Broker Space – the space where the bridge operates

  • Name – a name for the bridge

  • Choose a data lake – the data lake that Iceberg uses to store your data

    • Azure Blob Storage
      • Storage Account – the storage account to access
      • Storage SAS Token – the SAS token used to access the storage account
      • Container – the container where the data is stored
    • AWS S3
      • Bucket – the bucket where the data is stored
      • AWS Region for Bucket – the AWS region where the bucket is located
      • AWS Role (to Assume) – the AWS role to assume for the required permissions

Bridge Statuses

Check the Bridge Status on the Overview page to verify that it is ready and operating as expected. The following list describes the possible bridge statuses.

  • Halted – The bridge has stopped because an internal component failed. Data is not being delivered.
  • Provisioning – The bridge is being created or initialized and is not yet ready to deliver data.
  • Delivering – The bridge is healthy, fully configured, and actively delivering data to the destination.
  • Misconfigured – The bridge is running, but its data flow is not healthy or cannot be fully verified. Check the bridge configuration and data flow.
  • Reconfiguring – The bridge is applying configuration changes. Data delivery may be temporarily interrupted until the new configuration is synchronized.
  • Awaiting Data – The bridge is running and ready, but no source data is currently flowing. Data delivery will begin when data becomes available.

Connect Events

Select the CDC events that you want to deliver from the Event Broker to Iceberg:

  1. Click Add CDC Events to open a dialog box displaying the available CDC events managed by the Event Broker. Only events that can be subscribed to are shown because the bridge delivers events in one direction, from the Event Broker to Iceberg.

  2. Select one or more CDC events to integrate. The Iceberg connection configuration is automatically generated based on the selected events.

  3. Click Next to review and confirm the bridge configuration.

Editing Bridges

You can edit an Apache Iceberg bridge bridge to modify the configuration as your integration requirements evolve, without needing to recreate it. For an Iceberg bridge, you can add or remove CDC events.

To edit a bridge:

  1. On the Event Broker Manager page, navigate to the Event Broker Bridges tab.

  2. Click the bridge you want to modify.

  3. Click Edit to enter editing mode. In editing mode, you can perform the following actions:

    • Add CDC Events (Iceberg):

      1. Click Add CDC Events to open a dialog box that displays available CDC events.
      2. Select the CDC events you want to add and click Select. Added events display an Added badge and can be removed before applying changes.

    • Remove CDC Events (Iceberg):

      1. Navigate to the CDC event you want to remove and click Remove. Removed events display a Removed badge, and their name and metadata appear grayed out.
      2. To re-add a removed CDC event, click Add before applying changes.

  4. Once you have made your changes, you can:

    • Click Apply to save and apply the changes. A confirmation message will indicate if the changes were successful. Changes to the event configuration take effect when applied. After applying changes, the bridge status will change to Reconfiguring and will return to Running once the reconfiguration is complete.
    • Click Cancel to exit editing mode without saving any changes.