Redshift-managed VPC endpoints create a secure, private connection between services running in AWS. This document describes the steps to set this up between Amazon Redshift and Atlan, when you use our Single Tenant SaaS deployment.
- Your Redshift cluster must be an RA3 node type.
- Your Redshift cluster must have cluster relocation turned on.
- Your Redshift cluster must be available through port 5439.
- You must have spare capacity in your VPC endpoint quota.
(For all details, see Working with Redshift-managed VPC endpoints in Amazon Redshift.)
Request Atlan's details
Before granting access to your Redshift cluster to Atlan, you will need the following:
- Atlan's AWS account ID
- Atlan's VPC ID for the connection
Grant access to Atlan
Once you've received the details above, to grant Atlan access to your Redshift cluster:
- Sign in to the AWS Management Console and open the Amazon Redshift console.
- From the navigation menu, click Clusters.
- From the table, click the name of the cluster to which you want to grant access.
- Change to the Properties tab of the cluster.
- Under the Granted accounts section, click Grant access.
- In the Grantee information form:
- For AWS account ID, enter the Atlan AWS account ID.
- For VPC, choose Grant access to specific VPCs and enter the Atlan VPC ID.
- At the bottom right, click the Grant access button.
Notify Atlan support team
Once you've completed the steps above, contact the Atlan support team again and provide the following details for your Redshift cluster:
- AWS account ID
- Redshift cluster identifier — the unique identifier of your cluster
Atlan will create a Redshift-managed VPC endpoint, and then reply to you with a hostname.
When you use this hostname in the configuration for crawling, Atlan will connect to Redshift over the private network.