Set up private link

Connect your endpoints using PrivateLink

AWS
Azure

Connect your cluster to an application VPC via AWS PrivateLink.

To use AWS PrivateLink, you need the following:

An AWS user account with an IAM user policy that grants permissions to create, modify, describe, and delete endpoints.
The Amazon resource names (ARN) of security principals to which to grant access to the endpoint.

Make sure that default security group in your application VPC allows internal connectivity. Otherwise, your application may not be able to reach the endpoint.

Make sure that the Enable DNS resolution and Enable DNS hostnames DNS settings in your application VPC are enabled. To access these settings, in the AWS VPC console, select the VPC, click Actions, and choose Edit VPC Settings.

To use AWS PrivateLink to connect your cluster to a VPC in AWS that hosts your application, first create a private service endpoint (PSE) for each region of your cluster, then create corresponding interface VPC endpoints in AWS.

Create a PSE in YugabyteDB Managed

You create the PSEs (one for each region) for your cluster on the cluster Settings tab, or using ybm CLI.

Use YugabyteDB Managed

To create or edit a PSE, do the following:

Select your cluster.
Navigate to Settings > Network Access > Private Service Endpoint.
Click Create Private Service Endpoint or, to edit an existing PSE, Edit Private Service Endpoint to display the Edit Private Service Endpoint sheet.
For each region in your cluster, provide the ARN of an AWS principal you want to grant access. For example, arn:aws:iam::<aws account number>:root.
Click Save.

The endpoints are displayed with the following values:

Host - The host name of the PSE. You use this to connect to your cluster. The host name of a PSE for AWS always ends in aws.ybdb.io.
Service Name - You use this service name when creating the private endpoint in AWS.

You can also create the PSEs during cluster creation.

Use ybm CLI

To create a PSE, do the following:

Enter the following command:
```
ybm cluster network endpoint create \
  --cluster-name <yugabytedb_cluster> \
  --region <cluster_region> \
  --accessibility-type PRIVATE_SERVICE_ENDPOINT \
  --security-principals <amazon_resource_names>
```
Replace values as follows:
- yugabytedb_cluster - name of your cluster.
- cluster_region - cluster region where you want to place the PSE. Must match one of the regions where your cluster is deployed (for example, us-west-2), as well as the region where your application is deployed.
- amazon_resource_names - comma-separated list of the ARNs of AWS principals that you want to grant access. For example, arn:aws:iam::<aws account number>:root.
Note the endpoint ID in the response.

You can also display the PSE endpoint ID by entering the following command:
```
ybm cluster network endpoint list --cluster-name <yugabytedb_cluster>
```
This outputs the IDs of all the cluster endpoints.
After the endpoint becomes ACTIVE, display the service name of the PSE by entering the following command:
```
ybm cluster network endpoint describe --cluster-name <yugabytedb_cluster> --endpoint-id <endpoint_id>
```

Note the following values:

Host - The host name of the PSE. You will use this to connect to your cluster. The host name of a PSE for AWS always ends in aws.ybdb.io.
Service Name - You will use this service name when creating the private endpoint in AWS.

To delete a PSE, enter the following command:

ybm cluster network endpoint delete \
    --cluster-name <yugabytedb_cluster> \
    --endpoint-id <endpoint_id> \

Create an interface VPC endpoint in AWS

You can create the AWS endpoint using the AWS VPC console or from the command line using the AWS CLI.

Use the Amazon VPC console

To create an interface endpoint to connect to your cluster PSE, do the following:

Open the Amazon VPC console.
Switch to the region where your YugabyteDB cluster is deployed.
In the navigation pane, choose Endpoints and click Create endpoint.
Enter a Name tag for the endpoint.
Under Service Category, select Other endpoint services.
Under Service settings, in the Service name field, enter the service name of your cluster PSE and click Verify service.
In the VPC field, enter the ID of the VPC where you want to create the AWS endpoint.
Under Subnets, select the subnets (Availability Zones) to use.

At least one of the subnets should match the zones in your cluster. The endpoint service can only connect from a subnet in the same availability zone as the PSE; if there isn't a subnet in the same zone, create one. Always verify the Availability Zone ID as availability zone names can vary across different accounts.
Under Security groups, select the security groups to associate with the endpoint network interfaces.
Click Create endpoint.

The endpoint is added to the Endpoints in AWS.
Select the endpoint and on the endpoint details page, click Actions and choose Modify private DNS name so that the Private DNS names enabled setting is set to Yes.

The initial endpoint status is Pending. After the link is validated, the status is Available. The private DNS name may take a few minutes to propagate before you can connect.

You can now connect to your cluster from your application in AWS using your cluster PSE host address (for example, pse-us-west-2.65f14618-f86a-41c2-a8c6-7004edbb965a.aws.ybdb.io).

Use AWS CLI

Set up DNS support

Check if enableDnsHostnames and enableDnsSupport are set to true for the application VPC where you want to add the interface VPC endpoint:

aws ec2 describe-vpc-attribute --vpc-id <application_vpc_id> --attribute enableDnsSupport

aws ec2 describe-vpc-attribute --vpc-id <application_vpc_id> --attribute enableDnsHostnames

Replace values as follows:

application_vpc_id - ID of the AWS VPC. Find this value on the VPC dashboard in your AWS account.

If they are not set to true, set them as follows:

aws ec2 modify-vpc-attribute \
    --enable-dns-hostnames \
    --enable-dns-support \
    --vpc-id <application_vpc_id>

Create a security group for the endpoint

Create a separate security group for the interface endpoint to simplify security management (by default, AWS creates the endpoint in the default security group) and add a rule to allow traffic to the YBM PSE. Note that the rule may take a few minutes to propagate to the endpoint NICs in the security group.

aws ec2 create-security-group \
    --group-name ybm-interface-endpoint \
    --description "Security group for interface endpoint that connects to ybm pse" \
    --vpc-id <application_vpc_id>

This command returns the security group ID as, for example, GroupId: sg-903004f8. This ID is referred to as endpoint_security_group_id in the following commands.

Add an ingress rule for YSQL as follows:

aws ec2 authorize-security-group-ingress \
    --group-id <endpoint_security_group_id> \
    --port 5433 \
    --source-group <application_security_group_id> \
    --protocol tcp

And an ingress rule for YCQL as follows:

aws ec2 authorize-security-group-ingress \
    --group-id <endpoint_security_group_id> \
    --port 9042 \
    --source-group <application_security_group_id> \
    --protocol tcp

Replace values as follows:

endpoint_security_group_id - the security group ID of the endpoint
application_security_group_id - the security group ID of the application VPC

Create an interface VPC endpoint

Obtain the subnet IDs of the application VPC, as follows:

aws ec2 describe-subnets \
    --filters "Name=vpc-id,Values=<application_vpc_id>" \
    --query "Subnets[*].SubnetId"

This command returns the subnet IDs of the application VPC (subnet_ids in the following command). Note that the interface endpoint can connect only from a subnet in the same availability zone as the PSE. If there isn't a subnet in the same zone, create one.

Create the interface VPC endpoint, as follows:

aws ec2 create-vpc-endpoint \
    --vpc-endpoint-type Interface \ 
    --vpc-id <application_vpc_id> \
    --service-name <pse_service_name> \
    --subnet-ids <subnet_ids> \
    --security-group-ids <endpoint_security_group_id> \
    -–private-dns-enabled

Replace values as follows:

application_vpc_id - ID of the AWS VPC. Find this value on the VPC dashboard in your AWS account.
pse_service_name - service name of your PSE, which you noted down when creating the PSE.
subnet_ids - the subnet IDs, separated by whitespace, that your application VPC uses. You can also find these values under Subnets in your AWS VPC console. The endpoint service can connect only from a subnet in the same availability zone as the PSE. If there isn't a subnet in the same zone, create one. Always verify the Availability Zone ID as availability zone names can vary across different accounts.
endpoint_security_group_id - the security group ID of the endpoint

Set up private link

Create a PSE in YugabyteDB Managed

Use YugabyteDB Managed

Use ybm CLI

Create an interface VPC endpoint in AWS

Use the Amazon VPC console

Use AWS CLI

Set up DNS support

Create a security group for the endpoint

Create an interface VPC endpoint

Next steps