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, enter the Atlan VPC ID.
- Click the Grant access button.
Notify Atlan support team
When you use this hostname in the configuration for crawling, Atlan will connect to Redshift over the private network.