Skip to main content

​
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.

View the full entity schema

See every table and column exported to your destination, organized by entity group.

​
Setting up the integration

​
Prerequisites

  • An AWS account with permission to create S3 buckets and IAM roles/policies.
  • Access to the Stigg dashboard with permission to configure integrations.
Use a dedicated bucket for this integration to avoid resource contention and to keep its access policies tightly scoped.
1

Create the S3 bucket

In the AWS S3 console, create a bucket with:
  • Object Ownership: ACLs disabled
  • Block Public Access settings: Block all public access
Note the bucket name and AWS region — you’ll need them later.
2

Create the IAM policy and role

In the AWS IAM console, go to Policies → Create policy, click the JSON tab, and paste the following, replacing BUCKET_NAME:
Optionally add s3:DeleteObject to the Action list to allow automatic cleanup of the test file written during connection setup.
If the bucket uses KMS encryption, also add a statement granting kms:GenerateDataKey and kms:Decrypt on your CMK, replacing REGION_NAME, ACCOUNT_ID, and KEY_ID:
Then go to Roles → Create role, select Custom trust policy, and paste the trust policy shown in the Stigg connect form — it will look like this, with the organization and service-account identifiers pre-filled for your account:
Click Next, attach the permissions policy created above, click Next again, give the role a name (e.g. transfer-role), and click Create role. Open the created role and note its ARN — you’ll need it in the next step.
3

Connect Stigg with S3

In Stigg, navigate to Integrations > Apps > Amazon S3.Enter the following information in the connection form:Click Test & connect.
If your organization’s policy rules out role-based access, you can instead authenticate with an Access key ID and Secret access key for an IAM user with the same s3:PutObject permissions on the bucket.
4

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.

Related topics

Exported entitiesSync process, schedule, manual sync, and sync history