Azure Private Link #

Starburst Galaxy supports Azure Private Link for some catalogs. This page provides a general overview of Galaxy’s support for Azure Private Link. It is not intended to be a comprehensive guide to creating and administering Azure Private Link.

Support for Azure Private Link #

Starburst Galaxy supports Azure Private Link for the following data sources:

• Azure Data Lake Storage
• Azure database PaaS
• An Azure VM instance hosting the following databases
  • Oracle
  • PostgreSQL
  • MySQL
• Elasticsearch
• MariaDB
• SQL Server
• MongoDB
• MySQL
• Oracle
• PostgreSQL
• Snowflake

General setup phases #

To configure a Starburst Galaxy catalog to connect to a data source using the Azure Private Link service, you must configure certain features of the data source to prepare for the connection. There are two phases:

1. In the data source: Configure your data source to connect with Starburst Galaxy using Azure Private Link. See the step-by-step instructions for the following data sources:

   • Azure Private Link for ADLS
   • Azure Private Link for Azure database PaaS
   • Azure Private Link for a database running a VM
     
     

2. In Starburst Galaxy: Contact your Starburst account team for support.

Azure Private Link overview #

Starburst Galaxy supports secure connections to data sources with Azure Private Link.

Azure data sources can take advantage of the Azure Private Link service as one way to secure access without exposing the data source to the public internet. These data sources then operate within a virtual network within Azure.

Data source requirements #

When you create your Starburst Galaxy cluster and configure a catalog, you must deploy your cluster in the same region as your data source. Starburst Galaxy does not support cross-region connections with Azure Private Link.

Once configured, all traffic from to this data source is routed through Azure Private Link. You can federate your queries across multiple data sources that use Private Link in the same cluster.