Kubernetes on AWS: EKS Setup with eksctl Kubernetes on AWS: EKS Setup with eksctl

A local kind cluster is perfect for learning, but eventually you need Kubernetes on real infrastructure. On AWS, the managed option is EKS (Elastic Kubernetes Service), and the fastest way to stand one up is eksctl. This guide takes you from nothing to a running EKS cluster with a workload exposed to the internet — and, just as important, shows you how to tear it down so it does not quietly drain your account.

EKS removes the hardest part of running Kubernetes: you do not manage or patch the control plane. AWS does. With eksctl on top, a production-shaped cluster is a single command. If you are brand new to the objects you will deploy, skim Kubernetes fundamentals first, then come back.

Prerequisites

You need three CLI tools and AWS credentials with permission to create EKS, EC2, and CloudFormation resources.

# AWS CLI — configure credentials first
aws configure
aws sts get-caller-identity        # confirm you are authenticated

# eksctl (macOS / Linux via Homebrew)
brew install eksctl

# kubectl
brew install kubectl

Create the Cluster with One Command

This is the whole setup. eksctl provisions a VPC, the EKS control plane, and a managed node group — all as CloudFormation stacks.

eksctl create cluster \
  --name demo \
  --region us-east-1 \
  --nodes 2 \
  --node-type t3.medium \
  --managed

It takes 15–20 minutes. eksctl streams progress and, when finished, writes the cluster’s credentials into your ~/.kube/config automatically. Verify:

kubectl get nodes
kubectl get pods -A        # core system pods should be Running

    graph TD
  A[eksctl create cluster] --> B[CloudFormation]
  B --> C[VPC + Subnets]
  B --> D[EKS Control Plane - managed by AWS]
  B --> E[Managed Node Group]
  E --> F[EC2 Worker Nodes]
  D --> F
  F --> G[Your Pods]
  

Deploy and Expose a Workload

With nodes ready, deploy an app exactly as you would on any cluster. The only EKS-specific part is the Service type.

kubectl create deployment web --image=nginx --replicas=2
kubectl expose deployment web --type=LoadBalancer --port=80 --target-port=80
kubectl get svc web -w

A Service of type LoadBalancer tells the AWS cloud controller to provision an Elastic Load Balancer. After a minute or two, the EXTERNAL-IP column shows a public DNS name — open it in a browser and you are hitting pods running on EKS.

Inspect and Operate the Cluster

EKS clusters behave like any other Kubernetes cluster, so your usual workflow applies — every command from the kubectl cheat sheet works here.

kubectl get deploy,svc,pods -o wide
kubectl logs deploy/web
eksctl get cluster                 # eksctl's view of your clusters
eksctl get nodegroup --cluster demo

If a pod will not start, the diagnosis is identical to anywhere else — see how to fix Kubernetes CrashLoopBackOff.

Scaling Nodes

Scaling pods is kubectl scale. Scaling the underlying EC2 capacity is an eksctl (or autoscaler) operation:

eksctl scale nodegroup --cluster demo --name <nodegroup> --nodes 4

For production, install the Cluster Autoscaler or Karpenter so node capacity follows demand automatically instead of being set by hand.

Clean Up to Avoid a Surprise Bill

This is the step people forget. One command deletes everything eksctl created — control plane, node group, and the load balancer from your Service:

kubectl delete svc web            # removes the ELB first
eksctl delete cluster --name demo --region us-east-1

Common Pitfalls

• Skipping cleanup. The number one EKS surprise is a forgotten cluster. Make eksctl delete cluster a habit.
• Insufficient IAM permissions. eksctl needs broad rights to create CloudFormation, EKS, EC2, and IAM resources. A too-narrow policy fails mid-creation.
• One ELB per Service. Fine for demos, expensive at scale — move to Ingress.
• Region mismatch. Your kubectl context, eksctl commands, and AWS CLI must all target the same region.

If you already run CI/CD on AWS, the natural follow-on is wiring a pipeline to EKS — the same idea as the existing walkthrough on deploying Jenkins on EKS.

References and Further Reading

• Amazon Web Services. Amazon EKS User Guide. AWS Documentation.
• Weaveworks & AWS. eksctl — The official CLI for Amazon EKS. eksctl Documentation.
• Amazon Web Services. Getting started with Amazon EKS – eksctl. AWS Documentation.
• Kubernetes Authors. Service of type LoadBalancer. Kubernetes Documentation.