Egress PrivateLink Endpoints Setup Guide: First-Party Services on AWS for Confluent Cloud

This topic presents the steps for setting up Egress PrivateLink Endpoints for the AWS first-party services on AWS and Confluent Cloud to enable fully managed connectors in Confluent Cloud using AWS PrivateLink.

Step 1. Create a gateway in Confluent Cloud (for Enterprise cluster only)

If using an Enterprise cluster in Confluent Cloud, you must set up a gateway in Confluent Cloud as described in Create a gateway for outbound connectivity in Confluent Cloud.

Step 2. Create an Egress PrivateLink Endpoint

1. In the Network Management tab of the desired Confluent Cloud environment, click the Confluent Cloud network you want to add the PrivateLink Endpoint to. The Connection Type of the network needs to be “PrivateLink Access”.

2. Click Create endpoint in the Egress connections tab.

3. Click the service you want to connect to. Select Other if you do not see the specific service.

4. Follow the guided steps to specify the field values, including:

   • Name: Name of the PrivateLink Endpoint.

   • PrivateLink service name: The name of the PrivateLink service.

     The applicable service name can be retrieved from the AWS Services Privatelink Support page, for example, com.amazonaws.<region>.<service>.

   • Create an endpoint with high availability: Check the box if you wish to deploy an endpoint with High Availability.

     Endpoints deployed with high availability have network interfaces deployed in multiple availability zones.

5. Click Create to create the PrivateLink Endpoint.

6. If there are additional steps for the specific target service, follow the prompt to complete the tasks, and then click Finish.

Step 3. Create the DNS record

1. When the PrivateLink Endpoint status transitions to “Ready”, click Create DNS record in the Egress DNS tab, or click Create Record on the associated PrivateLink Endpoint tile.

2. Specify the following:

   • Egress PrivateLink Endpoint: The Egress PrivateLink Endpoint you created in the Step 2 section above.
   • Domain: Associated service endpoint (<service>.<region>.amazonaws.com).

   Links to AWS Service endpoints can be found on AWS Service Information.

3. Click Save to create the record.

Step 4. Create the Connector

1. When the DNS Record status transitions to “Ready”, you can create the connector.
2. For the steps to create the connector, refer to the connector-specific documentation that is listed for your specific connector in Supported connectors.