> 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.md). # Deployment - [AWS Serverless](https://docs.e6data.com/query-engine/guides/deployment/aws-serverless.md): Deploy e6data as a Serverless workspace on AWS - the end-to-end path from creating a workspace to running your first query. - [Architecture](https://docs.e6data.com/query-engine/guides/deployment/aws-serverless/architecture.md): How a Serverless e6data deployment on AWS works - managed compute in e6data's account, your data read in place via a cross-account IAM role. - [Prerequisites](https://docs.e6data.com/query-engine/guides/deployment/aws-serverless/prerequisites.md): What you need before deploying a Serverless e6data workspace on AWS. - [Configure AWS access](https://docs.e6data.com/query-engine/guides/deployment/aws-serverless/configure-aws-access.md): Create the cross-account IAM role e6data uses to read your S3 data and Glue catalog, then register its ARN in e6data. - [Connect S3 and Glue](https://docs.e6data.com/query-engine/guides/deployment/aws-serverless/connect-s3-and-glue.md): Create an AWS Glue catalog over your S3 data in a Serverless e6data workspace, using the cross-account IAM role. - [Create cluster](https://docs.e6data.com/query-engine/guides/deployment/aws-serverless/create-cluster.md): Create and configure a cluster to run queries in a Serverless e6data workspace on AWS. - [Run first query](https://docs.e6data.com/query-engine/guides/deployment/aws-serverless/run-first-query.md): Confirm your Serverless e6data deployment on AWS works by running a query against your catalog. - [FAQs](https://docs.e6data.com/query-engine/guides/deployment/aws-serverless/faqs.md): Common questions about data access, permissions, and revocation for a Serverless e6data deployment on AWS. - [Troubleshooting](https://docs.e6data.com/query-engine/guides/deployment/aws-serverless/troubleshooting.md): Resolve common IAM, cross-account, and catalog connection errors in a Serverless e6data deployment on AWS. - [AWS In-VPC / CloudPrem](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc.md): Deploy e6data inside your own AWS VPC on Amazon EKS - the end-to-end CloudPrem deployment, from infrastructure to your first query. - [Architecture](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc/architecture.md): 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. - [Prerequisites](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc/prerequisites.md): Tools, access, and onboarding items required before an In-VPC e6data deployment on AWS. - [Configure registry, VPC, EKS, and networking](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc/configure-registry-vpc-eks-networking.md): Build the AWS infrastructure (VPC, IAM, EKS, networking, ECR access) and install the Kubernetes platform components for an In-VPC e6data deployment. - [Deploy workspace and e6data](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc/deploy-workspace-and-e6data.md): Create the workspace namespace and NodePool, deploy the e6data workspace components with Helm, wait for reconciliation, and configure DNS. - [Register catalog](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc/register-catalog.md): Grant the In-VPC engine access to your data lake and register a catalog in your e6data workspace. - [Create cluster](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc/create-cluster.md): Create a cluster in your In-VPC workspace to run queries on the EKS compute Karpenter provisions. - [Run first query](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc/run-first-query.md): Validate an In-VPC e6data install by verifying the cluster and workspace components, then running your first query. - [Component versions and operations](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc/component-versions-and-operations.md): The Kubernetes workloads an In-VPC e6data deployment runs, the resource footprint, and the operational pattern for installs and upgrades. - [Delete workspace](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc/delete-workspace.md): Tear down an In-VPC e6data workspace and its AWS resources in the reverse order they were created. - [Security best practices](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc/security-best-practices.md): Security best practices for hardening an e6data In Your VPC deployment on AWS - identity, network, and EKS configuration. - [FAQs](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc/faqs.md): Frequently asked questions about deploying and operating e6data In Your VPC on AWS - networking, encryption, instance types, and Kubernetes setup. - [Troubleshooting](https://docs.e6data.com/query-engine/guides/deployment/aws-in-vpc/troubleshooting.md): Diagnose common issues in an In-VPC e6data deployment - scheduling, image pulls, the operator, reconciliation, Pod Identity, load balancers, and monitoring. - [Azure Serverless](https://docs.e6data.com/query-engine/guides/deployment/azure-serverless.md): Deploy e6data as a Serverless workspace on Azure - the end-to-end path from creating a workspace to running your first query. - [Architecture](https://docs.e6data.com/query-engine/guides/deployment/azure-serverless/architecture.md): How a Serverless e6data deployment on Azure works - managed compute in e6data's subscription, your ADLS Gen2 data read keylessly via Workload Identity. - [Prerequisites](https://docs.e6data.com/query-engine/guides/deployment/azure-serverless/prerequisites.md): What you need before deploying a Serverless e6data workspace on Azure. - [Configure Azure access](https://docs.e6data.com/query-engine/guides/deployment/azure-serverless/configure-azure-access.md): Grant e6data keyless read access to your Azure storage - provision a User-Assigned Managed Identity and register it as a Storage Credential. - [Connect ADLS and catalog](https://docs.e6data.com/query-engine/guides/deployment/azure-serverless/connect-adls-and-catalog.md): Create a catalog over your ADLS Gen2 data in a Serverless e6data workspace on Azure, using a shared Storage Credential. - [Create cluster](https://docs.e6data.com/query-engine/guides/deployment/azure-serverless/create-cluster.md): Create and configure a cluster to run queries in a Serverless e6data workspace on Azure. - [Run first query](https://docs.e6data.com/query-engine/guides/deployment/azure-serverless/run-first-query.md): Confirm your Serverless e6data deployment on Azure works by running a query against your catalog. - [FAQs](https://docs.e6data.com/query-engine/guides/deployment/azure-serverless/faqs.md): Common questions about data access, permissions, and revocation for a Serverless e6data deployment on Azure. - [Troubleshooting](https://docs.e6data.com/query-engine/guides/deployment/azure-serverless/troubleshooting.md): Resolve common Managed Identity, federated-credential, and storage-access errors in a Serverless e6data deployment on Azure. - [Azure In-VPC / CloudPrem](https://docs.e6data.com/query-engine/guides/deployment/azure-in-vpc.md): Deploy e6data inside your own Azure VNet on AKS - the end-to-end CloudPrem deployment, from infrastructure to your first query. - [Architecture](https://docs.e6data.com/query-engine/guides/deployment/azure-in-vpc/architecture.md): How an In-VPC (CloudPrem) e6data deployment on Azure runs inside your own VNet on AKS, with engine pods on your node pools and data in your subscription. - [Prerequisites](https://docs.e6data.com/query-engine/guides/deployment/azure-in-vpc/prerequisites.md): Tools, Azure permissions, outbound network access, and onboarding items required before an In-VPC e6data deployment on AKS. - [Configure registry, Kubernetes, and networking](https://docs.e6data.com/query-engine/guides/deployment/azure-in-vpc/configure-registry-kubernetes-networking.md): Build the Azure infrastructure (VNet, AKS, identities, ADLS storage) and install the Kubernetes platform components for an In-VPC e6data deployment on AKS. - [Deploy workspace and e6data](https://docs.e6data.com/query-engine/guides/deployment/azure-in-vpc/deploy-workspace-and-e6data.md): Deploy an e6data workspace on AKS - namespace, TLS, service accounts and RBAC, NamespaceConfig, QueryRouter, and DNS, using explicit kubectl and YAML. - [Register catalog](https://docs.e6data.com/query-engine/guides/deployment/azure-in-vpc/register-catalog.md): Grant the In-VPC engine access to your data and register a catalog in your Azure-hosted e6data workspace. - [Create cluster](https://docs.e6data.com/query-engine/guides/deployment/azure-in-vpc/create-cluster.md): Create a cluster in your Azure In-VPC workspace to run queries on the AKS compute you provisioned. - [Run first query](https://docs.e6data.com/query-engine/guides/deployment/azure-in-vpc/run-first-query.md): Validate an Azure In-VPC e6data install by verifying the workspace pods, then running your first query. - [Component versions and operations](https://docs.e6data.com/query-engine/guides/deployment/azure-in-vpc/component-versions-and-operations.md): Component versions for the Azure In-VPC deployment, the Kubernetes workloads it runs, how to upgrade them, the upgrade order, and how to roll back. - [Delete workspace](https://docs.e6data.com/query-engine/guides/deployment/azure-in-vpc/delete-workspace.md): Tear down an e6data workspace in your AKS cluster with kubectl and az, and what to intentionally leave in place. - [Troubleshooting](https://docs.e6data.com/query-engine/guides/deployment/azure-in-vpc/troubleshooting.md): Common issues when deploying or running e6data In Your VPC on Azure, with diagnostic commands and fixes. --- # 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.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.