Solving Real DevOps Challenge: Setting up EKS Cluster on AWS Last week, I faced an issue while de...Solving Real DevOps Challenge: Setting up EKS Cluster on AWS Last week, I faced an issue while de...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Asma's avatar
Asma Malik
• Nov 11
Solving Real DevOps Challenge: Setting up EKS Cluster on AWS
Last week, I faced an issue while deploying a Kubernetes cluster using EKS. Everything looked fine VPC, IAM roles, and subnets were configured but kubectl get nodes kept showing no resources found.
After checking logs and configurations, I realized the issue was simple but critical: My worker nodes were not properly attached to the EKS cluster.
Here’s the quick fix that worked for me: Create a proper Node Group linked to the same cluster name. Ensure the EC2 IAM role has policies:
AmazonEKSWorkerNodePolicy
AmazonEKS_CNI_Policy
AmazonEC2ContainerRegistryReadOnly Update your aws-auth ConfigMap with correct node role ARN. Run:
kubectl get nodes
and watch them appear like magic.
#AWS #EKS #Kubernetes #DevOps #Cloud #Infrastructure #Automation #AWSCommunity
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started