Connect your Amazon MSK data source and your Data Cloud tenant with a dedicated network
connection using Private Connect for Data Cloud. You can create a single connection to a specific
instance regardless of how many Data Cloud instances you have. Before setting up a connection for
Amazon MSK, you must establish a private network route.
Manage External Connections or Customize
Application permissions
To administer an MSK environment:
Amazon MSK account administrator
The number of private network routes for a particular Amazon MSK connection per
Data Cloud functional domain (not per Data Cloud org) is limited to one.
You can configure a PNR to connect to an Amazon MSK instance, even if it isn't in
the same region as your Data Cloud tenant.
From Data Cloud Setup, expand Admin Tools and select Private Connect.
Click New.
When the maximum number of licensed private network routes is reached, the New button
doesn’t appear.
On the Add Private Network Route page, select Amazon MSK and click
Setup.
The Configure Amazon MSK Private Network Route page provides the principle ID, which
identifies the Salesforce AWS environment where this private network route will be created.
Enter a route name. The route API name is auto-populated. You can’t change the route name
after you save it.
In the navigation pane, locate and choose Endpoint services.
Enter the Broker Endpoints. Broker endpoints are the addresses used to connect to your
cluster. From your MSK cluster in the AWS Management Console, navigate to the client
information section to display the broker endpoints. For more information, see Get the bootstrap brokers using the AWS Management
Console.
Copy the value of the Principal Id field in the PNR, and use the AWS console to add it to
the list of allowed principals for your endpoint service.
Click Save.
Once your Private Connect connection is configured, allow a few minutes for it to
become fully established before sending or receiving data.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.