Overview
Stigg’s integration with Amazon Athena allows you to export your product catalog, customer, and subscription data to S3 and query it directly with Athena — no database infrastructure to manage.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 S3 bucket in your AWS account for staging exported data
- An Athena workgroup (defaults to
primaryif you don’t use a dedicated one) - An IAM role (recommended) or IAM user that Stigg can use to write to S3, run Athena queries, and manage Glue Data Catalog tables
1
Create the S3 staging bucket
In the S3 console, create a bucket for Stigg to write data to. AWS recommends disabling ACLs and blocking all public access on the bucket.
2
Create the IAM access policy
Create an IAM policy granting the permissions Stigg needs, replacing
ACCOUNT_ID, WORKGROUP, BUCKET_NAME, and SCHEMA 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. Encryption with SSE-C isn’t currently supported.3
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.If your organization’s policy rules out cross-account role assumption, you can instead 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.
4
Connect Stigg with Athena
In Stigg, navigate to Integrations > Apps > Amazon Athena.Enter the following information in the connection form:
Click Test & connect.
5
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.
Working with Iceberg tables
Athena stores exported tables in Apache Iceberg format. A few operations are useful to know about:432000 seconds (5 days) — the example above shortens it to 3 days. Only adjust this if query performance degrades.