> 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/prerequisites.md).

# Prerequisites

What you need before deploying a Serverless e6data workspace on AWS.

Before you begin, make sure you have:

* Access to the **AWS Console** with permission to create IAM roles and policies.
* Permission to grant access to the **S3 buckets** that hold the data you want to query.
* Access to **AWS Glue** (or your chosen catalog service), if you plan to connect a Glue catalog.
* An e6data account with permission to create a workspace.

Familiarity with the **AWS CLI** is optional - every step can be done in the AWS Console, but the CLI is offered as an alternative where it's faster.

## What happens next

Once these are in place, the deployment proceeds as: [create your workspace](/query-engine/guides/workspaces/create-and-manage-workspaces.md) → [configure AWS access](/query-engine/guides/deployment/aws-serverless/configure-aws-access.md) → [connect S3 and Glue](/query-engine/guides/deployment/aws-serverless/connect-s3-and-glue.md) → [create a cluster](/query-engine/guides/deployment/aws-serverless/create-cluster.md) → [run your first query](/query-engine/guides/deployment/aws-serverless/run-first-query.md).

## See also

* [Architecture](/query-engine/guides/deployment/aws-serverless/architecture.md) - what e6data accesses and why.
* [AWS Serverless](/query-engine/guides/deployment/aws-serverless.md) - the full deployment guide.


---

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