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

# Connect S3 and Glue

> Create an AWS Glue catalog over your S3 data in a Serverless e6data workspace, using the cross-account IAM role.

A **catalog** connects e6data to a metastore that describes your databases, tables, and columns. On AWS the most common path is **AWS Glue** over data in **S3**. Your S3 data is reached through the [cross-account IAM role](/platform/deploy/aws-serverless/configure-aws-access) you configured earlier; the catalog supplies the table metadata.

This page covers the AWS Glue path for a Serverless deployment. For other catalog types and full catalog management, see [Catalogs](/query/catalogs/register-and-manage-catalogs).

## Before you start

Make sure you have [configured AWS access](/platform/deploy/aws-serverless/configure-aws-access): the cross-account IAM role exists, has S3 and Glue read permissions, and its ARN is registered in **Settings → Storage Credentials**.

## Connect an AWS Glue catalog

1. In the Compute Plane, open the **Catalogs** section and select **Create Catalog**.
2. Enter a **Catalog Name** - unique within the workspace; lowercase letters, numbers, and hyphens recommended (for example, `aws-glue-catalog`).
3. Set **Catalog Type** to **AWS Glue**.
4. (Optional) Enable **Governance** to apply fine-grained access control through Ranger, OPA, or Lake Formation. Use this if your organization enforces centralized data governance.
5. Configure the connection:
   * **AWS Region** - the region where your Glue catalog lives.
   * **Glue Database Filter** - (optional) restrict to specific databases.
6. **(Recommended) Use shared Storage Credential** — turn this on and select the Storage Credential you created earlier from the dropdown. This is the preferred method and reuses one keyless identity (the cross-account IAM role) across catalogs.
7. Select **Test Connection** to verify connectivity and permissions.
8. Choose the **schemas to include** by selecting the databases you need.
9. Select **Create Catalog**. The catalog is now available for querying in your workspace.

## Other catalog types

e6data also supports Hive Metastore, Databricks Unity, Apache Polaris, Iceberg REST, and Amazon S3 Tables. For Serverless deployments, each uses the same **Cross-Account Access** pattern (Target AWS Account ID + IAM Role ARN). See the per-catalog guides under [Catalogs](/query/catalogs/register-and-manage-catalogs).

## See also

* [Create a cluster](/platform/deploy/aws-serverless/create-cluster) - provision compute to query this catalog.
* [Catalogs](/query/catalogs/register-and-manage-catalogs) - all catalog types and management.
* [Troubleshooting](/platform/deploy/aws-serverless/troubleshooting) - catalog connection errors.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.