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.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.
View the full entity schema
See every table and column exported to your destination, organized by entity group.
Setting up the integration
Prerequisites
- An Amazon Redshift cluster that’s publicly accessible, in a public subnet with an Internet Gateway route (private clusters can connect via SSH tunneling — contact Stigg support)
- An S3 bucket in the same AWS region, used for staging data before it’s loaded into Redshift
- A Redshift database user with limited permissions for Stigg to connect as
- An IAM role (recommended) or IAM user with permission to access the staging bucket and get cluster credentials
If your security posture requires IP allowlisting, Stigg connects from a static IP:
35.192.85.117/32 (US Cloud) or 104.199.49.149/32 (EU Cloud). For private or self-hosted deployments, contact Stigg support for the egress IP.1
Create a limited Redshift user
Connect to your cluster with a SQL client and create a user for Stigg:Grant it permission to create objects and use temporary tables:
If you’re pre-creating the schema yourself rather than letting Stigg create it on first sync, run
GRANT ALL ON schema <schema> TO <username>; instead, and remove the database-level CREATE grant while keeping TEMPORARY.2
Allow network access
In the Redshift console, find your cluster’s endpoint under Clusters > General information, then open its VPC security group and edit Inbound rules to add a custom TCP rule for the connecting IP:
3
Create the S3 staging bucket
In the S3 console, create a bucket for staging data before it’s loaded into Redshift. AWS recommends disabling ACLs and blocking all public access. Optionally add a lifecycle rule to delete staged objects after 2 days.
4
Create the IAM access policy
Create an IAM policy granting the permissions Stigg needs, replacing
BUCKET_NAME, REGION_NAME, ACCOUNT_ID, CLUSTER_NAME, USERNAME, and DATABASE_NAME with your own values:If the bucket uses a customer-managed KMS key, also add a statement granting
kms:GenerateDataKey and kms:Decrypt on arn:aws:kms:REGION_NAME:ACCOUNT_ID:key/KEY_ID.5
Create the IAM role
In the AWS IAM console, create a role using Custom trust policy. The Stigg connect form shows a trust policy prepopulated with the identifiers for your account — paste it in as-is. Attach the access policy from the previous step, name the role something recognizable (e.g.
transfer-role), and record its ARN.Alternatively, create an IAM user with programmatic access, attach the same access policy, and use its Access Key ID and Secret Access Key when connecting below.
6
Connect Stigg with Redshift
In Stigg, navigate to Integrations > Apps > Amazon Redshift.Enter the following information in the connection form:
Click Test & connect.
7
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 for a description of each group.