Redshift Source

Overview

The Amazon Redshift Source connects your Redshift data warehouse to Sourcesible, enabling you to sync tables into the platform for use in Datasets, Traits, Audiences, and Pipelines. Sourcesible authenticates using a dedicated database user with read access to your target schemas.

Redshift Credential & Permission Setup

Sourcesible connects to Redshift using a database username and password. Create a dedicated read-only user to limit access scope.

Create a Dedicated Database User

• Connect to your Redshift cluster as a superuser using psql or a SQL client.
• Create a new user for Sourcesible:

GRANT USAGE ON SCHEMA your_schema TO sourcesible_user;
GRANT SELECT ON ALL TABLES IN SCHEMA your_schema TO sourcesible_user;

• Grant read access to the schemas you want to sync:

GRANT USAGE ON SCHEMA your_schema_name TO sourcesible_user;

• To automatically include future tables in the same schema:

ALTER DEFAULT PRIVILEGES IN SCHEMA your_schema
GRANT SELECT ON TABLES TO sourcesible_user;

Configure Network Access

Sourcesible must be able to reach your Redshift cluster over the network.

1. In the AWS Console, go to Amazon Redshift → Clusters and select your cluster.
2. Under Properties, locate and open the linked VPC security group.
3. Add an inbound rule allowing TCP on port 5439 from Sourcesible's IP addresses.

Connection Configuration

Add the Redshift Source

1. In Sourcesible, click Sources in the left navigation.
2. Click Add Source.
3. Search for and select Amazon Redshift.
4. Enter a name for this source in the Source Name field.

Enter Connection Credentials

1. In the Host field, enter your Redshift cluster endpoint (e.g., your-cluster.abc123.us-east-1.redshift.amazonaws.com).
2. In the Port field, enter 5439 (default Redshift port).
3. In the Database field, enter the name of the database you want to connect to.
4. In the Username field, enter the dedicated Sourcesible user you created.
5. In the Password field, enter the corresponding password.

6. Click Save.

---

Test Your Connection

Click Test Connection to verify your setup. Sourcesible checks the following:

• Network connectivity to the cluster endpoint on the specified port
• Successful authentication with the provided username and password
• Read access to the specified database

Next Steps

After your Redshift Source is connected, create a Dataset to select the tables you want to use.

• Create a Dataset — Choose schemas and tables from your Redshift source to expose within Sourcesible
• Define Traits — Compute user-level attributes from your Redshift tables
• Build Audiences — Segment users using Redshift data
• Set Up Pipelines — Route Redshift data to your Destinations

Tips and Troubleshooting

Connection Times Out

Symptom: The connection test fails with a timeout or "could not connect to server" error.

Cause: Sourcesible's IP addresses are blocked by the cluster's VPC security group or network ACL.

Fix: Add Sourcesible's outbound IPs to the inbound security group rules on TCP port 5439. See Configure Network Access for details.

Authentication Failed

Symptom: The connection test returns "authentication failed for user."

Cause: The username or password is incorrect, or the user does not exist in the target database.

Fix: Verify the credentials by connecting directly to the cluster:

psql -h your-cluster.abc123.us-east-1.redshift.amazonaws.com \
     -U sourcesible_user \
     -d your_database \
     -p 5439

If the connection succeeds locally but fails in Sourcesible, double-check the value entered in the Password field.

---

Permission Denied on Tables

Symptom: The connection succeeds, but no tables appear when creating a Dataset, or queries return a "permission denied" error.

Cause: The Sourcesible user lacks USAGE on the schema or SELECT on one or more tables.

Fix: Re-run the permission grants as a superuser:

GRANT USAGE ON SCHEMA your_schema TO sourcesible_user;
GRANT SELECT ON ALL TABLES IN SCHEMA your_schema TO sourcesible_user;

SSL Connection Required

Symptom: The connection fails with "SSL connection is required" or "SSL is not supported."

Cause: Your Redshift cluster parameter group enforces SSL, and the connection is not configured accordingly.

Fix: Review your cluster's require_ssl parameter group setting. Contact Sourcesible support to enable SSL on the connector if needed.