# Load Snowplow data to Apache Iceberg
> Send Snowplow data to Apache Iceberg data lakes for analytics and data processing with open table format, schema evolution, and cross-engine compatibility.
> Source: https://docs.snowplow.io/docs/destinations/warehouses-lakes/iceberg/
> Documentation index: https://docs.snowplow.io/llms.txt

[Snowplow supported](/docs/destinations/#destinations-catalog "Built and supported by Snowplow") · Warehouse or lake loader · Batch · AWS, GCP

> **Info: Cloud availability**
>
> The Iceberg integration is available for Snowplow pipelines running on **AWS** and **GCP** only.

Apache Iceberg is an open table format for data lake architectures. The Snowplow Iceberg integration allows you to load enriched event data (as well as [failed events](/docs/fundamentals/failed-events/)) into Iceberg tables in your data lake for analytics, data modeling, and more.

Iceberg data can be consumed using various tools and products, for example:

- Amazon Athena
- Amazon Redshift Spectrum
- Apache Spark or Amazon EMR
- Snowflake
- Databricks
- ClickHouse

We currently support the following catalogs:

| Catalog | AWS | GCP |
| ------- | --- | --- |
| Glue    | ✅   | ❌   |
| REST¹   | ✅   | ✅   |

_¹The REST catalog has only been tested with Snowflake Open Catalog (Apache Polaris), Snowflake Horizon Catalog, and Databricks Unity Catalog._

## What you will need

Connecting to a destination always involves configuring cloud resources and granting permissions. It's a good idea to make sure you have sufficient priviliges before you begin the setup process.

> **Tip:** The list below is just a heads up. The Snowplow Console will guide you through the exact steps to set up the integration.

Keep in mind that you will need to be able to:

**REST (Snowflake):**

- Specify your Snowflake Open Catalog account ID and region, as well as namespace
- Create a service connection to the catalog and provide the OAuth client ID and client secret

**REST (Databricks):**

- Create an external location, a catalog, and a schema, and provide the catalog and schema names
- Create a service principal and provide the OAuth client ID and client secret

**AWS Glue:**

- Specify your AWS account ID

- Provide an S3 bucket and an AWS Glue database

- Create an IAM role with the following permissions:

  - For the S3 bucket:

    - `s3:ListBucket`
    - `s3:GetObject`
    - `s3:PutObject`
    - `s3:DeleteObject`

  - For the Glue database:

    - `glue:CreateTable`
    - `glue:GetTable`
    - `glue:UpdateTable`

- Schedule a regular job to optimize the lake

***

## Getting started

You can add an Iceberg destination through the Snowplow Console. (For self-hosted customers, please refer to the [Loader API reference](/docs/api-reference/loaders-storage-targets/lake-loader/) instead.)

### Step 1: Create a connection

1. In Console, navigate to **Settings** > **Connections**
2. Select **Set up connection**
3. Choose **Event loading**, then **Iceberg**
4. Follow the steps to provide all the necessary values
5. Click **Complete setup** to create the connection

### Step 2: Create a loader

1. In Console, navigate to **Destinations** > **Warehouses and lakes**. Click **Add destination** and select **Iceberg**
2. **Select a pipeline**: choose the pipeline where you want to deploy the loader.
3. **Select your connection**: choose the connection you configured in step 1.
4. **Select the type of events**: enriched events or failed events
5. Click **Continue** to deploy the loader

You can review active destinations and loaders by navigating to **Destinations** > **Warehouses and lakes**.

For AWS Glue, we recommend scheduling regular [lake maintenance jobs](/docs/api-reference/loaders-storage-targets/lake-loader/maintenance/?lake-format=iceberg) to ensure the best long-term performance.

## How loading works

The Snowplow data loading process is engineered for large volumes of data. In addition, our loader applications ensure the best representation of Snowplow events. That includes automatically adjusting the tables to account for your custom data, whether it's new event types or new fields.

For more details on the loading flow, see the [Lake Loader](/docs/api-reference/loaders-storage-targets/lake-loader/) reference page, where you will find additional information and diagrams.

## Snowplow data format in Iceberg

All events are loaded into a single table (`events`).

There are dedicated columns for [atomic fields](/docs/fundamentals/canonical-event/), such as `app_id`, `user_id` and so on:

| app\_id | collector\_tstamp       | ... | event\_id                            | ... | user\_id                             | ... |
| ------- | ----------------------- | --- | ------------------------------------ | --- | ------------------------------------ | --- |
| website | 2025-05-06 12:30:05.123 | ... | c6ef3124-b53a-4b13-a233-0088f79dcbcb | ... | c94f860b-1266-4dad-ae57-3a36a414a521 | ... |

Snowplow data also includes customizable [self-describing events](/docs/fundamentals/events/#self-describing-events) and [entities](/docs/fundamentals/entities/). These use [schemas](/docs/fundamentals/schemas/) to define which fields should be present, and of what type (e.g. string, number).

For self-describing events and entities, there are additional columns, like so:

| app\_id | ... | unstruct\_event\_com\_acme\_button\_press\_1            | contexts\_com\_acme\_product\_1                                  |
| ------- | --- | ------------------------------------------------------- | ---------------------------------------------------------------- |
| website | ... | data for your custom `button_press` event (as `STRUCT`) | data for your custom `product` entities (as `ARRAY` of `STRUCT`) |

Note:

- "unstruct\[ured] event" and "context" are the legacy terms for self-describing events and entities, respectively
- the `_1` suffix represents the major version of the schema (e.g. `1-x-y`)

You can learn more [in the API reference section](/docs/api-reference/loaders-storage-targets/schemas-in-warehouse/).

> **Tip:** Check this [guide on querying](/docs/destinations/warehouses-lakes/querying-data/?warehouse=databricks) Snowplow data. (You will need a query engine such as Spark SQL or Snowflake to query Iceberg tables.)
