How-to Guide: Locating The Required Details to Connect AWS Redshift

This guide will help you set up integrations with your Amazon Redshift data warehouse, including locating important details and allowing access from Ledge's static IP address (34.231.208.110 )

🔐 AWS Redshift administrator privileges required

Prerequisites

Before you begin, ensure you have:

• AWS Management Console access

• Redshift cluster already created and running

• Appropriate IAM permissions for Redshift management

If you do not have those details, your database administrator or engineering contacts should have them, and can help in setting up permissions.

In the guide below we will collect the three components required to connect Redshift with Ledge:

1. Host URL/Endpoint

2. Port

3. Databases, tables and schemas names

Step 1: Locate Your Redshift Cluster Endpoint and Port

Option 1: Redshift Serverless

1. Go to your AWS Reshift Console

2. On the left menu, click Workgroup configuration

3. In the list, click on the name of your workgroup

4. On the workgroup details page, look for:

   • Endpoint, also known as Host (example: abc123.redshift-serverless.us-east-1.amazonaws.com)

   • Port (usually 5439)

   • Default database name

   • Namespace (linked to your data and user access)

_{Option 2: Redshift Classic (Provisioned Cluster)}

1. Go to the AWS Reshift Console

2. If you're not using Serverless, you'll see a section for Clusters

3. Click on the name of your cluster

4. Look for:

   • Endpoint, also known as Host (example: mycluster.abc123xyz789.us-east-1.redshift.amazonaws.com)

   • Port (usually 5439)

   • Database name (listed under "Cluster Database Properties")

   • Username (if you have access)

For exact information follow AWS documentation

Step 2: Configure Security Group for IP Access

1. In the AWS Management Console, navigate to your Redshift cluster

2. Under the Properties tab, find the VPC security groups section

3. Click on the security group associated with your cluster

4. In the Security Groups page, go to the Inbound rules tab

5. Click Edit inbound rules

6. Click Add rule and configure:

Setting	Value
Type	Custom TCP
Protocol	TCP
Port range	5439
Source	34.231.208.110/32
Description	Allow Ledge IP access

1. Click Save rules

Troubleshooting: Verify Cluster Accessibility

1. Check Public Accessibility

   1. In your cluster properties, verify Publicly accessible is set to Yes

   2. If not, you may need to modify the cluster settings

2. If you encounter issues not covered above:

   1. Check the AWS Redshift Documentation

   2. Review your AWS CloudTrail logs for authentication errors

   3. Contact your Ledge Customer Support Manager for integration-specific support

   4. Reach out to your IT support team for AWS infrastructure issues

Step 3: Connect to Ledge

You can now complete the setup on Ledge. In the Sources page, fill out the details as follows:

• Host & port, based on the information collected in step 2

• Database, schema, and table names you would like to connect