Skip to main content
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).
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.
For a fully managed alternative with no infrastructure to run, see AWS Serverless.

​
What you’ll deploy

The deployment proceeds in order:
1

Review the architecture

See Architecture - what runs in your account vs. e6data’s.
2

Check prerequisites

See Prerequisites - required tools and the items e6data provides during onboarding.
3

Configure registry, VPC, EKS, and networking

Follow Configure registry, VPC, EKS, and networking - AWS infrastructure and the Kubernetes platform components.
4

Deploy workspace and e6data

Follow Deploy workspace and e6data - the workspace namespace, NodePool, and e6data workspace components.
5

Register a catalog

See Register a catalog - connect your data lake.
6

Create a cluster

See Create a cluster - provision compute.
7

Run your first query

See Run your first query - validate the install.
Ongoing operations are covered in Component versions and operations, Delete workspace, and Troubleshooting.

​
See also

Once your cluster is running, run your first query.
Last modified on September 29, 2026