From 485ecb752cc63c45585163be1bf0d789d055e2c6 Mon Sep 17 00:00:00 2001 From: "Gamze.Akpinar" Date: Tue, 17 Nov 2026 14:07:15 +0100 Subject: [PATCH 1/5] Add IAM role creation steps to Iceberg bridge docs (DBR-3288) Document the IAM role customers create so the Apache Iceberg bridge can write to their S3 bucket: trust policy for the Mendix Tableflow agent role, S3 permissions policy with optional KMS statement, and where to enter the role ARN. Also add the missing description front matter. Co-Authored-By: Claude Opus 5.5 --- .../event-broker-bridges/iceberg-bridge.md | 103 +++++++++++++++++- 1 file changed, 102 insertions(+), 1 deletion(-) diff --git a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md index 399146b5881..61bf73310cb 100644 --- a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md +++ b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md @@ -2,6 +2,7 @@ title: "Configure a Bridge with Apache Iceberg" url: /appstore/services/event-broker-bridges/iceberg-bridge/ linktitle: "Apache Iceberg Bridge" +description: "Describes how to configure an Apache Iceberg bridge that delivers CDC events from the Mendix Event Broker to Iceberg tables in AWS S3 or Azure Blob Storage." --- ## Introduction @@ -22,10 +23,110 @@ Configure the service by filling out the following: * **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 + * **AWS Role (to Assume)** – the Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role that the bridge assumes to write to your S3 bucket +{{% alert color="info" %}}For instructions on creating the IAM role and getting its ARN, see the [Create an IAM Role for AWS S3](#create-iam-role) section.{{% /alert %}} {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/iceberg/ebb_iceberg_configure.png" alt="" width="400" >}} +### Create an IAM Role for AWS S3 {#create-iam-role} + +If you store your data in AWS S3, create an IAM role in your AWS account that the bridge can assume to write Iceberg tables to your bucket. The role needs a trust policy that allows the Mendix Tableflow agent role to assume it, and a permissions policy that grants access to the bucket. + +#### Prerequisites + +* Access to your AWS account with permissions to create and manage IAM roles and policies +* The S3 bucket where the Iceberg tables are stored +* The ARN of the Mendix Tableflow agent role + +#### Create the Role with a Trust Policy + +The trust policy defines who can assume the role. + +1. In the AWS Management Console, go to **IAM** > **Roles**. +2. Click **Create role**. +3. Select **Custom trust policy** as the trusted entity type. +4. Enter the following trust policy: + + ```json + { + "Version": "2012-10-17", + "Statement": [ + { + "Sid": "AllowMendixTableflowAgent", + "Effect": "Allow", + "Principal": { + "AWS": "MENDIX_TABLEFLOW_AGENT_ROLE_ARN" + }, + "Action": "sts:AssumeRole" + } + ] + } + ``` + +5. Replace *`MENDIX_TABLEFLOW_AGENT_ROLE_ARN`* with the ARN of the Mendix Tableflow agent role. +6. Click **Next**. + +#### Attach a Permissions Policy + +The permissions policy defines what the bridge can do after it assumes the role. + +1. On the **Add permissions** page, click **Create policy**. The policy editor opens in a new browser tab. +2. Select **JSON** and enter the following policy to grant the required S3 permissions: + + ```json + { + "Version": "2012-10-17", + "Statement": [ + { + "Sid": "AllowListBucket", + "Effect": "Allow", + "Action": "s3:ListBucket", + "Resource": "arn:aws:s3:::BUCKET_NAME" + }, + { + "Sid": "AllowReadWriteObjects", + "Effect": "Allow", + "Action": [ + "s3:GetObject", + "s3:PutObject", + "s3:DeleteObject" + ], + "Resource": "arn:aws:s3:::BUCKET_NAME/*" + } + ] + } + ``` + +3. If your bucket is encrypted with an AWS Key Management Service (KMS) key, add the following statement to the `Statement` array, separated from the previous statement by a comma: + + ```json + { + "Sid": "AllowKmsForBucketEncryption", + "Effect": "Allow", + "Action": [ + "kms:Decrypt", + "kms:GenerateDataKey" + ], + "Resource": "KMS_KEY_ARN" + } + ``` + +4. Replace *`BUCKET_NAME`* with the name of your S3 bucket and, if applicable, *`KMS_KEY_ARN`* with the ARN of the KMS key that encrypts the bucket. +5. Name the policy (for example, `MendixIcebergBridgeS3Policy`) and create it. +6. Return to the browser tab where you are creating the role, refresh the list of policies, and select the policy you created. +7. Click **Next**. + +{{% alert color="info" %}} +The bridge does not need AWS Glue permissions. +{{% /alert %}} + +#### Complete the Role Creation + +1. Enter a name for the role (for example, `MendixIcebergBridgeRole`). +2. Review the role configuration and click **Create role**. +3. Open the role and copy its ARN. The ARN has the format `arn:aws:iam::ACCOUNT_ID:role/MendixIcebergBridgeRole`, where *`ACCOUNT_ID`* is your AWS account ID. +4. When you configure the bridge, enter the role ARN in the **AWS Role (to Assume)** field. + ### 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. From 6072eff15ec02048b849576a7460498161a4dd15 Mon Sep 17 00:00:00 2001 From: "Gamze.Akpinar" Date: Tue, 17 Nov 2026 14:22:44 +0100 Subject: [PATCH 2/5] Rename Apache Iceberg to Iceberg in Event Broker bridge docs Co-Authored-By: Claude Opus 5.5 --- .../event-broker/event-broker-bridges/_index.md | 4 ++-- .../event-broker-bridges/iceberg-bridge.md | 10 +++++----- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/_index.md b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/_index.md index 139d5043559..8d475449246 100644 --- a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/_index.md +++ b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/_index.md @@ -2,7 +2,7 @@ title: "Mendix Event Broker Bridges" url: /appstore/services/event-broker-bridges/ linktitle: "Event Broker Bridges" -description: "Describes how to create and manage Mendix Event Broker Bridges to integrate the Event Broker with external technologies such as AWS SQS, HTTP, Azure Blob Storage, AWS S3, Apache Iceberg, and Kafka." +description: "Describes how to create and manage Mendix Event Broker Bridges to integrate the Event Broker with external technologies such as AWS SQS, HTTP, Azure Blob Storage, AWS S3, Iceberg, and Kafka." aliases: - /appstore/services/event-broker/#manage-mx-broker-bridge --- @@ -13,7 +13,7 @@ aliases: Mendix Event Broker Bridges were released for GA in 11.4.0. {{% /alert %}} -Mendix Event Broker Bridges integrate the Mendix Event Broker with external technologies, such as AWS SQS, HTTP, Azure Blob Storage, AWS S3, Apache Iceberg, and Kafka. These bridges enable the exchange of events between your Mendix Cloud environment and external systems. +Mendix Event Broker Bridges integrate the Mendix Event Broker with external technologies, such as AWS SQS, HTTP, Azure Blob Storage, AWS S3, Iceberg, and Kafka. These bridges enable the exchange of events between your Mendix Cloud environment and external systems. {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/event_broker_bridges.png" alt="" class="no-border" >}} diff --git a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md index 61bf73310cb..9d10d7b536d 100644 --- a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md +++ b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md @@ -1,13 +1,13 @@ --- -title: "Configure a Bridge with Apache Iceberg" +title: "Configure a Bridge with Iceberg" url: /appstore/services/event-broker-bridges/iceberg-bridge/ -linktitle: "Apache Iceberg Bridge" -description: "Describes how to configure an Apache Iceberg bridge that delivers CDC events from the Mendix Event Broker to Iceberg tables in AWS S3 or Azure Blob Storage." +linktitle: "Iceberg Bridge" +description: "Describes how to configure an Iceberg bridge that delivers CDC events from the Mendix Event Broker to Iceberg tables in AWS S3 or Azure Blob Storage." --- ## Introduction -An Apache Iceberg Bridge is a one-way bridge that delivers [Change Data Capture (CDC)](/refguide/change-data-capture/) events to Apache Iceberg tables stored in AWS S3 or Azure Blob Storage. +An Iceberg Bridge is a one-way bridge that delivers [Change Data Capture (CDC)](/refguide/change-data-capture/) events to Iceberg tables stored in AWS S3 or Azure Blob Storage. ## Configure Service @@ -154,7 +154,7 @@ Select the CDC events that you want to deliver from the Event Broker to Iceberg: ## 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. +You can edit an Iceberg 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. {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/edit-bridge/ebb_iceberg_edit_mode.png" class="no-border" >}} From 440d303ef8bbc2bf835b4c83af2ef43d4000a8fa Mon Sep 17 00:00:00 2001 From: "Gamze.Akpinar" Date: Tue, 17 Nov 2026 14:27:26 +0100 Subject: [PATCH 3/5] Use neutral name for the Mendix role in Iceberg bridge docs Co-Authored-By: Claude Opus 5.5 --- .../event-broker-bridges/iceberg-bridge.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md index 9d10d7b536d..db2a320ffe1 100644 --- a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md +++ b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md @@ -30,13 +30,13 @@ Configure the service by filling out the following: ### Create an IAM Role for AWS S3 {#create-iam-role} -If you store your data in AWS S3, create an IAM role in your AWS account that the bridge can assume to write Iceberg tables to your bucket. The role needs a trust policy that allows the Mendix Tableflow agent role to assume it, and a permissions policy that grants access to the bucket. +If you store your data in AWS S3, create an IAM role in your AWS account that the bridge can assume to write Iceberg tables to your bucket. The role needs a trust policy that allows the Mendix Iceberg bridge role to assume it, and a permissions policy that grants access to the bucket. #### Prerequisites * Access to your AWS account with permissions to create and manage IAM roles and policies * The S3 bucket where the Iceberg tables are stored -* The ARN of the Mendix Tableflow agent role +* The ARN of the Mendix Iceberg bridge role #### Create the Role with a Trust Policy @@ -52,10 +52,10 @@ The trust policy defines who can assume the role. "Version": "2012-10-17", "Statement": [ { - "Sid": "AllowMendixTableflowAgent", + "Sid": "AllowMendixIcebergBridge", "Effect": "Allow", "Principal": { - "AWS": "MENDIX_TABLEFLOW_AGENT_ROLE_ARN" + "AWS": "MENDIX_ICEBERG_BRIDGE_ROLE_ARN" }, "Action": "sts:AssumeRole" } @@ -63,7 +63,7 @@ The trust policy defines who can assume the role. } ``` -5. Replace *`MENDIX_TABLEFLOW_AGENT_ROLE_ARN`* with the ARN of the Mendix Tableflow agent role. +5. Replace *`MENDIX_ICEBERG_BRIDGE_ROLE_ARN`* with the ARN of the Mendix Iceberg bridge role. 6. Click **Next**. #### Attach a Permissions Policy From b8b868452f9396a0a3ded45a7ddaa513094f53a1 Mon Sep 17 00:00:00 2001 From: "Gamze.Akpinar" Date: Tue, 17 Nov 2026 14:38:22 +0100 Subject: [PATCH 4/5] Explain where to find the Mendix Iceberg bridge role ARN Co-Authored-By: Claude Opus 5.5 --- .../event-broker/event-broker-bridges/iceberg-bridge.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md index db2a320ffe1..0618ba027bb 100644 --- a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md +++ b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md @@ -36,7 +36,7 @@ If you store your data in AWS S3, create an IAM role in your AWS account that th * Access to your AWS account with permissions to create and manage IAM roles and policies * The S3 bucket where the Iceberg tables are stored -* The ARN of the Mendix Iceberg bridge role +* The ARN of the Mendix Iceberg bridge role, which [Event Broker Manager](https://broker.mendix.com/) shows when you configure an Iceberg bridge that uses AWS S3 #### Create the Role with a Trust Policy @@ -63,7 +63,7 @@ The trust policy defines who can assume the role. } ``` -5. Replace *`MENDIX_ICEBERG_BRIDGE_ROLE_ARN`* with the ARN of the Mendix Iceberg bridge role. +5. Replace *`MENDIX_ICEBERG_BRIDGE_ROLE_ARN`* with the ARN of the Mendix Iceberg bridge role. You can copy this ARN from the bridge configuration in Event Broker Manager. 6. Click **Next**. #### Attach a Permissions Policy From 98f2669ae12bbc7bd32d254a6ae6f40063d7abb2 Mon Sep 17 00:00:00 2001 From: "Gamze.Akpinar" Date: Tue, 17 Nov 2026 16:07:50 +0100 Subject: [PATCH 5/5] Restore Apache Iceberg name in Event Broker bridge docs Co-Authored-By: Claude Opus 5.5 --- .../event-broker/event-broker-bridges/_index.md | 4 ++-- .../event-broker-bridges/iceberg-bridge.md | 10 +++++----- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/_index.md b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/_index.md index 8d475449246..139d5043559 100644 --- a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/_index.md +++ b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/_index.md @@ -2,7 +2,7 @@ title: "Mendix Event Broker Bridges" url: /appstore/services/event-broker-bridges/ linktitle: "Event Broker Bridges" -description: "Describes how to create and manage Mendix Event Broker Bridges to integrate the Event Broker with external technologies such as AWS SQS, HTTP, Azure Blob Storage, AWS S3, Iceberg, and Kafka." +description: "Describes how to create and manage Mendix Event Broker Bridges to integrate the Event Broker with external technologies such as AWS SQS, HTTP, Azure Blob Storage, AWS S3, Apache Iceberg, and Kafka." aliases: - /appstore/services/event-broker/#manage-mx-broker-bridge --- @@ -13,7 +13,7 @@ aliases: Mendix Event Broker Bridges were released for GA in 11.4.0. {{% /alert %}} -Mendix Event Broker Bridges integrate the Mendix Event Broker with external technologies, such as AWS SQS, HTTP, Azure Blob Storage, AWS S3, Iceberg, and Kafka. These bridges enable the exchange of events between your Mendix Cloud environment and external systems. +Mendix Event Broker Bridges integrate the Mendix Event Broker with external technologies, such as AWS SQS, HTTP, Azure Blob Storage, AWS S3, Apache Iceberg, and Kafka. These bridges enable the exchange of events between your Mendix Cloud environment and external systems. {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/event_broker_bridges.png" alt="" class="no-border" >}} diff --git a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md index 0618ba027bb..d001049890a 100644 --- a/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md +++ b/content/en/docs/marketplace/platform-supported-content/services/event-broker/event-broker-bridges/iceberg-bridge.md @@ -1,13 +1,13 @@ --- -title: "Configure a Bridge with Iceberg" +title: "Configure a Bridge with Apache Iceberg" url: /appstore/services/event-broker-bridges/iceberg-bridge/ -linktitle: "Iceberg Bridge" -description: "Describes how to configure an Iceberg bridge that delivers CDC events from the Mendix Event Broker to Iceberg tables in AWS S3 or Azure Blob Storage." +linktitle: "Apache Iceberg Bridge" +description: "Describes how to configure an Apache Iceberg bridge that delivers CDC events from the Mendix Event Broker to Iceberg tables in AWS S3 or Azure Blob Storage." --- ## Introduction -An Iceberg Bridge is a one-way bridge that delivers [Change Data Capture (CDC)](/refguide/change-data-capture/) events to Iceberg tables stored in AWS S3 or Azure Blob Storage. +An Apache Iceberg Bridge is a one-way bridge that delivers [Change Data Capture (CDC)](/refguide/change-data-capture/) events to Apache Iceberg tables stored in AWS S3 or Azure Blob Storage. ## Configure Service @@ -154,7 +154,7 @@ Select the CDC events that you want to deliver from the Event Broker to Iceberg: ## Editing Bridges -You can edit an Iceberg 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. +You can edit an Apache Iceberg 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. {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/edit-bridge/ebb_iceberg_edit_mode.png" class="no-border" >}}