Last Updated: 2024-04-16

Background

AWS PrivateLink allows private connectivity between virtual private clouds (VPC), supported AWS services, and on-premises networks. This connection does not expose traffic to the public internet, making it a great choice for secure client or tool connectivity and other use cases.

Starburst Galaxy extends support for AWS PrivateLink across certain connections. This tutorial will guide you through configuring PrivateLink for a client or tool connection to a Starburst Galaxy cluster.

Scope of tutorial

In this tutorial, you will learn how to configure AWS PrivateLink for client or tool connectivity to Starburst Galaxy.

Learning objectives

Once you've completed this tutorial, you will be able to:

• Configure AWS PrivateLink for connectivity from Starburst Galaxy to a client or tool.
• Use PrivateLink to securely connect your client or tool to a Starburst Galaxy cluster.

Prerequisites

• You need a Starburst Galaxy account to complete this tutorial. Please see Starburst Galaxy: Getting started for instructions on setting up a free account.
• You need the Trino CLI to complete testing at the end of this tutorial. You can download the latest version here. This tutorial uses version 429-e.0.
• To use the Trino CLI, you must have Java 17 installed. You can download a version for your system here if needed.

About Starburst tutorials

Starburst tutorials are designed to get you up and running quickly by providing bite-sized, hands-on educational resources. Each tutorial explores a single feature or topic through a series of guided, step-by-step instructions.

As you navigate through the tutorial you should follow along using your own Starburst Galaxy account. This will help consolidate the learning process by mixing theory and practice.

Background

If you are configuring PrivateLink for the first time you are encouraged to work with a Starburst technical resource. This individual will work with you to set up the environment needed to complete the tutorial.

Contacting your technical resource

To be assigned this resource, you should reach out to your regular Starburst account team for assistance.

Working together

Once assigned, your Starburst technical resource will work with you to set up an environment where you can complete the tutorial.

Please review the following overview of this process before beginning the tutorial.

Your responsibilities:

• Submit a support ticket via Starburst Galaxy. Provide your AWS account ID which they will use to grant your account access to the Starburst Galaxy Endpoint Service.
• Create an Endpoint in the AWS console using the Endpoint Service Name provided by Starburst. Submit another support ticket to notify support when this is complete.
• The Starburst support team will accept the connection request by the Endpoint. They will notify you when they have accepted it.
• Create a PrivateLink cluster in Starburst Galaxy.
• Create a new Route 53 Private Hosted zone for galaxy.starburst.io in the AWS console.
• Create a new A record pointing to your Starburst Galaxy PrivateLink cluster.
• Create a new wildcard record pointing to *.galaxy.starburst.io in the AWS console.
• Test connectivity to the PrivateLink cluster using the DNS name you just configured in Route 53.

Steps to add an additional Starburst Galaxy PrivateLink cluster in the same AWS VPC region:

• Create a PrivateLink cluster in Starburst Galaxy.
• Create a new A record pointing to your Starburst Galaxy PrivateLink cluster.
• Test connectivity to the PrivateLink cluster using the DNS name you just configured in Route 53.

Background

A wildcard DNS record is a type of DNS record that allows you to specify a wildcard character (*) as part of the domain name. This wildcard character matches any subdomain that has not been explicitly defined in the DNS zone.

For example, if you set up a wildcard DNS record for "*.example.com" to point to a specific IP address, then any subdomain of "example.com" that has not been explicitly defined (e.g., "sub1.example.com", "sub2.example.com", etc.) will automatically resolve to the specified IP address.

Wildcard DNS records are commonly used in scenarios where you want to route all subdomains of a domain to a single location or when you want to simplify DNS configuration for a large number of subdomains.

In this tutorial, you are going to use the wildcard DNS record to route all galaxy.starburst.io subdomains to a VPC Endpoint that you create in your AWS environment.

Wildcard DNS records and VPC Endpoints

Currently, you can only connect to a Starburst Galaxy PrivateLink cluster from one VPC per region. To set this up, you need to create a wildcard DNS record for each region, which directs traffic to a single VPC Endpoint. This means that any request resolved to the wildcard subdomain will be directed to that specific VPC Endpoint.

Background

It's time to get started. In this section, you'll begin by obtaining your AWS account ID and providing it to Starburst support via a support ticket.

There are many ways to find your AWS account ID. These instructions will illustrate one way.

Step 1: Sign in to AWS console

You're going to start by signing in to your AWS console. Remember that this should be the AWS account that your client or tool will be connecting from. It may not be the same account that contains your data sources.

• Sign in to your AWS account.
• Locate your login name in the top-right corner of the screen, and click to open the drop-down menu.
• Click the copy button to the right of your Account ID.
• Give the Account ID to your Starburst technical resource. They will use it to allow your AWS account to connect to the Starburst Galaxy Endpoint service.

Step 2: Open support ticket

You are going to use the automated assistant in Starburst Galaxy to open a support ticket and provide support with the Account ID that you just copied.

• Log in to Starburst Galaxy.
• Click the support icon located at the bottom right of the screen.
• Select Chat with technical support.
• Select Submit a Support Ticket.
• The automated assistant will ask you to provide your email address, first name, and last name.
• When you receive the prompt to describe your issue, note that you would like support to grant your AWS account access to the Starburst Galaxy Endpoint Service. Be sure to include your AWS Account ID in the request.
• Wait for Starburst support to confirm that they have granted your AWS account access to the Starburst Galaxy Endpoint Service. This should take no longer than 24 - 48 hours.

Step 3: Select the appropriate Endpoint Service name

In the next section, you will create an Endpoint, and you will need to supply the correct Starburst Galaxy Endpoint Service name as part of the configuration. Locate your region from the list below, and copy the corresponding Endpoint Service name.

• us-east-1: com.amazonaws.vpce.us-east-1.vpce-svc-0548ad6a109d47141
• us-east-2: com.amazonaws.vpce.us-east-2.vpce-svc-0448777022b5867f2
• us-west-1: com.amazonaws.vpce.us-west-1.vpce-svc-054aa50ccbc1e0086
• us-west-2: com.amazonaws.vpce.us-west-2.vpce-svc-0e240c1078174a65c
• ap-southeast-2: com.amazonaws.vpce.ap-southeast-2.vpce-svc-0ae51f2ae863da09e
• ap-southeast-1: com.amazonaws.vpce.ap-southeast-1.vpce-svc-09a6b78555f8dc6c5
• ca-central-1: com.amazonaws.vpce.ca-central-1.vpce-svc-0cc1c1b214fd4862b
• eu-central-1: com.amazonaws.vpce.eu-central-1.vpce-svc-0db312c5a1c77ce4a
• eu-west-1: com.amazonaws.vpce.eu-west-1.vpce-svc-073283405f562e5dd
• eu-west2: com.amazonaws.vpce.eu-west-2.vpce-svc-0be5f607056167f16
• af-south-1: com.amazonaws.vpce.af-south-1.vpce-svc-01fec2b6e5b757beb

Background

Now it's time to create an Endpoint.

In the context of AWS PrivateLink, a VPC Endpoint allows users to securely connect their VPC to an Endpoint Service. In this case, you will be connecting to the Starburst Galaxy Endpoint Service.

Step 1: Start the Endpoint wizard

• Navigate to the VPC dashboard in the AWS console. This can be done by searching for VPC and clicking on VPC in the results list.
• From the left-hand navigation menu, expand Virtual private cloud, and click Endpoints.
• Click the Create endpoint button on the right side of the dashboard.

Step 2: Verify Starburst Galaxy Endpoint Service

It's time to start configuring your new Endpoint, starting with a name tag and Endpoint Service with which to connect. This is the time to verify connection with the Starburst Galaxy Endpoint Service you copied earlier in this tutorial.

• In the Name tag field, enter a name using the guidelines above.
• Under the Service category section, select Other Endpoint Services.
• In the Service name field, input the Starburst Galaxy Endpoint Service name you stored earlier.
• Click the Verify service button.
• Ensure that you received the "Service name verified" message before moving on.

Step 3: Select VPC and Subnets

Now it's time to select the VPC in which to create the Endpoint.

• Expand the VPC drop-down menu, and select the VPC that your clients or tools are in or will be connecting through.
• Under Subnets, check the box in front of all listed Availability Zones.
• For each Availability Zone, under the Subnet ID column, select the private subnet you wish to use. From each subnet you select, an IP address will be reserved for your Endpoint.

Step 4: Select security group

The final step to configure your Endpoint is to choose a security group. Because this is a private Endpoint, the security group will only need to allow the IP CIDR from the hosts where your clients or tools are running.

• In the Security group filter box, enter the name of the security group you would like to use.
• Use the check box to select the security group from the list.
• Click the Create endpoint button.
• Submit another support ticket to notify Starburst support that you've created the Endpoint so that they can accept the Endpoint connection request.

Step 5: Wait for Starburst to accept Endpoint connection

You need to wait for the Endpoint connection request to be accepted before moving on.

• Wait for the Endpoint Status column to change from Pending acceptance to Available.

Step 6: Record DNS name and Subnet IPs

Later in this tutorial, you will be creating a DNS alias record for your Endpoint DNS name. You're going to record that name now and save it in a safe place for later use. You're also going to record your Endpoint Subnet IPs for validation in a later step.

• Click the checkbox next to your Endpoint to select it from the list.
• Scroll down to view the Endpoint details.
• Under DNS names, copy the first name on the list.
• Save the DNS name in a text editor or other easily accessible place for future use.
• Click the Subnets tab.
• Record all IPv4 addresses.

Background

It's time to switch gears and work in the Starburst Galaxy UI. Your next task is to create a cluster that is only accessible via PrivateLink. When your client or tool uses PrivateLink to connect to Starburst Galaxy, it will be connecting to the cluster you create.

Step 1: Sign into Starburst Galaxy

• Sign into Starburst Galaxy in the usual way. If you have not already set up an account, you can do that here.
• Input your Email and Password.
• Click the Sign in to Starburst Galaxy button.

Step 2: Set your role

Starburst Galaxy separates users by role. Your current role is listed in the top right-hand corner of the screen.

Creating a cluster in Starburst Galaxy will require access to a role with appropriate privileges. Today, you'll be using the accountadmin role.

• Check your role, to ensure that it is set to accountadmin.
• If it is set to anything else, use the drop-down menu to select the correct role.

Step 3: Create a new cluster

It's time to create your cluster. In Starburst Galaxy, the Clusters pane is used for all cluster operations.

• From the left-hand navigation menu, select Clusters.
• Select the Create cluster button.

Step 4: Configure cluster

It's time to add some details to your cluster, such as the name, catalogs to include, and region.

• In the Cluster name field, provide a meaningful name.
• Expand the Catalogs drop-down menu, and select all catalogs you would like to include in the cluster.
• Expand the Cloud provider region drop-down menu, and select your region.

Step 5: Configure Cluster type

Next you'll choose the execution mode, cluster size, and auto-suspend time period for your cluster.

• Expand the Execution mode drop-down menu, and select your preferred execution mode.
• Expand the Cluster size drop-down menu, and select your preferred cluster size. Do not choose free.
• Expand the Auto suspend drop-down menu, and select your preferred auto-suspend time period for the cluster.

Step 6: Configure cluster for PrivateLink

The option to make the cluster accessible only via PrivateLink is located in the Advanced settings menu.

• Expand the Advanced settings menu.
• Select the option for cluster accessible only via Private Link.
• Click the Create cluster button.

Step 8: Copy Cluster Host name

While you're in the Clusters pane, you need to record the Host name for your PrivateLink cluster for later use.

• Click the Connection info button for your PrivateLink cluster.
• Copy the Host name and save it in a text editor for later reference.

Background

AWS Route 53 is a scalable and highly available Domain Name System (DNS) web service offered by Amazon Web Services. It is designed to route end users to internet applications by translating human-readable domain names (like www.example.com) into the numeric IP addresses (like 192.0.2.1) used by computers to connect to each other.

In AWS Route 53, a private hosted zone is a DNS zone that is used to manage domain names and their corresponding DNS records within an Amazon VPC. Private hosted zones are only accessible from within the specified VPC, making them ideal for internal resources that should not be accessible from the public internet.

When you create a private hosted zone in Route 53, you can define custom domain names (e.g., mycompany.local) and create DNS records (such as A, AAAA, CNAME, etc.) for those domain names. These DNS records can then be used to route traffic within your VPC to the appropriate resources, such as EC2 instances, load balancers, or other services.

After you create the private hosted zone in Route 53, you'll be creating two DNS records. The first will route traffic to your PrivateLink cluster based on its host name. The second record will ensure that any redirections come back to the correct cluster.

Step 1: Create hosted zone

It's time to switch back to working in the AWS console. Hosted zones can be created from the Route 53 dashboard in AWS.

• Navigate to the Route 53 dashboard in the AWS console. This can be done by searching for Route 53 and selecting Route 53 from the results list.
• Use the left-hand navigation menu to select Hosted zones.
• Click the Create hosted zone button.

Step 2: Configure hosted zone

It's time to configure the hosted zone by providing the name of the domain you want to route traffic for and selecting the type of hosted zone you would like.

• In the Domain name field, enter one of the following names, depending on your Starburst Galaxy account domain.

• Development environment: private.trino.galaxy-dev.io
• Demo environment: private.trino.galaxy-demo.io
• Production environment: private.trino.galaxy.starburst.io
• Under Type, select Private hosted zone.

Step 3: Select VPC

You're almost finished with the private hosted zone configuration. The final step is to select a VPC to associate with the hosted zone.

• Click to expand the Region drop-down menu, and select your region from the list.
• In the VPC ID field, enter your Endpoint VPC.
• Click the Create hosted zone button.

Background

Now that you've created a hosted zone, you can create the two required DNS alias records. After you've completed this section, you'll be ready to test your PrivateLink connection.

Step 1: Create first DNS alias record

This record will route traffic to your Starburst Galaxy PrivateLink cluster based on its host name.

You should be on the information page for the Private hosted zone you created in the previous section.

• Click the Create record button.

Step 2: Configure first record

It's time to configure your record by giving it a name and identifying where it should route to.

• In the Record name field, enter the Starburst Galaxy PrivateLink cluster host name that you recorded in a previous step. Do not include the domain name portion of the host name as it is added for you by Route 53.

Example host name: erosas-privatelink-cluster-us-east-1.private.trino.galaxy.starburst.io

Example host name with domain name removed: erosas-privatelink-cluster-us-east-1

• Click the Alias slider to enable it.
• There are three fields to complete in the Route traffic to section.
• Expand the first dropdown menu below Route traffic to, and select Alias to VPC endpoint.
• Expand the second dropdown menu below Route traffic to, and select your VPC endpoint region.
• In the third field below Route traffic to, enter the DNS name that you copied earlier in this tutorial.

• Click the Create records button.

Step 3: Create wildcard DNS record

This second record will ensure that any traffic redirections are routed back to your PrivateLink cluster.

• Click the Create record button again.
• In the Record name field, enter one of the following based on your VPC Endpoint region. Notice there is no dash between the region code and the region number.

us-east-1: *.aws-us-east1

us-east-2: *.aws-us-east2

us-west-1: *.aws-us-west1

us-west-2: *.aws-us-west2

ap-southeast-2: *.aws-ap-southeast2

ap-southeast-1: *.aws-ap-southeast1

ca-central-1: *.aws-ca-central1

eu-central-1: *.aws-eu-central1

eu-west-1: *.aws-eu-west1

eu-west-2: *.aws-eu-west2

af-south-1: *.aws-af-south1

• Click the Alias slider to enable it.
• There are three fields to complete in the Route traffic to section.
• Expand the first dropdown menu below Route traffic to, and select Alias to VPC endpoint.
• Expand the second dropdown menu below Route traffic to, and select your VPC endpoint region.
• In the third field below Route traffic to, enter the DNS name that you copied earlier in this tutorial.
• Click the Create records button.

Background

You've completed all the necessary steps to configure AWS PrivateLink for client or tool connectivity to Starburst Galaxy. Your final task is to test the connection. We will use the Trino CLI as the test client.

Step 1: Run DNS lookup test

You'll need to confirm that this test returns the Subnet IPs from your VPC Endpoint. Recall that you copied those earlier in this tutorial. The command you use to run the DNS lookup test will depend on your operating system.

Windows users

• Run the following command in a PowerShell window. Be sure to replace your_dns_name with your actual DNS name (ex. erosas-privatelink-cluster-us-east-1.private.trino.galaxy.starburst.io)

nslookup your_dns_name

• Confirm you see the Subnet IPs from your VPC Endpoint listed under the Non-authoritative answer heading.

Mac/Linux users

• Run the following command in a terminal window. Be sure to replace your_dns_name with your actual DNS name (ex. erosas-privatelink-cluster-us-east-1.private.trino.galaxy.starburst.io)

dig your_dns_name

• Confirm you see the Subnet IPs from your VPC Endpoint listed under the Answer Section heading.

Step 2: Test connection to Trino CLI

If you haven't done so already, you can visit the Starburst Software Downloads site to get the latest version of the Trino CLI. These instructions use the trino-cli-429-e.0-executable.jar.

The command you use to connect to the Trino CLI will depend on your operating system.

Windows users

• Run the command below to connect to the Trino CLI.
• Replace with your actual DNS name (ex. erosas-privatelink-cluster-us-east-1.private.trino.galaxy.starburst.io)
• Replace with your actual Starburst Galaxy URL (ex. erosas.galaxy.starburst.io)
• Enter your password when prompted.

java -jar trino --server https://<your_dns_name> --user <your_galaxy_url>/accountadmin --password --debug

Mac/Linux users

• Run the command below to connect to the Trino CLI.
• Replace with your actual DNS name (ex. erosas-privatelink-cluster-us-east-1.private.trino.galaxy.starburst.io)
• Replace with your actual Starburst Galaxy URL (ex. erosas.galaxy.starburst.io)
• Enter your password when prompted.

./trino --server https://<your_dns_name> --user <your_galaxy_url>/accountadmin --password --debug

Step 3: Confirm connection to Trino CLI

Let's confirm that the connection was successful by running a simple SQL command.

• Run the following command to list the catalogs connected to your cluster.

SHOW CATALOGS;

Tutorial complete

Congratulations! You have reached the end of this tutorial, and the end of this stage of your journey.

You're all set! Now you can use PrivateLink for client or tool connectivity to Starburst Galaxy.

Continuous learning

At Starburst, we believe in continuous learning. This tutorial provides the foundation for further training available on this platform, and you can return to it as many times as you like. Future tutorials will make use of the concepts used here.

Next steps

Starburst has lots of other tutorials to help you get up and running quickly. Each one breaks down an individual problem and guides you to a solution using a step-by-step approach to learning.

Tutorials available

Visit the Tutorials section to view the full list of tutorials and keep moving forward on your journey!