Connecting to a PrivateLink Cadence Cluster


This page describes the steps that need to be taken to connect clients in one VPC to a PrivateLink enabled Cadence cluster in another VPC. In short, customers need to create a security group, an endpoint with the endpoint service name of the created Cadence PrivateLink cluster, and a Route 53 record to the endpoint created. 


Retrieve Required Cluster Connection Information

  1. Log into the console, click the created cluster and enter the Connection Info page.
  2. The Connection Info page contains the specific connection details for PrivateLink. The endpoint created in the next section uses the endpoint service name shown below.
  3. In the Connection Info page, identify the region of the created PrivateLink Cadence cluster. For instance, the page shows the region is US_EAST_1, hence access to the AWS VPC Endpoint console in the US_EAST_1 region:
  4. If the PrivateLink Cadence cluster and client are in different AWS accounts, please ensure the AWS Principal of the client AWS account is added to allow cross-account access to the endpoint. For more info, please read Managing Principal ARNs of a PrivateLink Cadence Cluster



Create Endpoint Security Group

A security group is required to allow traffic from your VPC to the PrivateLink endpoint. Your Instaclustr provided Cadence cluster already has a security group applied to ensure the security of your cluster, but an Endpoint cannot be created without having an associated security group. Therefore the security group being created here can be as permissive or as strict as you require. These steps will outline the recommended security group configuration.

  1. In the AWS Console, select the appropriate region for your VPC and navigate to the Security Groups page.
  2. Click “Create security group”.
  3. Under the heading “Security group name”, enter a name for the security group. For example, “companyName-cadence-privatelink-group”. The name cannot be edited after creation, thus it is recommended to use a naming convention which allows easy identification of the PrivateLink endpoint and destination cluster it will be associated with.
  4. Under the heading “Description”, enter a short description of the security group. For example, “Allows access to Cadence cluster via PrivateLink”.
  5. Under the heading “VPC”, search for and select the VPC which will connect to the Cadence cluster via PrivateLink.
  6. Under the Inbound rules heading, click “Add rule”. The rules created here permit traffic outbound from your VPC, inbound to the Cadence cluster over PrivateLink.
  7. Select Custom TCP in the “Type” field. Enter 7933, 7833 and 443 in the “Port range” field (n.b. Port 7933 and 7833 are the Cadence Frontend Service listener port for tChannel/gRPC. When connecting via PrivateLink, these ports are load balanced between all Cadence nodes in your cluster. Port 443 is the Cadence Web listener port, this port will direct to Cadence Web node. All these three ports will not change, and can be verified on your Cadence cluster’s Connection Info page.) Select Custom in the “Source” field, then enter the CIDR of the subnet you will be connecting to the PrivateLink endpoint from (ie. the CIDR within which your EC2 Instance resides). Optionally, add a description in the Description field.
  8. Click “Create security group”, the security group should be created successfully. Take note of the security group name, as it will be required when creating the Endpoint in the following steps.

Create Endpoint and Route 53 Record

  1. On the AWS VPC Endpoint Console page, click “Create endpoint”.
  2. On the creation page under “Service category”, select “Other endpoint services”
  3. In “Service Settings”, paste the endpoint service name from step 2 to the “Service name” field. Click “Verify service” and a green box will appear.
  4. For “VPC”, select the client’s VPC that will connect to the PrivateLink Cadence cluster. Note, the VPC of the client and PrivateLink Cadence cluster should be in the same region as we do not support inter-region access via PrivateLink.
  5. The configuration would then be as follows.
  6. For “Subnets”, please select one “Subnet ID” for each “Availability Zone”. Please note that we recommend that your clients (producers and consumers) be located in separate availability zones to support high availability should any one availability zone be unreachable.
  7. Select the security group that you created earlier. You will get the following configurations. Once done, click “Create endpoint”.
  8. You will be redirected to the main VPC endpoint page which will specifically show the created endpoint. Once the Status of the endpoint reaches Available, copy the first DNS under the “DNS names”.
  9. Head to the Route 53 record home page, enter Hosted Zone and select “Create hosted zones”.
  10. Find the “URL” in Retrieve Required Cluster Connection Information step 2. Under “Advertised Hostname”, enter the “URL” without the first part of the hostname into “Domain name”. For example for, enter
  11. Select “Private hosted zone” as “Type”.
  12. Select the corresponding region and VPC of the client used in step 4. 
  13. Ensure you have the following configurations, click “Create hosted zone”.
  14. You will be redirected to the created private hosted zone.
  15. Select “Create record”.
  16. Under “Record name”, place the rest of the “URL” from step 2. For instance, the “URL” is and we entered in  step 13. Thus the remaining URL to be entered is cadence.
  17. Click the toggle “Alias” and select “Alias to VPC endpoint” from the dropdown box.
  18. Select the same region as the one in step 3 in the next dropdown box.
  19. In the last field, paste the endpoint DNS name from step 8.
  20. The resulting configuration is as follows.
  21. The newly created record will be in the hosted zone. You can now connect to the cluster with or



By Instaclustr Support
Need Support?
Experiencing difficulties on the website or console?
Already have an account?
Need help with your cluster?
Contact Support
Why sign up?
To experience the ease of creating and managing clusters via the Instaclustr Console
Spin up a cluster in minutes