Managed control plane · deliberate choices
Own the workload.
Trust the boundary.
Learn Amazon EKS from the first Pod to a secure, multi-AZ, observable, cost-aware enterprise platform.
Auto Mode · managed nodes · Fargate · Karpenter · Pod Identity · VPC CNI · delivery · SRE · recovery
REFERENCE TOPOLOGY · THREE AVAILABILITY ZONES
What you will be able to do
01 Choose the compute boundary02 Secure people and Pods03 Survive upgrades and failure04 Defend performance and cost
18 production chapters
From Kubernetes objects to platform judgment.
Every stage translates an AWS feature into a decision you can explain, test, and operate.The first architecture fork
Choose responsibility before instance type.
Auto Mode removes most node work. Managed node groups retain EC2 control. Fargate removes nodes for compatible Pods. Karpenter makes capacity follow workload constraints.
Make the compute decision →Less node responsibilityAUTO MODEMANAGED NODESSELF-MANAGEDMore node control
Retrieve and apply
Practice consequences, not product names.
A managed control plane is the beginning.