| 1 | --- |
| 2 | title: Amazon EKS |
| 3 | description: Run Alchemy's Kubernetes resources on Amazon EKS. Find the guide for creating clusters, ECR images, Pod Identity, and load balancers. |
| 4 | --- |
| 5 | |
| 6 | Everything in these Kubernetes docs works on |
| 7 | [Amazon EKS](https://aws.amazon.com/eks/). The EKS guide lives with |
| 8 | the rest of the AWS docs: |
| 9 | |
| 10 | **[EKS guide →](/aws/compute/eks)** |
| 11 | |
| 12 | It covers creating an Auto Mode cluster in the same Stack, granting |
| 13 | access, and what EKS adds when you pass the cluster as the `cluster` |
| 14 | of a `Kubernetes.*` resource: |
| 15 | |
| 16 | - **No kubeconfig.** Alchemy authenticates with your AWS |
| 17 | credentials. |
| 18 | - **A registry per workload.** `main` and `context` workloads are |
| 19 | built into ECR, so no `registry` setting is needed. |
| 20 | - **AWS bindings.** Bindings such as `AWS.DynamoDB.PutItem(table)` |
| 21 | grant IAM permissions to the workload through EKS Pod Identity. |
| 22 | - **Public load balancers.** `LoadBalancer` Services get an |
| 23 | internet-facing Network Load Balancer. |
| 24 | |
| 25 | To get started with AWS, see [AWS setup](/aws/setup). |
| 26 | |
| 27 | ## Use an EKS cluster through kubeconfig |
| 28 | |
| 29 | A context written by `aws eks update-kubeconfig` works with |
| 30 | [`Kubernetes.KubeConfig`](/kubernetes/clusters/connecting) like any |
| 31 | other cluster. That path only authenticates. Workloads need a |
| 32 | [registry](/kubernetes/clusters/registries) for `main` and `context` |
| 33 | images, and AWS bindings aren't wired to Pod Identity. Pass the |
| 34 | `AWS.EKS.Cluster` resource, or an `aws-eks` connection, to get the |
| 35 | full integration. |