> 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/reference/configuration-reference/aws-configuration.md).

# AWS configuration

Reference for the AWS resources and configuration values used in an In-VPC e6data deployment on EKS.

This reference summarizes the AWS resources and configuration an In-VPC (CloudPrem) deployment on EKS uses. For the step-by-step build, see [Configure registry, VPC, EKS, and networking](/query-engine/guides/deployment/aws-in-vpc/configure-registry-vpc-eks-networking.md).

## Common variables

These environment variables are referenced throughout the build commands:

| Variable         | Meaning                                             |
| ---------------- | --------------------------------------------------- |
| `CLUSTER_NAME`   | Base name for the EKS cluster and derived resources |
| `REGION`         | AWS region                                          |
| `VPC_CIDR`       | VPC address range (for example, `10.0.0.0/16`)      |
| `AWS_ACCOUNT_ID` | Your AWS account ID                                 |
| `WORKSPACE_NAME` | The e6data workspace name                           |

## Infrastructure

| Area       | What's created                                                                                                                        |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Networking | VPC, public/private subnets across AZs, Internet Gateway, NAT Gateway, route tables, and an S3 VPC endpoint                           |
| EKS        | An EKS cluster (a recent Kubernetes version), OIDC provider, Pod Identity agent, VPC CNI and EBS CSI add-ons, and a system node group |
| Storage    | A versioned, encrypted, SSL-only S3 bucket for workspace metadata                                                                     |

## IAM roles

| Role                                                           | Purpose                                                                                  |
| -------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| EKS cluster role                                               | EKS control-plane permissions                                                            |
| EKS node role                                                  | Worker-node permissions (worker, CNI, ECR read, SSM)                                     |
| Karpenter role                                                 | Node provisioning (EC2, pricing, SQS interruption queue), via EKS Pod Identity           |
| ALB Controller role                                            | AWS Load Balancer Controller permissions, via EKS Pod Identity                           |
| EBS CSI driver role                                            | EBS volume management for the CSI driver add-on, via EKS Pod Identity                    |
| Workspace engine / console roles (and an app role for add-ons) | Per-workspace access to the metadata bucket and cross-account data, via EKS Pod Identity |

## See also

* [Configure registry, VPC, EKS, and networking](/query-engine/guides/deployment/aws-in-vpc/configure-registry-vpc-eks-networking.md)
* [Kubernetes configuration](/query-engine/reference/configuration-reference/kubernetes-configuration.md)
* [Environment variables](/query-engine/reference/configuration-reference/environment-variables.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/reference/configuration-reference/aws-configuration.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.