Requirements
To follow the steps in this guide, you’ll need:- A Databricks workspace configured for PrivateLink access
- For Azure: A VNet-injected Databricks workspace
- For AWS: A Databricks workspace with AWS PrivateLink enabled
- Permissions in your cloud environment to retrieve PrivateLink configuration details
- Organization Admin permissions in Omni
Setup
Gather connection information
Before contacting Omni support, retrieve your Databricks workspace connection details:
- Your Databricks workspace URL. For example,
adb-1234567890123456.7.azuredatabricks.netordbc-abcd1234-5678.cloud.databricks.com - The cloud provider (AWS or Azure) and region where your Databricks workspace is deployed
- Based on your cloud provider, we’ll also need:
- For AWS - The VPC endpoint service name, which will start with
com.amazonaws.vpce - For Azure - The Databricks workspace resource ID, which should contain
/providers/Microsoft.Databricks/workspaces/
- For AWS - The VPC endpoint service name, which will start with
- Confirmation that your workspace is configured for PrivateLink access:
- For AWS - Verify AWS PrivateLink is enabled for your workspace
- For Azure - Verify your workspace is VNet-injected
Contact Omni support
Contact Omni support with the following information:
- Your Databricks workspace URL
- The connection details for the database, including:
- The cloud provider (AWS or Azure)
- The region of your Databricks workspace
- The VPC endpoint service name (AWS) or Databricks workspace resource ID (Azure)
- Technical contact details, in case of connection difficulties