> 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/architecture.md). # 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](https://256648299-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz2BYVXehgdnk8dbeZoW5%2Fuploads%2Fgit-blob-6cbd7fbc4b49a4a073d275174f6a17c8c3e7190b%2FAWS%20IN-VPC%20PLT-V2.png?alt=media) ## 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](/query-engine/guides/deployment/aws-in-vpc/component-versions-and-operations.md). ## See also * [Prerequisites](/query-engine/guides/deployment/aws-in-vpc/prerequisites.md) - tools and onboarding items. * [Configure registry, VPC, EKS, and networking](/query-engine/guides/deployment/aws-in-vpc/configure-registry-vpc-eks-networking.md) - build the infrastructure. --- # 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/architecture.md?ask=&goal= ``` `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.