Add Amazon MSK Kafka source to an eventstream

Статия
19.11.2024 г.

This article shows you how to add an Amazon MSK Kafka source to an eventstream. 

Amazon MSK Kafka is a fully managed Kafka service that simplifies the setup, scaling, and management. By integrating Amazon MSK Kafka as a source within your eventstream, you can seamlessly bring the real-time events from your MSK Kafka and process it before routing them to multiple destinations within Fabric. 

Бележка

This source is not supported in the following regions of your workspace capacity: West US3, Switzerland West.

Prerequisites

Access to a workspace in the Fabric capacity license mode (or) the Trial license mode with Contributor or higher permissions.
An Amazon MSK Kafka cluster in active status.
Your Amazon MSK Kafka cluster must be publicly accessible and not be behind a firewall or secured in a virtual network.

Бележка

The maximum number of sources and destinations for one eventstream is 11.

Add Amazon MSK Kafka as a source 

In Fabric Real-Time Intelligence, select Eventstream to create a new eventstream.
On the next screen, select Add external source.

Configure and connect to Amazon MSK Kafka

On the Data sources page, select Amazon MSK Kafka.
On the Connect page, select New connection.
In the Connection settings section, for Bootstrap Server, enter the public endpoint of your Kafka cluster.

To get the public endpoint:
In the Connection credentials section, If you have an existing connection to the Amazon MSK Kafka cluster, select it from the drop-down list for Connection. Otherwise, follow these steps:
1. For Connection name, enter a name for the connection.
2. For Authentication kind, confirm that API Key is selected.
3. For Key and Secret, enter API key and key Secret for Amazon MSK Kafka cluster.
Select Connect. 
Now, on the Connect page, follow these steps.
1. For Topic, enter the Kafka topic.
2. For Consumer group, enter the consumer group of your Kafka cluster. This field provides you with a dedicated consumer group for getting events.
3. Select Reset auto offset to specify where to start reading offsets if there's no commit.
4. For Security protocol, the default value is SASL_SSL. The default SASL mechanism is SCRAM-SHA-512 and cannot be changed.
Select Next. On the Review + connect screen, review the summary, and then select Connect.