06 · KubernetesLab 36 / 59
Challengeterraform
Amazon EKS Cluster & Managed Node Group Provisioning — Challenge
Provision the cluster everything else runs on, with worker nodes in private subnets and no public endpoint.
- Time
- 15 min
- Level
- Intermediate
- Objectives
- 4 objectives
- Cost
- Billable
Where this fits in the platform
This lab adds
- An EKS cluster with workers in private subnets
Which lets you
- Application Routing with K8s Ingress & AWS Load Balancer Controller
- Kubernetes RBAC & Service Accounts
- Kubernetes Security Hardening (NetworkPolicies) & HPA
- Managing EKS Cluster Add-ons with Helm & IRSA
- GitHub Actions: Build, Scan and Deploy to EKS
- Deploying Kube-Prometheus-Stack on AWS EKS
- Incident: CrashLoopBackOff
- Incident: Service-to-Service Calls Fail
- Node Drain, Upgrade & Recovery
Before you start
Cost — Billable
An EKS control plane is $0.10/hour (~$73/month) from the moment it exists, with no free tier — plus the node group's EC2 instances and any NAT Gateway. Budget a few dollars for an afternoon, and destroy the cluster the same day.
The goal#
Build Amazon EKS Cluster & Managed Node Group Provisioning yourself, starting from an empty directory, without following the guided steps.
Everything you need is in the criteria above. Work down them one at a time, and verify each before moving to the next.
Hands-on environment
Run it on AWS
This lab builds real cloud infrastructure, so it needs your own AWS account. Follow the cost and cleanup notes above — the resources are yours, and so is the bill.
Anything you tick here is your own record. EgyKode cannot see inside that terminal, so the success criteria stay self-assessed even when the environment checks your work for you.
Rules#
- Do not open the guided lab until you have genuinely tried.
- When something fails, read the error before you search. The error message is the lesson.
- Tear down anything billable as soon as you finish.
If you get stuck#
The guided lab is one click away at the bottom of this page. Using it is not failure — coming back and repeating the challenge afterwards is the point.
You are done when
0 of 4
The concept behind it
Next up
Lab 36 of 59 on the project path