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

# AWS Serverless

Deploy e6data as a Serverless workspace on AWS - the end-to-end path from creating a workspace to running your first query.

A **Serverless** workspace runs e6data's compute in e6data's own cloud account, fully managed for you. Your data never leaves your AWS account - e6data reads it in place through a cross-account IAM role you grant. This is the fastest way to get started on AWS: there is no Kubernetes, no infrastructure to run, and no networking to stand up.

{% hint style="info" %}
**Who this is for:** any e6data user with AWS Console access - no infrastructure or Kubernetes required. **Before you start:** permission to create a cross-account IAM role, plus access to the S3 buckets and Glue/Hive catalog you want to query (see [Prerequisites](/query-engine/guides/deployment/aws-serverless/prerequisites.md)).
{% endhint %}

This guide walks the full deployment in order.

## Before you start

Review the [Prerequisites](/query-engine/guides/deployment/aws-serverless/prerequisites.md) - AWS Console access with permission to create IAM roles, and access to the S3 buckets and catalog service you want to query.

## Deployment steps

{% stepper %}
{% step %}

### Review the architecture

See [Architecture](/query-engine/guides/deployment/aws-serverless/architecture.md) - how Serverless on AWS fits together and where your data stays.
{% endstep %}

{% step %}

### Check prerequisites

See [Prerequisites](/query-engine/guides/deployment/aws-serverless/prerequisites.md) - what you need before you begin.
{% endstep %}

{% step %}

### Create your workspace

Follow [Create and manage workspaces](/query-engine/guides/workspaces/create-and-manage-workspaces.md) - pick **Serverless**, **AWS**, and your region.
{% endstep %}

{% step %}

### Configure AWS access

See [Configure AWS access](/query-engine/guides/deployment/aws-serverless/configure-aws-access.md) - create the cross-account IAM role and register it with e6data.
{% endstep %}

{% step %}

### Connect S3 and Glue

See [Connect S3 and Glue](/query-engine/guides/deployment/aws-serverless/connect-s3-and-glue.md) - create a catalog over your data.
{% endstep %}

{% step %}

### Create a cluster

See [Create a cluster](/query-engine/guides/deployment/aws-serverless/create-cluster.md) - provision the compute that runs queries.
{% endstep %}

{% step %}

### Run your first query

See [Run your first query](/query-engine/guides/deployment/aws-serverless/run-first-query.md) - confirm the deployment works.
{% endstep %}
{% endstepper %}

For help along the way, see [FAQs](/query-engine/guides/deployment/aws-serverless/faqs.md) and [Troubleshooting](/query-engine/guides/deployment/aws-serverless/troubleshooting.md).

## See also

* [AWS In-VPC / CloudPrem](/query-engine/guides/deployment/aws-in-vpc.md) - deploy e6data inside your own VPC instead.

Once your cluster is running, [run your first query](/query-engine/guides/deployment/aws-serverless/run-first-query.md).


---

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