Amazon EKS
Amazon Elastic Kubernetes Service (EKS) provides an AWS-managed Kubernetes control plane. Its operational boundary differs from a self-managed cluster: AWS maintains core control-plane services, while workload configuration and data-plane decisions remain important operator responsibilities. Source: KodeKloud AWS EKS, Architecture
Operational Decision Map
The following map synthesizes the reviewed KodeKloud lessons. It is a planning aid, not a complete deployment procedure or a current compatibility matrix. Source and reviewed-lesson scope
| Decision | Mechanism and Constraint | Deeper Note |
|---|---|---|
| Control-plane ownership | AWS operates core components; applications and data-plane configuration still need owners | Architecture |
| Pod IP capacity | VPC CNI uses node ENIs; IPv4 prefix delegation needs available subnet blocks | CNI |
| Traffic isolation | Verify VPC CNI policy enforcement and test DNS separately from application traffic | Network Policies |
| Operator access | IAM authentication and EKS access configuration are distinct from workload AWS permissions | Authentication and Authorization |
| Workload AWS access | IRSA and Pod Identity use different trust and credential-delivery mechanisms | ServiceAccount |
| Compute scale-out | Karpenter provisions nodes for unschedulable workloads; requests and topology constrain choices | Autoscaling |
| Persistent data | Choose between AZ-bound EBS block volumes and shared EFS filesystems | Storage |
| External credentials | Separate store rotation, mounted-file refresh, Secret sync, and application reload | Secrets |
| Observability | Collect control-plane, node, and application telemetry through appropriate paths | Logging and Monitoring |
| Maintenance | Plan control-plane, compute, and add-on updates separately | Cluster Upgrades |
Source for all rows: KodeKloud AWS EKS, reviewed lessons.
Evidence Limits
The course index also lists Fargate, node groups, IPv6, load-balancer integration, Gateway API, VPC Lattice, and security groups for Pods. Those lessons were not reviewed in this ingest. Do not infer their current support constraints from this summary. The source archive records questionable examples excluded from synthesis and the unsuccessful attempt to cross-check AWS documentation. Source: course index and ingest reliability notes