> ## Documentation Index
> Fetch the complete documentation index at: https://delivery.vexa.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# EKS

> Amazon EKS — what the provider profile sets, what the cluster must provide, and how far the evidence goes

**Amazon Elastic Kubernetes Service — `--provider aws-eks`.** The generic [Kubernetes requirements](/environments/kubernetes) apply unchanged; this page is the delta and how far the evidence goes.

## Status

**Provider profile implemented; not yet validated by a station run in a real EKS cluster.** `kit/providers/aws-eks/profile.env` carries `PROFILE_TESTED=no`, and the installer prints that on every run — *this profile is declared, not yet exercised end-to-end; expect deltas.* The deltas below are named from AWS documentation, not measured by us. The first subscriber on EKS validates this page: the [preflight](/preflight), smoke and [station](/station-gate) reports from that install are the evidence, and this line changes when they exist.

## What the provider profile configures

`install.sh` has no per-provider branches — provider differences live only in `kit/providers/<name>/profile.env`. The `aws-eks` file sets the same pinned versions every profile sets, Argo CD `v3.5.1` and Kyverno `v1.19.0`, and nothing else. It installs no addon, selects no storage class and writes no load-balancer annotation. Those are your cluster's own configuration. Preflight checks the storage class (P8) and the pull path to the channel (P5, P7); it reads **no** load-balancer or ingress state at all, so that row is yours to confirm.

## What the cluster must provide

| Requirement                                                                                                                       | Why                                                                                                               |
| --------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **The EBS CSI addon, with a StorageClass marked default** (gp3)                                                                   | EKS ships no default StorageClass. Without one, preflight P8 fails and every delivered volume claim sits Pending. |
| **The AWS Load Balancer Controller**, or classic ELB, or an ingress you manage                                                    | `type: LoadBalancer` provisions nothing on EKS by itself                                                          |
| Kubernetes ≥ 1.29                                                                                                                 | the P9 floor                                                                                                      |
| Outbound reachability to the channel registry, or your own mirror — an ECR pull-through cache is the natural one here             | the subscription pulls; nothing pushes in. Digests and signatures survive mirroring.                              |
| 2 nodes × 4 vCPU / 8 GB, plus headroom per concurrent meeting bot — it requests 500m / 1Gi and its limit ships at 2 vCPU / 2560Mi | measured on the reference environment: p50 922Mi, max 1292Mi across 10 bots                                       |

Next: [Install](/install) · [Preflight](/preflight) · [Kubernetes](/environments/kubernetes)