Equals

Open the AWS console and navigate to Redshift via the search in the top nav.

Ensure you are in the correct region in the top right (Ohio, Virginia, etc.).

Open the sidebar and click “Clusters”.

Choose the cluster you want to connect to from the list.

1. Open the AWS console and navigate to Redshift via the search in the top nav.
2. Ensure you are in the correct region in the top right (Ohio, Virginia, etc.).
3. Open the sidebar and click “Clusters”.
4. Choose the cluster you want to connect to from the list.
    

To connect Redshift to Equals you need five pieces of information: Endpoint, Port, Database name, Username, and Password. The Schema field is optional.

Find your cluster in AWS, following the instructions above.

Once on the cluster details page you can find Endpoint under “General information”.

Navigate to “Properties” in the tab bar below “General information”.

Under “Database configurations” you can find the Database name, the Port (likely 5439), and the Username (called “Admin user name”).

Finally you need the Password. This was set when your cluster was created. If you don’t know the password ask the team member who set up your database.

1. Find your cluster in AWS, following the instructions above.
2. Once on the cluster details page you can find Endpoint under “General information”.
3. Navigate to “Properties” in the tab bar below “General information”.
4. Under “Database configurations” you can find the Database name, the Port (likely 5439), and the Username (called “Admin user name”).
5. Finally you need the Password. This was set when your cluster was created. If you don’t know the password ask the team member who set up your database.

There are two steps to allowing access from our IP: enabling public access and creating an inbound security group rule.

Under “Network and security settings”, ensure “Publicly accessible” is set to “Enabled”. If it is already enabled, you can skip to the next section.

Click “Edit” in the header of “Network and security settings”.

At the bottom of the page check “Turn on Publicly accessible” and click “Save changes”. Note: it is not necessary to assign an elastic IP address.

1. Find your cluster in AWS, following the instructions above.
2. Navigate to “Properties” in the tab bar below “General information”.
3. Under “Network and security settings”, ensure “Publicly accessible” is set to “Enabled”. If it is already enabled, you can skip to the next section.
4. Click “Edit” in the header of “Network and security settings”.
5. At the bottom of the page check “Turn on Publicly accessible” and click “Save changes”. Note: it is not necessary to assign an elastic IP address.

Under “Network and security settings”, navigate to the “VPC security group”.

On the “Security group” page, click “Inbound rules” in the tab bar.

Add a rule, and set “Type” to “Redshift”, “Source” to “Custom”, and paste <code>54.68.61.53/32</code> in the “Source” text field.

Click “Save rules”. Equals should now be able to access your cluster.

1. Find your cluster in AWS, following the instructions above.
2. Navigate to “Properties” in the tab bar below “General information”.
3. Under “Network and security settings”, navigate to the “VPC security group”.
4. On the “Security group” page, click “Inbound rules” in the tab bar.
5. Click “Edit inbound rules”
6. Add a rule, and set “Type” to “Redshift”, “Source” to “Custom”, and paste <code>54.68.61.53/32</code> in the “Source” text field.
7. Click “Save rules”. Equals should now be able to access your cluster.

Finding your cluster in AWS

Finding connection details

Allowing access from our IP

Enabling public access

Creating an inbound security group rule