# Load Snowplow data to Amazon Redshift
> Send Snowplow data to Amazon Redshift for analytics and data warehousing with automatic table creation, schema evolution, and optimized batch loading from S3.
> Source: https://docs.snowplow.io/docs/destinations/warehouses-lakes/redshift/
> Documentation index: https://docs.snowplow.io/llms.txt

[Snowplow supported](/docs/destinations/#destinations-catalog "Built and supported by Snowplow") · Warehouse or lake loader · Batch · AWS

> **Info: Cloud availability**
>
> The Redshift integration is available for Snowplow pipelines running on **AWS** only.

The Snowplow Redshift integration allows you to load enriched event data directly into your Redshift cluster (including Redshift serverless) for analytics, data modeling, and more.

## What you will need

Connecting to a destination always involves configuring cloud resources and granting permissions. It's a good idea to make sure you have sufficient priviliges before you begin the setup process.

> **Tip:** The list below is just a heads up. The Snowplow Console will guide you through the exact steps to set up the integration.

Keep in mind that you will need to be able to:

- Provide your Redshift cluster endpoint and connection details

- Allow-list Snowplow IP addresses

- Specify the desired database and schema names

- Create a user and a role with the following permissions:

  - Schema ownership (`CREATE SCHEMA ... AUTHORIZATION`)
  - `SELECT` on system tables (`svv_table_info`, `svv_interleaved_columns`, `stv_interleaved_counts`) — this is required for maintenance jobs

## Getting started

You can add a Redshift destination through the Snowplow Console. (For self-hosted customers, please refer to the [Loader API reference](/docs/api-reference/loaders-storage-targets/snowplow-rdb-loader/) instead.)

### Step 1: Create a connection

1. In Console, navigate to **Settings** > **Connections**
2. Select **Set up connection**
3. Choose **Event loading**, then **Redshift**
4. Follow the steps to provide all the necessary values
5. Click **Complete setup** to create the connection

### Step 2: Create a loader

1. In Console, navigate to **Destinations** > **Warehouses and lakes**. Click **Add destination** and select **Redshift**
2. **Select a pipeline**: choose the pipeline where you want to deploy the loader.
3. **Select your connection**: choose the connection you configured in step 1.
4. Click **Continue** to deploy the loader

You can review active destinations and loaders by navigating to **Destinations** > **Warehouses and lakes**.

## How loading works

The Snowplow data loading process is engineered for large volumes of data. In addition, our loader applications ensure the best representation of Snowplow events. That includes automatically adjusting the tables to account for your custom data, whether it's new event types or new fields.

For more details on the loading flow, see the [RDB Loader](/docs/api-reference/loaders-storage-targets/snowplow-rdb-loader/) reference page, where you will find additional information and diagrams.

## Snowplow data format in Redshift

The event data is split across multiple tables.

The main table (`events`) contains the [atomic fields](/docs/fundamentals/canonical-event/), such as `app_id`, `user_id` and so on:

| app\_id | collector\_tstamp       | ... | event\_id                            | ... | user\_id                             | ... |
| ------- | ----------------------- | --- | ------------------------------------ | --- | ------------------------------------ | --- |
| website | 2025-05-06 12:30:05.123 | ... | c6ef3124-b53a-4b13-a233-0088f79dcbcb | ... | c94f860b-1266-4dad-ae57-3a36a414a521 | ... |

Snowplow data also includes customizable [self-describing events](/docs/fundamentals/events/#self-describing-events) and [entities](/docs/fundamentals/entities/). These use [schemas](/docs/fundamentals/schemas/) to define which fields should be present, and of what type (e.g. string, number).

For each type of self-describing event and entity, there are additional tables that can be joined with the main table:

**com\_acme\_button\_press\_1**

| root\_id                             | root\_tstamp            | button\_name | button\_color | ... |
| ------------------------------------ | ----------------------- | ------------ | ------------- | --- |
| c6ef3124-b53a-4b13-a233-0088f79dcbcb | 2025-05-06 12:30:05.123 | Cancel       | red           | ... |

**com\_acme\_product\_1**

| root\_id                             | root\_tstamp            | name   | price | ... |
| ------------------------------------ | ----------------------- | ------ | ----- | --- |
| c6ef3124-b53a-4b13-a233-0088f79dcbcb | 2025-05-06 12:30:05.123 | Salt   | 2.60  | ... |
| c6ef3124-b53a-4b13-a233-0088f79dcbcb | 2025-05-06 12:30:05.123 | Pepper | 3.10  | ... |

> **Note:** The `_1` suffix represents the major version of the schema (e.g. `1-x-y`).

You can learn more [in the API reference section](/docs/api-reference/loaders-storage-targets/schemas-in-warehouse/).

> **Tip:** Check this [guide on querying](/docs/destinations/warehouses-lakes/querying-data/?warehouse=redshift) Snowplow data.
