> ## Documentation Index > Fetch the complete documentation index at: https://docs.e6data.com/llms.txt > Use this file to discover all available pages before exploring further. # Architecture > How an In-VPC (CloudPrem) e6data deployment on AWS runs entirely inside your own VPC on EKS, with only admin and observability traffic reaching e6data. An In-VPC deployment runs the entire e6data Compute Plane inside your own AWS VPC on Amazon EKS. AWS In-VPC deployment architecture ## What this gives you * **Your data stays in your account.** All access to S3 and your catalog happens through IAM roles inside your environment. * **Full network isolation.** Query traffic never traverses the public internet. * **Complete visibility.** You have access to all AWS resources, logs, and metrics in your account. ## What the Control Plane does The e6data Control Plane (hosted by e6data) handles only: * Admin operations and workspace management. * Access control and authentication. * Observability - metrics and logs sent over HTTPS on port 443. Your data never leaves your environment. ## Components The deployment installs cluster-wide platform components (the e6-operator, Karpenter, the AWS Load Balancer Controller, and cert-manager) and, per workspace, a set of workspace components (console, query routing, monitoring collection, and a metadata compaction job). These are enumerated in [Component versions and operations](/platform/deploy/aws-cloudprem/component-versions-and-operations). ## See also * [Prerequisites](/platform/deploy/aws-cloudprem/prerequisites) - tools and onboarding items. * [Configure registry, VPC, EKS, and networking](/platform/deploy/aws-cloudprem/configure-registry-vpc-eks-networking) - build the infrastructure. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.