Overview
Stigg’s integration with Amazon S3 allows you to export your product catalog, customer, and subscription data to an S3 bucket as structured files — useful for data lake pipelines, custom ETL workflows, or archival.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.
Exported entities
When connecting S3, you can choose which Stigg entity groups to include in the sync. All groups are selected by default. See Exported entities for the full list of entity groups and the tables within each.Entity schema
Setting up the integration
Prerequisites
- An S3 bucket in your AWS account
- An IAM role that Stigg can assume, with read/write access to the bucket
Create an IAM role for Stigg
In the AWS IAM console, create a role with the following S3 permissions on your bucket:Grant Stigg’s AWS account (
s3:PutObjects3:DeleteObject(only needed to validate the connection during setup — can be removed afterward)
If your bucket uses KMS encryption, also grant
kms:GenerateDataKey and kms:Decrypt on the KMS key.arn:aws:iam::STIGG_ACCOUNT_ID:root) permission to assume this role. Contact Stigg support for the current account ID.Connect Stigg with S3
In Stigg, navigate to Integrations > Apps > Amazon S3.Enter the following information in the connection form:
Click Test & connect.
| Field | Description |
|---|---|
| Bucket name | The name of your S3 bucket |
| Bucket region | The AWS region where the bucket is located, e.g. us-east-1 |
| IAM Role ARN | The ARN of the IAM role created above |
| Folder prefix (optional) | A path prefix within the bucket where data will be written |
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.