> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/guides/deployment/aws-serverless/connect-s3-and-glue.md).

# 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](/query-engine/guides/deployment/aws-serverless/configure-aws-access.md) 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-engine/guides/catalogs.md).

## Before you start

Make sure you have [configured AWS access](/query-engine/guides/deployment/aws-serverless/configure-aws-access.md): 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-engine/guides/catalogs.md).

## See also

* [Create a cluster](/query-engine/guides/deployment/aws-serverless/create-cluster.md) - provision compute to query this catalog.
* [Catalogs](/query-engine/guides/catalogs.md) - all catalog types and management.
* [Troubleshooting](/query-engine/guides/deployment/aws-serverless/troubleshooting.md) - catalog connection errors.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/guides/deployment/aws-serverless/connect-s3-and-glue.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.