Egress Private Link Endpoints Setup Guide: First-Party Services on Azure for Confluent Cloud¶
This topic presents the steps for setting up Egress Private Link Endpoints for the Azure first-party services on Azure and Confluent Cloud to enable the use of fully managed connectors in Confluent Cloud using Azure Private Link.
Step 1. Retrieve the Resource ID¶
In the Azure portal, go to your service’s overview section, and click Json View.
Copy the Resource ID which is required when you create the Egress Private Link Endoint in Confluent Cloud.
Step 2. Create an Egress Private Link Endpoint¶
In the Network Management tab of the desired Confluent Cloud environment, click the Confluent Cloud network you want to add the Private Link Endpoint to. The Connection Type of the network needs to be “Private Link Access”.
Click Create endpoint in the Egress connections tab.
Click the service you want to connect to. Select Other if you do not see the specific service.
Follow the guided steps to specify the field values, including:
Name: The name of the Private Link Endpoint.
Resource ID: The resource ID of the Private Link service.
The Resource ID is the one noted down above, in the last step of the Step 1 section.
Note that the resource alias is not supported.
Sub-resource name: The sub-resource name for the specific Azure service.
The applicable sub-resource name can be retrieved in Azure Private-link resource.
Click Create to create the Private Link Endpoint.
If there are additional steps for the specific target service, follow the prompt to complete the tasks, and then click Finish.
Step 3. Accept the connection request¶
When the Private Link Endpoint status becomes “Pending Accept” in the Azure portal, go to Pending Connections and approve the associated connection request.
Confirm this is the correct connection by checking the Description column which will provide the associated Confluent Cloud gateway and environment ID.
Step 4. Create the DNS record¶
When the Private Link Endpoint status transitions to “Ready”, click Create DNS record in the DNS tab, or click Create Record on the associated Private Link Endpoint tile.
Specify the following:
- Private Link Endpoint
- Domain: The associated service endpoint. For example, for Azure SQL
Server, it is in the pattern,
<sql-server-name>.database.windows.net
.
The following are example entries for Azure Blob Storage.
Click Save.
Step 5. Create the Connector¶
- When the DNS Record status transitions to “Ready”, you can create the connector.
- For the steps to create the connector, refer to the connector-specific documentation that is listed for your specific connector in Supported connectors.