Enabling a Redshift-managed PrivateLink between ThoughtSpot Cloud and your Redshift data warehouse

Learn how to deploy a Redshift-managed PrivateLink, also known as Redshift-managed VPC endpoint, between your Redshift data warehouse and the ThoughtSpot Cloud tenant.

To deploy a Redshift-managed PrivateLink, you must work with ThoughtSpot Support and follow the procedure in this article.

Prerequisites

Enable a Redshift-managed PrivateLink for Redshift

To deploy a Redshift-managed PrivateLink between your Redshift data warehouse and the ThoughtSpot Cloud tenant, follow these steps.

When configuring Redshift-managed PrivateLink, you must create a Support ticket requesting ThoughtSpot’s AWS account ID and AWS VPC ID, configure your AWS account to allow ThoughtSpot access to your cluster, receive the DNS endpoint for Connections from ThoughtSpot, and connect to your cluster using the Endpoint DNS name.

Step 1: Create a Support ticket

Create a Support ticket requesting ThoughtSpot’s AWS account ID and the AWS VPC ID for your cluster at ThoughtSpot Support. Note that you need a Support Portal login to file a ticket. If you do not have one, contact your ThoughtSpot liaison.

Step 2: Configure your AWS account

To configure your AWS account to allow ThoughtSpot access, follow these steps: Granting access to a cluster.

Note that you only need to perform the steps to grant access to a cluster, not the ones described in "Creating a Redshift-managed VPC endpoint".

Once you have granted access to the ThoughtSpot AWS account, provide your AWS account ID and Redshift cluster identifier to ThoughtSpot Support. You can use the same Support ticket filed in step 1.

Step 3: Receive the DNS endpoint

Using the same Support ticket, request the DNS endpoint for your cluster.


Was this page helpful?