## Set up a private network link to Amazon Redshift

URL: https://docs.atlan.com/apps/connectors/data-warehouses/amazon-redshift/how-tos/set-up-a-private-network-link-to-amazon-redshift

> :::warning Who can do this? You will need your Amazon Redshift administrator or AWS administrator involved - you may not have access to run these tasks.

:::warning Who can do this?
 You will need your Amazon Redshift administrator or AWS administrator involved - you may not have access to run these tasks.

:::

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.

## Prerequisites

- Your Redshift cluster must be an RA3 node type.
- Your Redshift cluster must have [cluster relocation turned on](https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-recovery.html).
- Your Redshift cluster must be available through port 5439.
- You must have spare capacity in your [VPC endpoint quota](https://docs.aws.amazon.com/redshift/latest/mgmt/amazon-redshift-limits.html).

(For all details, see [Working with Redshift-managed VPC endpoints in Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-cross-vpc.html).)

## 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

[Request these from Atlan support](https://docs.atlan.com/support/submit-request).

## Grant access to Atlan

Once you've received the details above, to [grant Atlan access to your Redshift cluster](https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-cross-vpc.html#managing-cluster-cross-vpc-console-grantor):

1. Sign in to the AWS Management Console and open the [Amazon Redshift console](https://console.aws.amazon.com/redshift/).
2. From the navigation menu, click **Clusters**.
3. From the table, click the name of the cluster to which you want to grant access.
4. Change to the **Properties** tab of the cluster.
5. Under the _Granted accounts_ section, click **Grant access**.
6. In the _Grantee information_ form:
 1. For _AWS account ID_, enter the Atlan AWS account ID.
 2. For _VPC_, choose **Grant access to specific VPCs** and enter the Atlan VPC ID.
7. 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](https://docs.atlan.com/support/submit-request) 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](https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-cross-vpc.html#managing-cluster-cross-vpc-console-grantee), and then reply to you with a hostname.

When you use this hostname in the configuration for [crawling](https://docs.atlan.com/llms/connectors/amazon-redshift/crawl-amazon-redshift/llms.txt), Atlan will connect to Redshift over the private network.

---