🎯 Learning Objectives

• Learn how to create and configure an EKS Cluster through the AWS Console
• Understand the difference between EKS Auto Mode, Node Groups, and Fargate Profiles
• Learn how to create the required IAM Roles for the cluster and nodes
• Understand the Networking, Monitoring, and Add-ons options in EKS
• Learn how the EBS CSI Driver and EFS CSI Driver integrate with EKS

Part 1: Creating an EKS Cluster — Basic Configuration

Overview

In the EKS Console, we can choose between two configuration modes: Quick Configuration and Custom Configuration. We use Custom Configuration to explore all available options.

EKS Auto Mode

EKS Auto Mode is a new feature that allows EKS to manage the underlying infrastructure automatically. When a new Pod cannot fit onto existing nodes, EKS automatically creates a new node — no manual infrastructure management required.

Key Points

• Example cluster name: DemoEKSCluster
• A Cluster IAM Role is required — create it using "Create Recommended Role"
• The Auto Mode role requires the following Managed Policies:
  • AmazonEKSBlockStoragePolicy
  • AmazonEKSClusterPolicy
  • AmazonEKSComputePolicy
  • AmazonEKSLoadBalancingPolicy
  • AmazonEKSNetworkingPolicy
• The required Node IAM Role is named AmazonEKSAutoNodeRole — also created via "Create Recommended Role"
• Cluster Access: enable Cluster Administrator Access for the current IAM principal
• Kubernetes Version: leave as default
• Auto Mode Node Pools: General Purpose and System