Amazon Redshift is one of the fastest cloud data warehouse services. It allows you to handle large analytical workloads with best-in-class performance, speed, and efficiency.

RudderStack supports Amazon Redshift as a source from which you can ingest data and route it to your desired downstream destinations.

Granting permissions

RudderStack requires you to grant certain user permissions on your Amazon Redshift warehouse to successfully access data from it.

Run the queries listed in the following sections on Amazon Redshift Console in the exact order to grant these permissions:

Step 1: Creating a new user in Redshift

1. Create a new user rudder with a password <strong_unique_password>.

Copy
CREATE USER rudder WITH PASSWORD '<strong_unique_password>'

Password considerations for Redshift

The password set in the above command must meet the following conditions:

• It should be 8-64 characters in length.
• It must contain atleast one upper case, one lower case, and one number.
• It can contain any ASCII characters with the ASCII codes 33-126, with the exception of ' (single quotation mark), " (double quotation mark), \, /, and @.

Step 2: Creating the RudderStack schema and granting permissions

1. Create a dedicated schema _rudderstack.

Copy
CREATE SCHEMA "_rudderstack";

2. Grant full access to schema _rudderstack for the user rudder.

Copy
GRANT ALL ON SCHEMA "_rudderstack" TO rudder;

3. Grant full access to the user rudder over all the _rudderstack schema objects.

Copy
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA "_rudderstack" TO rudder;

Step 3: Granting permissions on your schema and table

1. Grant access to the user rudder to look up the objects within your schema <YOUR_SCHEMA>.

Copy
GRANT USAGE ON SCHEMA "<YOUR_SCHEMA>" TO rudder;

2. Grant access to the user rudder to read data from required table <YOUR_TABLE>.

Copy
GRANT SELECT ON TABLE "<YOUR_SCHEMA>"."<YOUR_TABLE>" TO rudder;

Replace <YOUR_SCHEMA> and <YOUR_TABLE> with the exact names of your Redshift schema and table respectively.

Optional commands

• The following command grants access to the user rudder to view and read data from all the tables present in the schema <YOUR_SCHEMA>:

Copy
GRANT SELECT ON ALL TABLES IN SCHEMA "<YOUR_SCHEMA>" TO rudder;

• The following command grants access to the user rudder to read data from all the future tables in the schema <YOUR_SCHEMA>:

Copy
ALTER DEFAULT PRIVILEGES IN SCHEMA "<YOUR_SCHEMA>" GRANT SELECT ON TABLES TO rudder;

Replace <YOUR_SCHEMA> with the exact name of your Redshift schema.

Setting up the Redshift source in RudderStack

To set up Redshift as a source in RudderStack, follow these steps:

Naming the source

1. Log into your RudderStack dashboard.
2. From the left navigation bar, go to Source > New Source > Reverse ETL. Then, select Redshift, as shown:

3. Assign a name to the source.

Configuring the connection credentials

1. Choose the relevant option from Table or Model to use the source to sync data from either a warehouse table or a model.

2. Enter the relevant settings in the Connection Credentials section as listed below:

• Host - Host name of your Redshift service.
• Port - Port number of your Redshift service.
• Database - Database name in your Redshift instance where the data is loaded.
• User - Username which has the required read/write access to the above database.
• Password - Password for the above user.
• SSL Mode: Choose the SSL mode through which RudderStack will connect to your Redshift instance. RudderStack provides two options - disable and require. For more information on these options, refer to the FAQ section below.

3. Click Continue to verify your credentials. RudderStack will then verify and validate your credentials.

4. Once verified, click Continue to proceed.

Schedule settings

1. Specify the Schedule Settings to schedule the data syncs from your Redshift instance.

2. After specifying the schedule type and run settings, click Continue to finish the setup.

Redshift is now successfully configured as a source in your RudderStack dashboard. You can further connect this source to your preferred destination by clicking on Add Destination button, as shown:

Specifying the data to import

While connecting a destination to your Reverse ETL source, you can use the default JSON mapping or the Visual Data Mapping feature.

FAQ

What are the SSL mode options when setting up the Redshift source in RudderStack?

When setting up a Redshift source, RudderStack provides the following two SSL options:

• disable: SSL mode is disabled when you select this option. Use it in cases where security is not an issue and you don't want any encryption overhead.
• require: When you select this option, your data is encrypted and sent to RudderStack. Use it in cases where security is important and you can deal with the resulting encryption overhead.

What do the three validations under Verifying Credentials imply?

When setting up a Reverse ETL source, once you proceed after entering the connection credentials, you will see the following three validations under the Verifying Credentials option:

These options are explained below:

• Verifying Connection: This option indicates that RudderStack is trying to connect to the warehouse with the information specified in the connection credentials.

• Able to List Schema: This option checks if RudderStack is able to fetch all the schema details using the provided credentials.
• Able to Access RudderStack Schema: This option implies that RudderStack is able to access the _RUDDERSTACK schema you have created by successfully running all the commands in the User Permissions section.

What is the difference between the Table and Model options when creating a Reverse ETL source?

When creating a new Reverse ETL source, you are presented with the following two options from which RudderStack will sync the data:

• When you choose Table, RudderStack imports all the data associated with the specified table during the sync.
• When you choose Model, RudderStack imports the data by running the query specified in the connected model, during the sync.