Configure an AWS PrivateLink connection to Confluent Cloud¶

This topic describes how to configure AWS PrivateLink to connect to your Confluent Cloud cluster.

The following diagram summarizes the AWS PrivateLink architecture with the customer VPC/account and the Confluent Cloud VPC/account.

Overview of AWS PrivateLink

Prerequisites: A Dedicated Kafka cluster in AWS with AWS PrivateLink enabled. For more information about how to create a dedicated cluster, see Create a Cluster in Confluent Cloud.

Follow this procedure to configure AWS PrivateLink for a Dedicated cluster in AWS.

Register your AWS account with Confluent Cloud using the Confluent Cloud UI.
Set up the VPC Endpoint(s) to Confluent Cloud PrivateLink Service in your AWS account using the AWS portal.
Set up Availability Zone mapped DNS records to use AWS VPC Endpoints using the AWS portal.
Validate connectivity to Confluent Cloud.

Requirements¶

To use AWS PrivateLink with Confluent Cloud, your VPC must allow outbound internet connections for DNS resolution, Schema Registry and Confluent Cloud CLI to work.
1. DNS requests to public authority traversing to private hosted zone is required.
2. Confluent Cloud Schema Registry is only accessible over the internet.
3. Confluent Cloud CLI requires internet access to authenticate with the Confluent Cloud control plane.
Confluent Cloud web UI components like topic management need additional configuration to function as they use cluster endpoints. To use all features of the Confluent Cloud web UI with AWS PrivateLink, follow this procedure.

Warning

For limitations of the AWS PrivateLink feature, see Limitations.

Register your AWS account with Confluent Cloud¶

To make an AWS PrivateLink connection to a cluster in Confluent Cloud you must register the AWS account ID you wish to use. This is a security measure so Confluent can ensure only your organization can initiate AWS PrivateLink connections to the cluster. AWS PrivateLink connections from a VPC not contained in a registered AWS account will not be accepted by Confluent Cloud.

Navigate to the Cluster Settings page, click the Networking tab, and click Add Account.
Provide the 12-digit AWS Account Number for the account containing the VPCs you want to make the PrivateLink connection from and click Save. Your AWS PrivateLink connection status will transition from “Pending” to “Active” in the Confluent Cloud web UI. You still need to configure the VPC endpoint in your VPC before you can connect to the cluster.

Set up the VPC Endpoint for AWS PrivateLink in your AWS account¶

After the connection status is “Active” in the Confluent Cloud web UI, you must configure VPC Endpoint(s) in your VPC to make the PrivateLink connection(s) to your Confluent Cloud cluster.

Note

Confluent recommends using a Terraform configuration to configure the Private Link Endpoint. This configuration automates the manual steps described below.

Prerequisites

In the Confluent Cloud UI you will find the following information for your Confluent Cloud cluster under the Cluster Settings section.

Kafka Bootstrap (in the General tab)
Availability Zone ID(s) (in the Networking tab)
VPC Service Endpoint Name (in the Networking tab)
DNS Domain Name (in the Networking tab)
Zonal DNS Subdomain Name(s) (in the Networking tab)

Verify subnet availability

The Confluent Cloud VPC and cluster is created in specific zone(s) that, for optimal usage, should match the zone(s) of the customer VPC you want to make the AWS PrivateLink connection(s) from. You must have subnet(s) in your VPC for these zone(s) so that IP(s) can be allocated from them. It is allowed to also have subnets in zones outside of these. AWS Zone IDs should be used for this. You can find the specific Availability Zone(s) for your Confluent Cloud cluster in the UI.

Ensure the VPC settings enableDnsHostnames and enableDnsSupport are set to true.

Note

Please note: Availability Zone names (like us-west-2a) are not consistent across AWS accounts, so Availability Zone IDs (like usw2-az1) are used instead.
Create the VPC Endpoint

In the AWS VPC Console:
1. Select Endpoints from left hand list of tabs.
2. Click Create Endpoint.
3. Select Find service by name.
4. Paste in the Confluent Cloud VPC Service Endpoint Name. You can find this in the Confluent Cloud UI.
5. Click Verify. If you get an error, ensure that your account is allowed to create PrivateLink connections.
6. Select VPC to create endpoints. Keep a note of this VPC Endpoint ID for use later.
7. Note the availability zone(s) for your Confluent Cloud cluster from the Networking tab in the Confluent Cloud UI. Select the service in these zone(s). Ensure the desired subnet is selected for each zone. Failure to add all zone(s) as displayed in the Confluent Cloud UI can cause connectivity issues to brokers in the omitted zones, which can result in an unusable cluster.
  
  Note
  
  Confluent Cloud single availability zone clusters will need service and subnet selection in one zone whereas Confluent Cloud multi availability zone clusters will need service and subnet selection in three zones.
8. Select or create a security group for the VPC Endpoints. Add three inbound rules for each of ports 80, 443, and 9092 from your desired source (i.e. your VPC CIDR). The Protocol should be TCP for all three rules. Note: port 80 is not required, but is available as a redirect only to https/443 if desired.
9. Wait for acceptance by Confluent Cloud. This should happen almost immediately (less than 1 minute). After it is accepted, the endpoint will transition from “Pending” to “Active”.

Set up DNS records to use AWS VPC Endpoints¶

DNS changes must be made to ensure connectivity passes through AWS PrivateLink in the supported pattern. Any DNS provider can be used - AWS Route53 (used in this example) is not required. Any DNS provider that can ensure DNS is routed as follows is acceptable.

Note

Run the DNS helper script to identify the DNS Zone records for VPC Endpoints.

Update DNS using AWS Route53 in the AWS console:

Create the Private Hosted Zone.
1. Click Create Hosted Zone.
2. Paste Confluent Cloud DNS into Domain Name. This can be found in the Confluent Cloud UI.
3. Change Type to Private Hosted Zone for Amazon VPC.
4. Select the VPC ID where you added the VPC Endpoint.
5. Click Create.
Set up DNS records for Confluent Cloud single availability zone clusters as follows:
1. Create the following record with the Create Record Set button using the VPC Endpoint DNS Name map from the previous setup in the form
```
*.$domain CNAME “The lone zonal VPC Endpoint” TTL 60
```
  For example:
```
*.l92v4.us-west-2.aws.confluent.cloud CNAME vpce-09f9f4e9a86682eed-9gxp2f7v-us-west-2c.vpce-svc-04689782e9d70ee9e.us-west-2.vpce.amazonaws.com TTL 60
```

Set up DNS records for Confluent Cloud multi availability zone clusters as follows:

Create the following records with the Create Record Set button using the VPC Endpoint DNS Name map from the previous setup in the form
```
*.$domain CNAME “All Zones VPC Endpoint” TTL 60
```
For example:
```
*.l92v4.us-west-2.aws.confluent.cloud CNAME vpce-09f9f4e9a86682eed-9gxp2f7v.vpce-svc-04689782e9d70ee9e.us-west-2.vpce.amazonaws.com TTL 60
```
The CNAME is used to ensure AWS Route53 health checks are utilized in the case of AWS outages.

Create one record per zone (repeat for all zones) in the form.

*.$zoneid.$domain CNAME “Zonal VPC Endpoint” TTL 60

For example:

*.usw2-az3.l92v4.us-west-2.aws.confluent.cloud. CNAME vpce-09f9f4e9a86682eed-9gxp2f7v-us-west-2a.vpce-svc-04689782e9d70ee9e.us-west-2.vpce.amazonaws.com TTL 60
*.usw2-az2.l92v4.us-west-2.aws.confluent.cloud. CNAME vpce-09f9f4e9a86682eed-9gxp2f7v-us-west-2c.vpce-svc-04689782e9d70ee9e.us-west-2.vpce.amazonaws.com TTL 60
*.usw2-az1.l92v4.us-west-2.aws.confluent.cloud. CNAME vpce-09f9f4e9a86682eed-9gxp2f7v-us-west-2b.vpce-svc-04689782e9d70ee9e.us-west-2.vpce.amazonaws.com TTL 60

Validate Connectivity to Confluent Cloud¶

From an instance within the VPC (or anywhere the previous step’s DNS is set up), run the following to validate Kafka connectivity through AWS PrivateLink is working correctly.
1. Set a variable with the cluster bootstrap URL.
```
% export BOOTSTRAP=$ConfluentCloudBootstrap
```
  For example:
```
% export BOOTSTRAP=lkc-nkodz-0l6je.us-west-2.aws.confluent.cloud
```
2. Test connectivity to the cluster.
```
% openssl s_client -connect $BOOTSTRAP:9092 -servername $BOOTSTRAP -verify_hostname $BOOTSTRAP </dev/null 2>/dev/null | grep -E 'Verify return code|BEGIN CERTIFICATE' | xargs
```
3. If the return output is -----BEGIN CERTIFICATE----- Verify return code: 0 (ok), connectivity to the bootstrap is confirmed.
Note

You might need to update the network security tools and firewalls to allow connectivity. If you have issues connecting after following these steps, confirm which network security systems your organization uses and whether their configurations need to be changed. If you still have issues, run the debug connectivity script and provide the output to Confluent Cloud Support for assistance with your PrivateLink setup.
Next, verify connectivity with the Confluent Cloud CLI.
1. Log in to the Confluent Cloud CLI with your Confluent Cloud credentials.
```
ccloud login
```
2. List the clusters in your organization.
```
ccloud kafka cluster list
```
3. Select the cluster with AWS PrivateLink you wish to test.
```
ccloud kafka cluster use ...
```
  For example:
```
ccloud kafka cluster use lkc-a1b2c
```
4. Create a cluster API key to authenticate with the cluster.
```
ccloud api-key create --resource ... --description ...
```
  For example:
```
ccloud api-key create --resource lkc-a1b2c --description "connectivity test"
```
5. Select the API key you just created.
```
ccloud api-key use ... --resource ...
```
  For example:
```
ccloud api-key use WQDMCIQWLJDGYR5Q --resource lkc-a1b2c
```
6. Create a test topic.
```
ccloud kafka topic create test
```
7. Start consuming events from the test topic.
```
ccloud kafka topic consume test
```
8. Open another terminal tab or window.
9. Start a producer.
```
ccloud kafka topic produce test
```
10. Type anything into the produce tab and hit Enter; press Ctrl+D or Ctrl+C to stop the producer.
11. The tab running consume will print what was typed in the tab running produce.
You’re done! The cluster is ready for use.

Limitations¶