< Back to home


Fully managed Kubernetes control plane(master). Meaning

we create and worry about worker nodes only.

Amazon EKS is a managed service that makes it easy for us to use Kubernetes on AWS without needing to install and operate your own Kubernetes control plane.

EKS workflow

ECS vs EKS vs Fargate

Kubernetes/ k8s installation options


video to follow: https://www.youtube.com/watch?v=DcnviAwmzM4

install kubectl


install AWS CLI


Configure AWS CLI


create cluster

  • permission for IAM role for cluster
    • AmazonEKSClusterPolicy

here i am using default VPC and subnets. in production create custom. use private subnets. for load balancer etc. use public subnet.

networking add on - leave defaults

leave logging off as it incurrs too much charge

check if cluster is up

aws eks --region us-east-1 describe-cluster --name gouravk8s01 --query cluster.status

update kubeconfig

aws eks --region us-east-1 update-kubeconfig --name gouravk8s01

if having problem :

// Start with fresh file rm ~/.kube/config

validate kubectl configuration to master node

kubectl get svc

Now add node group

validate worker node status

kubectl get nodes --watch

delete unused node group and cluster to avoid incurring charges

if deletion is taking too long..the node group could have dependency attached to it that needs to be delete first like security groups, ENI(elastic network interface) etc.

Note: It's normal for your cluster to take time to delete. You aren't charged for a cluster that is in the DELETING state.