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

# AWS In-VPC / CloudPrem

Deploy e6data inside your own AWS VPC on Amazon EKS - the end-to-end CloudPrem deployment, from infrastructure to your first query.

An **In-VPC** (CloudPrem) deployment runs the entire e6data Compute Plane inside **your own AWS VPC** on Amazon EKS. Your data and query traffic never leave your environment; the e6data Control Plane handles only admin operations, workspace management, access control, and observability (sent over HTTPS on port 443).

{% hint style="info" %}
**Who this is for:** your infrastructure / platform team - you need AWS admin access to deploy into your own VPC (creating the VPC, EKS cluster, IAM roles, and networking). **Before you start:** the AWS CLI, `kubectl`, and Helm, and familiarity with EKS.
{% endhint %}

{% hint style="info" %}
For a fully managed alternative with no infrastructure to run, see [AWS Serverless](/query-engine/guides/deployment/aws-serverless.md).
{% endhint %}

## What you'll deploy

The deployment proceeds in order:

{% stepper %}
{% step %}

### Review the architecture

See [Architecture](/query-engine/guides/deployment/aws-in-vpc/architecture.md) - what runs in your account vs. e6data's.
{% endstep %}

{% step %}

### Check prerequisites

See [Prerequisites](/query-engine/guides/deployment/aws-in-vpc/prerequisites.md) - required tools and the items e6data provides during onboarding.
{% endstep %}

{% step %}

### Configure registry, VPC, EKS, and networking

Follow [Configure registry, VPC, EKS, and networking](/query-engine/guides/deployment/aws-in-vpc/configure-registry-vpc-eks-networking.md) - AWS infrastructure and the Kubernetes platform components.
{% endstep %}

{% step %}

### Deploy workspace and e6data

Follow [Deploy workspace and e6data](/query-engine/guides/deployment/aws-in-vpc/deploy-workspace-and-e6data.md) - the workspace namespace, NodePool, and e6data workspace components.
{% endstep %}

{% step %}

### Register a catalog

See [Register a catalog](/query-engine/guides/deployment/aws-in-vpc/register-catalog.md) - connect your data lake.
{% endstep %}

{% step %}

### Create a cluster

See [Create a cluster](/query-engine/guides/deployment/aws-in-vpc/create-cluster.md) - provision compute.
{% endstep %}

{% step %}

### Run your first query

See [Run your first query](/query-engine/guides/deployment/aws-in-vpc/run-first-query.md) - validate the install.
{% endstep %}
{% endstepper %}

Ongoing operations are covered in [Component versions and operations](/query-engine/guides/deployment/aws-in-vpc/component-versions-and-operations.md), [Delete workspace](/query-engine/guides/deployment/aws-in-vpc/delete-workspace.md), and [Troubleshooting](/query-engine/guides/deployment/aws-in-vpc/troubleshooting.md).

## See also

* [Deployment models](/query-engine/get-started/deployment-models.md) - Serverless vs. In Your VPC.
* [CloudPrem cluster operations](/query-engine/guides/clusters/cloudprem-cluster-operations.md) - operating clusters in an In-VPC deployment.

Once your cluster is running, [run your first query](/query-engine/guides/deployment/aws-in-vpc/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-in-vpc.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.