> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stigg.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Amazon Redshift

## Overview

Stigg's integration with Amazon Redshift allows you to export your product catalog, customer, and subscription data directly to your Redshift cluster for custom reporting and analysis.

<Note>
  Stigg's native data export integrations are included in the Scale plan, and are also available as an optional add-on to the Growth plan. See Stigg's pricing for more details.
</Note>

## Exported entities

When connecting Redshift, you can choose which Stigg entity groups to include in the sync. All groups are selected by default.

See [Exported entities](./overview#exported-entities) for the full list of entity groups and the tables within each.

<Card title="Entity schema" icon="sitemap" href="./schema" horizontal />

## Setting up the integration

### Prerequisites

* An Amazon Redshift cluster
* An S3 bucket in the same AWS region (used for staging data before loading into Redshift)
* An IAM role with permission to read/write the S3 staging bucket and load data into Redshift

<Steps>
  <Step title="Create an IAM role for Stigg">
    In the [AWS IAM console](https://console.aws.amazon.com/iam/), create a role that Stigg can assume. The role must have:

    * **S3 permissions**: `s3:GetObject`, `s3:PutObject`, `s3:DeleteObject`, `s3:ListBucket` on your staging bucket
    * **Redshift permissions**: `redshift:GetClusterCredentials` and the ability to run `COPY` commands

    Grant Stigg's AWS account (`arn:aws:iam::STIGG_ACCOUNT_ID:root`) permission to assume this role. Contact [Stigg support](mailto:support@stigg.io) for the current account ID.
  </Step>

  <Step title="Connect Stigg with Redshift">
    In [Stigg](https://app.stigg.io/), navigate to **Integrations > Apps > Amazon Redshift**.

    Enter the following information in the connection form:

    | Field          | Description                                        |
    | -------------- | -------------------------------------------------- |
    | Host           | The Redshift cluster endpoint                      |
    | Port           | The port Redshift listens on. Defaults to `5439`.  |
    | Database       | The name of the target database                    |
    | Cluster        | The Redshift cluster identifier                    |
    | Schema         | The schema where Stigg will create and sync tables |
    | Username       | The Redshift database user                         |
    | IAM Role ARN   | The ARN of the IAM role created above              |
    | Staging bucket | The S3 bucket name and region used for staging     |

    Click **Test & connect**.
  </Step>

  <Step title="Select entities to export">
    After entering your connection details, expand the **Entities to export** section to choose which entity groups to include in the sync. All groups are selected by default.

    See [Exported entities](./overview#exported-entities) for a description of each group.
  </Step>
</Steps>

## Sync process and schedule

After setup, Stigg performs a full sync of all selected entities. Subsequent syncs are incremental, transferring only changes since the last run.

Stigg syncs data on a configurable schedule — daily at 12:00 AM UTC by default. You can adjust the sync frequency from the integration settings at any time.

## Manual sync

To trigger an immediate sync, open the Redshift integration in [Stigg](https://app.stigg.io/) and click **Sync now**.

## Sync history

The integration page shows a log of all past and in-progress syncs. The dashboard updates automatically as syncs complete.

Each row shows the sync status and timestamps. Expand a row to see rows synced per entity, sync duration, trigger source, and who initiated it.

Use the status and date filters to find a specific sync run.

## Removing the integration

To remove the integration, click on the dotted menu icon and select the **Remove** action.

Confirm the action by clicking on the **Remove** button in the opened modal.