Overview
Stigg’s integration with Amazon Redshift Serverless allows you to export your product catalog, customer, and subscription data to a Redshift Serverless workgroup — without managing cluster capacity.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
- A Redshift Serverless workgroup and namespace
- An S3 bucket in the same AWS region, used for staging data before it’s loaded into Redshift Serverless
- An IAM role (recommended) or IAM user with permission to access the staging bucket and call
redshift-serverless:GetCredentials
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 the database user
Connect to your workgroup with a SQL client and create a user derived from the IAM identity Stigg will connect with. For the recommended IAM role method, the username takes the form
IAMR:<role-name>:Using an IAM user with HMAC access keys instead? Create the user as
IAM:<user-name> and grant it the same way.If Redshift Serverless already auto-created the user,
CREATE USER will error — skip it and just run the GRANT. If you’re pre-creating the schema yourself rather than letting Stigg create it on first sync, also run GRANT ALL ON schema <schema> TO "IAMR:<role-name>";.2
Allow network access
In the Redshift Serverless console, find your workgroup’s endpoint under Properties > 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 Serverless. 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
REGION_NAME, ACCOUNT_ID, WORKGROUP_NAME_OR_ID, and BUCKET_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 (based on Google federated identity) — 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 Serverless
In Stigg, navigate to Integrations > Apps > Amazon Redshift Serverless.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.