Last Updated: 2024-03-20


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 data federation across cloud and on-prem networks.

Starburst Galaxy extends support for AWS PrivateLink across certain catalogs. This tutorial will guide you through the process of configuring PrivateLink for an on-premises data source.

Scope of tutorial

In this tutorial, you will learn how to configure AWS PrivateLink for an on-premises data source.

Learning objectives

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


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.


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:


Understanding the AWS PrivateLink on-prem architecture is important when completing the steps in this tutorial.

In this section you will learn about this architecture and the way that Starburst Galaxy uses it to securely connect private clouds.

Reference architecture

The following diagram illustrates a PrivateLink connection between the Starburst Galaxy VPC, your VPC, and your on-prem data source.

Review the diagram below for more information.


It's time to get started. In this section, you'll begin by obtaining some key information about your data source, including:

You'll need this information to create a target group and load balancer in the next sections of this tutorial.

Step 1: Record data source IP address and Port number

For Starburst Galaxy to connect to your data source using PrivateLink, you will need to know both the IP address and Port number for your data source.

How you do this will vary depending on the implementation and underlying technology used to construct your on-prem data source.

The following are examples of each:


Now it's time to set up a target group. In the context of AWS, a target group is responsible for directing incoming traffic from a load balancer to designated targets, such as cloud instances, containers, or IP addresses.

In this tutorial, the target group you create will play a crucial role in routing traffic to your data source's IP address. This ensures efficient communication between the load balancer and data source, optimizing performance and reliability.

Step 1: Start the target group wizard

AWS makes creating target groups easy with a creation wizard, accessed through the EC2 dashboard. You are going to use that wizard to create your target group.

Step 2: Provide a target group name

Now it's time to configure your new target group.

AWS will ask you to select a target type and provide a meaningful name.

Step 3: Configure the target group

Next, you're going to configure your target group for use with your data source. To do this, you're going to use some of the details that you copied into your text editor earlier in this tutorial.

Step 4: Complete configuration process

Almost there! For the final step, you're going to finish the configuration process and create the target group.


Now it's time to create a network load balancer. In AWS, a Network Load Balancer (NLB) is a service that automatically distributes incoming network traffic across multiple targets based on IP protocol data. This includes Amazon EC2 instances, containers, and IP addresses. Load balancers are also configurable across either a single AWS Availability Zone or multiple Availability Zones.

After configuring PrivateLink, an endpoint in the Starburst Galaxy VPC will connect to your Network Load Balancer using a service located in your VPC.

Step 1: Start the load balancer wizard

Once again, AWS makes the process of creating a load balancer easy by providing a wizard.

Step 2: Select load balancer type

AWS load balancers come in several different types. These include Application Load Balancers, Network Load Balancers, and Gateway Load Balancers.

For this tutorial, you're going to select the Network Load Balancer.

Step 3: Name your load balancer

It's time to start configuring your new load balancer, starting with a name.

Step 4: Configure the load balancer

Next, you're going to configure your load balancer for use with your on-prem data source.

Step 5: Configure AWS availability zone mappings

Now it's time to map AWS availability zones to subnets for your load balancer. You will need to map each listed availability zone to a private subnet capable of routing traffic to your on-prem data source.

Step 6: Configure security group IP CIDR

Next, it's time to select a security group to control access between your load balancer and data source. Without this security group, your network load balancer will accept all connections, creating a security risk in production environments.

Step 7: Configure port number and target group

Step 8: Wait for load balancer to activate

That's it! Your load balancer is now being created. This process takes between three to five minutes.


Now it's time to create an endpoint service.

In the context of AWS PrivateLink, an endpoint service allows you to expose services running in your VPC to other accounts within the same AWS region using a private connection.

Step 1: Start the endpoint service wizard

Just like target groups and load balancers, AWS includes a wizard to help you create an endpoint service.

Step 2: Name your endpoint service

It's time to start configuring your new endpoint service, starting with a name.

Step 3: Configure endpoint service

Now it's time to configure your endpoint service. To do this, you're going to make sure that it connects with your network load balancer and uses the correct IP address.


Time to switch gears. You've completed all of the steps required on your own. Now it's time to contact the Starburst support team to finish the last steps.

Step 1: Enter the Starburst Galaxy ARN

In the last section of this tutorial, you created your endpoint service. At the end of that process, you are directed to a page that displays the details of that service.

You're going to use this section to input the Starburst Galaxy Amazon Resource Name (ARN).

Step 2: Record Service name

Now it's time to locate and copy the service name for your endpoint service. This is one of the endpoint service details listed in AWS.

The Starburst support team will use it to create the endpoint in Starburst Galaxy.

Step 3: Open support ticket

You are going to use the automated assistant in Starburst Galaxy to open a support ticket and provide support with the Service name that you just copied. You will also need to provide the port your database is listening on and your preferred Starburst Galaxy PrivateLink configuration name.

Step 4: Select the Starburst Galaxy endpoint

Do not begin this step until you receive confirmation that the Starburst Galaxy endpoint has been created successfully.

Step 5: Accept the endpoint connection request

Now that you've selected the Starburst Galaxy endpoint, it's time to accept the connection request.

Step 6: Confirm endpoint connection

That's it. The connection is now being created. This process takes between 1 to 3 minutes to complete.

When this process is complete, you are finished and ready to start using PrivateLink.

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 to configure access to your organization's on-prem data.

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!

Start Free with
Starburst Galaxy

Up to $500 in usage credits included

  • Query your data lake fast with Starburst's best-in-class MPP SQL query engine
  • Get up and running in less than 5 minutes
  • Easily deploy clusters in AWS, Azure and Google Cloud
For more deployment options:
Download Starburst Enterprise

Please fill in all required fields and ensure you are using a valid email address.