profile

Fast Track To Cloud

Amazon EKS Auto Mode - Explained and Simplified 🚀

Published 21 days ago • 1 min read

Hello Reader,

Hi from Las Vegas, USA, where I am here to present at AWS Re:Invent, the biggest cloud conference on earth. In this edition I am going to go over a BIG announcement that you should learn - Amazon EKS Autonomous Mode or EKS Auto Mode or lovingly called EKS Auto!

Why is this important?

  • Getting started with Kubernetes is hard. Sure Amazon EKS manages control plane, but you need to install core addons, select AMI, create worker node, and scale the nodes.
  • It doesn't stop there. Anytime You update Kubernetes version, you have to upgrade the addons, and worker nodes (And ensure that the addons works with the upgraded version!). Even if you stay in the same Kubernetes version for long time, you need to rehydrate the AMIs for any new security patches
  • That's why EKS Auto is created! With EKS Auto, AWS takes care of the core addons, and worker nodes, you just focus on deploying the workload. Let's explore below

EKS Auto - How does it work?

  • With EKS Auto, you create the cluster, AWS automatically installs core addons Karpenter (scaling), Ingress (Networking), and EBS CSI (Storage) as part of Control Plane
  • What this means is AWS makes them secure, scalable, HA just like EKS control plane components. And AWS manages the versions as well
  • This is a big one - AWS manages the worker nodes. You do NOT need to create EC2. You simply deploy a workload, and AWS will create an EC2 for you. AWS manages the AMI. It is Bottlerocket based which is purpose built for running container and secure
  • AWS rightsizes the instance sizes based on the workload, automatically, and save you lot of money. You don't need to go and optimize the nodes
  • When AWS releases new AMI for the same Kubernetes version, AWS automatically updates the nodes, in a rolling deployment fashion, respecting your Kubernetes scheduling constraints
  • If you update EKS control plane to next Kubernetes version, AWS automatically updates the addons, and the worker nodes automatically. AWS tests the addons for new version and ensures they work smoothly

It sounds awfully similar to EKS Fargate?

  • EKS Fargate also abstracts the underlying infrastructure from you, which is similar to EKS Auto. However there are major diferences between EKS Auto and EKS Fargate. This post is getting long, so I put the difference in the below video, check it out
video preview​

Want to get trained by me and get cloud jobs?

I run AWS SA Bootcamp with Live Classes, Mock Interviews, 1:1, Hands-On, Behavioral, Resume Improvement and more. Past students got high paying jobs including at AWS. Check out details and waitlist for next cohort at https://www.sabootcamp.com/​

​

Keep learning and keep rocking 🚀,

Raj

Fast Track To Cloud

Rajdeep Saha

Free Cloud Interview Guide to crush your next interview. Plus, real-world answers for cloud interviews, and system design from a top Solutions Architect at AWS.

Read more from Fast Track To Cloud

Hello Reader, Happy Holidays! In today's newsletter, I am going to share three tips that helped me and many of my students switch careers to the cloud and get high-paying jobs. I will also share an update about the upcoming January cohort of the AWS SA Bootcamp. Tip 1: Leverage your IT experience Your existing IT experience is NOT throwaway. Don't think you can't reuse components of your existing knowledge in your cloud journey. For example, my student Abhisekh has deep knowledge of the...

3 days ago • 3 min read

Hello Reader, In today’s post, let’s look at another correct but average answer and a great answer that gets you hired to common cloud interview questions. Question - How did you do Disaster Recovery (DR) for your AWS application? Common but average answer - I will replicate it to another region What the interviewer is looking for is how DR strategies are chosen, and what are the different strategies. As an SA, you will be responsible for talking to the app team and coming up with an...

13 days ago • 2 min read

Hello Reader, A container icebreaker interview question is the fundamental container workflow from the local machine to the cloud. In this edition, we will start with the manual process that every project starts with, then we will show how this manual process gives way to CICD and then how it evolves to a more mature pipeline. Let's start with understanding the foundational flow first: Developer writes code, and associated Dockerfile to containerize the code in her local machine She uses...

27 days ago • 2 min read