Access VeloDB from Your VPC on Azure

Before you begin, read Access VeloDB from your VPC for the connection direction, ownership model, and network-control scope.

1. On the target warehouse, open the Connection page, select the Private Link tab, and click New Connection under Access VeloDB from Your VPC.

2. Click Set up one or more endpoints to open Azure PrivateLink.

   

3. On the Basics tab, verify that the region matches the VeloDB warehouse, complete the form, and click Next: Resource.

   

   Parameter	Category	Description
   Subscription	Project details	Subscription to use for access.
   Resource group	Project details	Resource group for the private endpoint. Create one if none is suitable.
   Name	Instance details	Private endpoint instance name.
   Network Interface Name	Instance details	Auto-generated from the instance name. You can edit it.
   Region	Instance details	Must match the warehouse region.

4. On the Resource tab, choose Connect to an Azure resource by resource ID or alias, paste the Service Alias from the VeloDB endpoint service information panel, and click Next: Virtual Network.

   

5. On the Virtual Network tab, select the VNet and subnet for the endpoint, and click Next: DNS.

   

6. Keep the default settings on the DNS and Tags tabs. A DNS record is required for private connectivity. See the Azure Private DNS documentation for details. Review the configuration and click Create.

   

   

   

7. When the endpoint status changes from Created to OK, the PrivateLink connection is ready.

   

   

8. Refresh the VeloDB Cloud Connection page. The endpoint list shows the connection details.

   

9. Click Find DNS Name in the endpoint list to retrieve the endpoint IP address or DNS name.

   

10. Use the Connection Examples popover on the Connection page for snippets covering MySQL and HTTP.

    

11. Configure private DNS for HTTPS.

    Note This step is required only if TLS is enabled for your warehouse. TLS is supported in version 26.0.5 and later in the 26.0.x release series, and version 26.1.2 and later in the 26.1.x release series. If your warehouse runs an earlier version or TLS is not enabled, skip this step.

    The server certificate is issued for the domain provided by VeloDB. Connecting directly to the Azure endpoint name causes TLS certificate validation to fail because the domain names do not match. Configure Azure Private DNS to map the VeloDB domain to the endpoint IP address.

    11.1. On the Azure home page, open Private DNS zones. On the Basics tab, select your resource group and complete the other required fields. In Name, enter the suffix of the VeloDB domain. On the Virtual Network Links tab, add your VNet. Then click Create to create the private DNS zone.

    

    

    

    11.2. After creating the private DNS zone, select Record sets under DNS Management to add a record. In Name, enter the prefix that, together with the private DNS zone name, forms the complete VeloDB domain. Select A as the record type, and enter the endpoint IP address in IP address.

    

After the endpoint is ready, use Connection information and examples to connect an application.