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

# S3-Compatible Storage

## Overview

Stigg's integration with S3-compatible storage allows you to export your product catalog, customer, and subscription data to any object storage provider that supports the S3 protocol (such as MinIO, Backblaze B2, Wasabi, or Cloudflare R2) as structured files.

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

<Card title="View the full entity schema" icon="sitemap" href="./schema">
  See every table and column exported to your destination, organized by entity group.
</Card>

## Setting up the integration

### Prerequisites

An S3-compatible object storage bucket, and HMAC credentials with write access to it.

<Steps>
  <Step title="Create HMAC credentials">
    Consult your object storage provider's documentation to generate an **HMAC Access ID** and **Secret**, with write access to your target bucket.
  </Step>

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

    Enter the following information in the connection form:

    | Field          | Description                                                  |
    | -------------- | ------------------------------------------------------------ |
    | Bucket host    | The endpoint hostname of your object storage provider        |
    | Bucket name    | The name of the target bucket                                |
    | Folder name    | The folder path within the bucket where data will be written |
    | HMAC access ID | The HMAC Access ID generated above                           |
    | HMAC secret    | The HMAC Secret generated above                              |

    Click **Test & connect**.

    <Note>
      The bucket must be reachable from Stigg's sync service egress IP. Data is written as Parquet by default — CSV, JSON, and JSONL are also supported.
    </Note>
  </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>


## Related topics

- [Exported entities](/documentation/importing-and-exporting-data/export/overview#exported-entities.md)
- [Sync process, schedule, manual sync, and sync history](/documentation/importing-and-exporting-data/export/overview#sync-process.md)