1. Home
2. Networking
3. Private Links

AWS PrivateLink

AWS PrivateLink offers one-way connectivity from your VPC to a Confluent Cloud cluster, without any coordination of CIDR ranges. PrivateLink connections to Confluent Cloud can only be made from VPCs in registered customer AWS accounts.

For more information about AWS PrivateLink, see the AWS documentation.

Create an AWS PrivateLink connection to Confluent Cloud

Follow the steps below to create an AWS PrivateLink to connect to your Confluent Cloud cluster.

Note

For an overview of AWS PrivateLink and illustrated steps on getting started with AWS PrivateLink in Confluent Cloud, see Announcing AWS PrivateLink Support in Confluent Cloud.

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

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.

To create an AWS PrivateLink connection for a Dedicated cluster in Confluent Cloud on AWS, follow these steps.

1. Register your AWS account with Confluent Cloud using the Confluent Cloud Console.
2. Set up the VPC Endpoints to Confluent Cloud PrivateLink service in your AWS account using the AWS portal.
3. Set up Availability Zone mapped DNS records to use AWS VPC Endpoints using the AWS portal.
4. Validate connectivity to Confluent Cloud.

Prerequisites

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

1. Navigate to the Cluster Settings page, click the Networking tab, and click Add Account.
2. 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 Console. 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 Console, you must configure VPC Endpoints in your VPC to make the AWS PrivateLink connections to your Confluent Cloud cluster.

Note

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

1. In the Confluent Cloud Console, find the following information for your Confluent Cloud cluster under the Cluster Settings section.

   • Kafka Bootstrap (in the General tab)
   • Availability Zone IDs (in the Networking tab)
   • VPC Service Endpoint Name (in the Networking tab)
   • DNS Domain Name (in the Networking tab)
   • Zonal DNS Subdomain Names (in the Networking tab)

2. Verify subnet availability.

   The Confluent Cloud VPC and cluster is created in specific zones that, for optimal usage, should match the zones of the VPC you want to make the AWS PrivateLink connections from. You must have subnets in your VPC for these zones so that IP addresses 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 Zones for your Confluent Cloud cluster in the Confluent Cloud Console.

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

   Note

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

3. 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 Console.

   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 zones for your Confluent Cloud cluster from the Networking tab in the Confluent Cloud Console. Select the service in these zones. Ensure the desired subnet is selected for each zone. Failure to add all zones as displayed in the Confluent Cloud Console can cause connectivity issues to brokers in the omitted zones, which can result in an unusable cluster.

      Note

      Confluent Cloud single availability zone clusters need service and subnet selection in one zone whereas Confluent Cloud multi-availability zone clusters 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 (your VPC CIDR). The Protocol should be TCP for all three rules.
      • 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 a 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 Management Console:

1. 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 Console.
   3. Change Type to Private Hosted Zone for Amazon VPC.
   4. Select the VPC ID where you added the VPC Endpoint.
   5. Click Create.

2. 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
      

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

   1. 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 used in the case of AWS outages.

   2. 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

1. 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 an environment 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 Support for assistance with your PrivateLink setup.

2. Next, verify connectivity with the Confluent Cloud CLI.

   1. Log in to the Confluent 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.

3. You’re done! The cluster is ready for use.

Limitations

• The Africa (Cape Town) Region availability zone af-south-1 is not supported for AWS PrivateLink clusters in Confluent Cloud. Instead, you can use VPC peering for clusters in this region, or use AWS PrivateLink with clusters in different regions.
• Supported and unsupported availability zones in AWS us-east-1 region for AWS PrivateLink clusters in Confluent Cloud:
  • Supported availability zones: use1-az1, use1-az4, and use1-az5
  • Unsupported availability zones: use1-az2, use1-az3, and use1-az6
• Cross-region AWS PrivateLink connections are not supported.
• AWS PrivateLink is only available for use with Dedicated clusters.
• Existing Confluent Cloud clusters cannot be converted to use AWS PrivateLink.
• Fully-managed Confluent Cloud connectors can connect to sources or sinks using a public IP. Sources or sinks in the customer network with private IP are not supported.
• AWS PrivateLink connections cannot be shared across multiple Confluent Cloud clusters. Separate AWS PrivateLink connections must be made to each Confluent Cloud cluster.
• Availability zone selection for placement of Confluent Cloud cluster and AWS PrivateLink service is not supported.
  • Each Confluent Cloud multi-availability zone cluster using AWS PrivateLink will be provisioned with service endpoints in three availability zones. For those AWS regions that have more than three availability zones, the availability zones will be selected based on Confluent Cloud placement policies. One of the following options can be used to ensure connectivity to a Confluent Cloud multi availability zone cluster over AWS PrivateLink:
    • Provision subnets in your VPC in all availability zones in the region
    • Provision subnets in your VPC in at least the three availability zones in which the PrivateLink service endpoints are provisioned. This information will be available in the Confluent Cloud Console under the Networking tab on the Cluster Settings page after the Confluent Cloud cluster is provisioned.
    • The following regions currently have more than three availability zones: us-east-1 (N. Virginia) and us-west-2 (Oregon)
  • Each Confluent Cloud single availability zone cluster using AWS PrivateLink will be provisioned with service endpoints in one availability zone. The availability zone will be selected based on Confluent Cloud placement policies. One of the following options can be used to ensure connectivity to a Confluent Cloud single availability zone cluster over AWS PrivateLink:
    • Provision subnets in your VPC in all availability zones in the region
    • Provision subnets in your VPC in at least the single availability zone in which the PrivateLink service endpoint is provisioned. This information will be available in the Confluent Cloud Console under the Networking tab on the Cluster Settings page after the Confluent Cloud cluster is provisioned.
• For requirements of the AWS PrivateLink feature, see Prerequisites.