Enabling an AWS PrivateLink between ThoughtSpot Cloud and your Databricks data warehouse
Learn how to deploy an AWS PrivateLink between your Databricks data warehouse and the ThoughtSpot Cloud tenant.
Your data’s security is important. ThoughtSpot encrypts all your data by default. For an additional layer of security and network reliability, you can use an AWS PrivateLink. This option is currently available for your Amazon Redshift, Databricks, Denodo, Dremio, Oracle, SAP HANA, Snowflake, Starburst, or Teradata data warehouse connections.
This article details how to enable a PrivateLink for Databricks; to enable it for other data warehouses, refer to:
|You can only enable one PrivateLink for each cluster.|
To deploy an AWS PrivateLink, you must work with ThoughtSpot Support and follow the procedure in this article.
You must have a Databricks Enterprise account.
The ThoughtSpot cluster must be in the same AWS region as your Databricks account.
You must have Databricks Account Admin credentials.
The Databricks Account admin is different from the Workspace Admin. The Account admin is able to log into https://accounts.cloud.databricks.com/.
To deploy an AWS PrivateLink between your Databricks data warehouse and the ThoughtSpot Cloud tenant, follow these steps.
After completing the prerequisites, you must configure the register the VPC Endpoint. Follow these steps:
Complete Step 3: Register your VPC endpoint IDs with the Account API in the Databricks AWS PrivateLink documentation. You need the VPC Endpoint ID from ThoughtSpot Support to complete this step.
After you complete steps 1-4 in this document, contact ThoughtSpot Support. They must finish the PrivateLink configuration.
Make sure you send ThoughtSpot Support your Databricks Workspace URL. This URL is in the format
Create a Databricks connection.