Deck 3 of 7: the AWS-managed Kubernetes platform.

Eight modules take you from how an EKS cluster is built to how it is upgraded, observed and paid for.

Deck 1

Foundations

Prerequisite: control plane, scheduling, workloads, networking, storage.

Deck 2

GKE deep dive

The Google counterpart; compare as you go.

You are here

3 · EKS deep dive

Access, compute, networking, identity, add-ons, operations.

Deck 4

On-prem, AKS, troubleshooting

Rancher, kubeadm, hybrid, diagnostic trees.

1Architecture and access

2Compute: nodes, Karpenter, Auto Mode

3Networking: VPC CNI and load balancing

4Identity and security

5Add-ons and storage

6Operations: upgrades, observability, cost

7Real-world: migration and incidents

8Quiz: 15 questions

Do Deck 1 first if Pods, Services and PVCs are not yet second nature.

Where this deck fits

Deck 3 builds directly on Deck 1. Every Kubernetes mechanism is the same on EKS; what changes is how AWS exposes the control plane, which AWS services plug into the cluster, and which operational jobs are yours. The eight modules follow the order you meet them on a real project: create and secure access to a cluster, decide on compute, wire the network and load balancers, set up identity and security, install add-ons and storage, then run upgrades, observability and cost control.

Decks 5 to 7 cut across platforms (security and tenancy, scaling and lifecycle, advanced networking and extensibility). Some topics here, such as Karpenter and Pod Identity, are introduced at the level an EKS operator needs; the deeper multi-tenancy and capacity material lives in later decks.

If you work on more than one cloud, read Deck 2 alongside this one. The comparison slides call out where EKS and GKE differ in ownership and defaults.