> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stigg.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Amazon Athena

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

<Note>
  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.
</Note>

## Exported entities

When connecting Athena, you can choose which Stigg entity groups to include in the sync. All groups are selected by default.

See [Exported entities](./overview#exported-entities) for the full list of entity groups and the tables within each.

<Card title="Entity schema" icon="sitemap" href="./schema" horizontal />

## Setting up the integration

### Prerequisites

* An S3 bucket in your AWS account where Stigg will write data
* An Athena workgroup (the `primary` workgroup works if you don't have a specific one)
* An IAM role with S3 read/write access to your bucket and Athena query permissions

<Steps>
  <Step title="Create an IAM role for Stigg">
    In the [AWS IAM console](https://console.aws.amazon.com/iam/), create a role that Stigg can assume. The role must have:

    * **S3 permissions**: `s3:GetObject`, `s3:PutObject`, `s3:DeleteObject`, `s3:ListBucket`, `s3:GetBucketLocation` on your bucket
    * **Athena permissions**: `athena:StartQueryExecution`, `athena:StopQueryExecution`, `athena:GetQueryExecution`, `athena:GetQueryResults`, `athena:StartSession`, `athena:GetDatabase`, `athena:GetDataCatalog`, `athena:GetWorkGroup`, `athena:GetTableMetadata`
    * **Glue permissions**: `glue:GetDatabases`, `glue:GetDatabase`, `glue:CreateDatabase`, `glue:GetTables`, `glue:GetTable`, `glue:CreateTable`, `glue:UpdateTable`, `glue:DeleteTable`, `glue:GetPartitions`

    Grant Stigg's AWS account (`arn:aws:iam::STIGG_ACCOUNT_ID:root`) permission to assume this role. Contact [Stigg support](mailto:support@stigg.io) for the current account ID.
  </Step>

  <Step title="Connect Stigg with Athena">
    In [Stigg](https://app.stigg.io/), navigate to **Integrations > Apps > Amazon Athena**.

    Enter the following information in the connection form:

    | Field         | Description                                              |
    | ------------- | -------------------------------------------------------- |
    | Database      | The Glue/Athena database where tables will be registered |
    | Schema        | The schema name for your Stigg data                      |
    | Workgroup     | The Athena workgroup to use. Defaults to `primary`.      |
    | Bucket name   | The S3 bucket where data will be written                 |
    | Bucket region | The AWS region of your S3 bucket                         |
    | IAM Role ARN  | The ARN of the IAM role created above                    |

    Click **Test & connect**.
  </Step>

  <Step title="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](./overview#exported-entities) for a description of each group.
  </Step>
</Steps>

## Sync process and schedule

After setup, Stigg performs a full sync of all selected entities. Subsequent syncs are incremental, transferring only changes since the last run.

Stigg syncs data on a configurable schedule — daily at 12:00 AM UTC by default. You can adjust the sync frequency from the integration settings at any time.

## Manual sync

To trigger an immediate sync, open the Athena integration in [Stigg](https://app.stigg.io/) and click **Sync now**.

## Sync history

The integration page shows a log of all past and in-progress syncs. The dashboard updates automatically as syncs complete.

Each row shows the sync status and timestamps. Expand a row to see rows synced per entity, sync duration, trigger source, and who initiated it.

Use the status and date filters to find a specific sync run.

## Removing the integration

To remove the integration, click on the dotted menu icon and select the **Remove** action.

Confirm the action by clicking on the **Remove** button in the opened modal.