Node groups (managed, self-managed, Fargate) in AWS - Mini Project: Build & Apply

Create an EKS Cluster with Managed, Self-Managed, and Fargate Node Groups

📖 Scenario: You are setting up a Kubernetes cluster on AWS using Amazon EKS. You want to create three types of node groups to run your workloads: a managed node group, a self-managed node group, and a Fargate profile for serverless compute.This setup helps you understand how to configure different node groups for various workload needs.

🎯 Goal: Build an Amazon EKS cluster with one managed node group, one self-managed node group, and one Fargate profile using AWS CloudFormation YAML syntax.This will demonstrate how to configure each node group type properly.

📋 What You'll Learn

Create an EKS cluster resource named MyEKSCluster.

Create a managed node group named ManagedNodeGroup attached to MyEKSCluster.

Create a self-managed node group using an Auto Scaling Group named SelfManagedNodeGroup.

Create a Fargate profile named MyFargateProfile for the cluster.

Use valid AWS CloudFormation YAML syntax with correct resource types and properties.

💡 Why This Matters

🌍 Real World

This project simulates setting up a Kubernetes cluster on AWS with different node group types to optimize cost and performance for various workloads.

💼 Career

Understanding how to configure managed, self-managed, and Fargate node groups is essential for cloud engineers and DevOps professionals working with AWS EKS.

1

Create the EKS Cluster Resource

Write the AWS CloudFormation YAML code to create an EKS cluster resource named MyEKSCluster with the Kubernetes version set to 1.27 and role ARN as arn:aws:iam::123456789012:role/EKSClusterRole.

AWS

# Your code here to create the EKS cluster resource named MyEKSCluster

Need a hint?

Use AWS::EKS::Cluster resource type and specify Version and RoleArn properties.

2

Add a Managed Node Group

Add a managed node group resource named ManagedNodeGroup attached to the cluster MyEKSCluster. Use instance types t3.medium and set the node group scaling to minimum 1, maximum 3, and desired 2 nodes.

AWS

Resources:
  MyEKSCluster:
    Type: AWS::EKS::Cluster
    Properties:
      Name: MyEKSCluster
      Version: '1.27'
      RoleArn: arn:aws:iam::123456789012:role/EKSClusterRole
      ResourcesVpcConfig:
        SubnetIds:
          - subnet-abc12345
          - subnet-def67890
# Add ManagedNodeGroup resource here

Need a hint?

Use AWS::EKS::Nodegroup resource type and link it to MyEKSCluster with ClusterName.

3

Add a Self-Managed Node Group with Auto Scaling Group

Add a self-managed node group by creating an Auto Scaling Group resource named SelfManagedNodeGroup with launch configuration SelfManagedLaunchConfig. Use instance type t3.medium, minimum size 1, maximum size 3, and desired capacity 2. Attach the Auto Scaling Group to subnets subnet-abc12345 and subnet-def67890.

AWS

Resources:
  MyEKSCluster:
    Type: AWS::EKS::Cluster
    Properties:
      Name: MyEKSCluster
      Version: '1.27'
      RoleArn: arn:aws:iam::123456789012:role/EKSClusterRole
      ResourcesVpcConfig:
        SubnetIds:
          - subnet-abc12345
          - subnet-def67890
  ManagedNodeGroup:
    Type: AWS::EKS::Nodegroup
    Properties:
      ClusterName: !Ref MyEKSCluster
      NodegroupName: ManagedNodeGroup
      ScalingConfig:
        MinSize: 1
        MaxSize: 3
        DesiredSize: 2
      Subnets:
        - subnet-abc12345
        - subnet-def67890
      InstanceTypes:
        - t3.medium
      NodeRole: arn:aws:iam::123456789012:role/EKSNodeGroupRole
# Add SelfManagedLaunchConfig and SelfManagedNodeGroup resources here

Need a hint?

Create a launch configuration and an Auto Scaling Group with the specified properties.

4

Add a Fargate Profile for Serverless Compute

Add a Fargate profile resource named MyFargateProfile for the cluster MyEKSCluster. Set the pod execution role ARN to arn:aws:iam::123456789012:role/AmazonEKSFargatePodExecutionRole. Configure selectors to run pods in namespace default.

AWS

Resources:
  MyEKSCluster:
    Type: AWS::EKS::Cluster
    Properties:
      Name: MyEKSCluster
      Version: '1.27'
      RoleArn: arn:aws:iam::123456789012:role/EKSClusterRole
      ResourcesVpcConfig:
        SubnetIds:
          - subnet-abc12345
          - subnet-def67890
  ManagedNodeGroup:
    Type: AWS::EKS::Nodegroup
    Properties:
      ClusterName: !Ref MyEKSCluster
      NodegroupName: ManagedNodeGroup
      ScalingConfig:
        MinSize: 1
        MaxSize: 3
        DesiredSize: 2
      Subnets:
        - subnet-abc12345
        - subnet-def67890
      InstanceTypes:
        - t3.medium
      NodeRole: arn:aws:iam::123456789012:role/EKSNodeGroupRole
  SelfManagedLaunchConfig:
    Type: AWS::AutoScaling::LaunchConfiguration
    Properties:
      ImageId: ami-0abcdef1234567890
      InstanceType: t3.medium
      IamInstanceProfile: EKSWorkerNodeInstanceProfile
      SecurityGroups:
        - sg-0123456789abcdef0
  SelfManagedNodeGroup:
    Type: AWS::AutoScaling::AutoScalingGroup
    Properties:
      LaunchConfigurationName: !Ref SelfManagedLaunchConfig
      MinSize: 1
      MaxSize: 3
      DesiredCapacity: 2
      VPCZoneIdentifier:
        - subnet-abc12345
        - subnet-def67890
      Tags:
        - Key: Name
          Value: SelfManagedNodeGroup
          PropagateAtLaunch: true
# Add MyFargateProfile resource here

Need a hint?

Use AWS::EKS::FargateProfile resource type and specify selectors for the default namespace.