You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature is currently in [Private Beta](/releasenotes/release-status/). Contact your Customer Success Manager or Account Manager for further assistance.
101
-
{{% /alert %}}
102
-
103
-
Mendix Event Broker Bridges facilitate integration between the Mendix Event Broker and external technologies, such as AWS SQS and HTTP. These bridges enable the exchange of events between your Mendix Cloud environment and external systems, ensuring efficient communication across diverse technological landscapes.
Every event must carry four mandatory CloudEvents core attributes, each prefixed with `ce_`:
110
-
111
-
* id as `ce_id`
112
-
* source as `ce_source`
113
-
* specversion as `ce_specversion`
114
-
* type as `ce_type`
115
-
116
-
See [CloudEvents](https://github.com/cloudevents/spec/blob/v1.0.1/spec.md#required-attributes) for more information on required attributes.
117
-
118
-
#### HTTP Bridges Header
119
-
120
-
For HTTP Bridges, an additional HTTP header is required for authentication.
121
-
122
-
***Authorization** – The value must be set as a Bearer token using the Personal Access Token (PAT) generated during bridge configuration.
123
-
For example: `Authorization: Bearer <your-personal-access-token>`
124
-
125
-
This header must be included in all HTTP requests sent to the Mendix Event Broker via the HTTP Bridge. For details on how to obtain your Bearer token, see [Using the HTTP Bridge](#using-the-http-bridge).
126
-
127
-
{{% alert color="info" %}}
128
-
You can include additional HTTP headers in your request, such as `ce_time: 2025-06-13T15:36:52.148542+02:00`. For example, passing `ce_time` will set the published time of the event. All other custom HTTP headers will be forwarded as Kafka headers by default.
129
-
{{% /alert %}}
130
-
131
-
### Creating a Bridge
132
-
133
-
Technical Contacts with a license to the Mendix Event Broker can manage this feature from the **Event Broker Bridges** tab on the [Event Broker Manager](https://broker.mendix.com/) page.
1. Click **Create a Bridge** to create a new bridge.
138
-
2. Select either an **AWS SQS** or an **HTTP** service to configure.
139
-
140
-
* An AWS SQS bridge uses the [Amazon Simple Queue Service](https://aws.amazon.com/sqs/). The HTTP Bridge uses HTTP requests to send events from external systems to the Mendix Event Broker. The HTTP bridge is one-way: **HTTP to Event Broker**.
141
-
142
-
3. Click **Next** to continue with creating your bridge.
143
-
144
-
* For instructions on configuring for AWS SQS, see [Configuring a Bridge with AWS SQS](#bridge-with-aws-sqs)
145
-
* For instructions on configuring for HTTP, see [Configuring a Bridge with HTTP](#bridge-with-http)
146
-
147
-
### Configuring a Bridge with AWS SQS {#bridge-with-aws-sqs}
148
-
149
-
The creation process for AWS SQS bridges includes two further steps on the Mendix side and policies that need to be implemented on the AWS side.
150
-
151
-
#### Configuration Details
152
-
153
-
1. Select a [Space](#spaces), Name, and Region for the bridge to operate in.
6. After all events have been configured, click **Start** to start the Mendix Event Broker Bridge. This process will take several minutes to complete. You can also choose to **Start Later**.
Initially, you will have no business events. Choose the business events to integrate by doing the following:
247
-
248
-
1. Click **Add Business Events** to open a dialog displaying all events managed by the Event Broker (including Mendix app-defined and uploaded AsyncAPI events). Only events that can **subscribe** are displayed, as this bridge is one-way.
249
-
2. Select the event(s) you want to integrate. Once events are selected, the URL for the HTTP connection is automatically generated. No further configuration is required.
250
-
3. Click **Next** to integrate the chosen business events.
After creating an HTTP Bridge, you can modify its event configuration by adding or removing events as your integration requirements evolve, without needing to recreate the bridge.
277
-
278
-
{{% alert color="info" %}}You can only edit an HTTP Bridge when its status is **Running**.{{% /alert %}}
279
-
280
-
To edit an HTTP Bridge:
281
-
282
-
1. On the [Event Broker Manager](https://broker.mendix.com/) page, navigate to the **Event Broker Bridges** tab.
In editing mode, you can perform the following actions:
289
-
290
-
***Add Business Events**:
291
-
292
-
1. Click **Add Business Events** to open a dialog that displays available events.
293
-
2. Select the events you want to add and click **Select**. Added events will display an **Added** badge and can be removed before applying changes.
294
-
295
-
***Remove Business Events**:
296
-
297
-
1. Navigate to the event you want to remove and click **Remove**. Removed events will display a **Removed** badge, and their name and metadata will appear grayed out.
298
-
2. Re-add a removed event by clicking **Add** before applying changes.
* 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 they are applied.
304
-
* Click **Cancel** to exit editing mode without saving any changes.
305
-
306
-
{{% alert color="info" %}}
307
-
The **Apply** button is only enabled when changes have been made to the bridge configuration.
308
-
{{% /alert %}}
309
-
310
-
{{% alert color="warning" %}}
311
-
If an error occurs during the editing process, the bridge will automatically roll back to its previous running state to ensure continuity of service.
312
-
{{% /alert %}}
97
+
{{< include "/static/_includes/event-broker-bridges.md" >}}
313
98
314
99
## Externally Defined Events {#externally-defined-events}
0 commit comments