Personal Utility Load Balancer for EKS in Terraform

Amazon Internet Companies (AWS) offers a strong mixture of providers for constructing, deploying, and managing functions. Amazon Elastic Kubernetes Service (EKS) is a managed Kubernetes service that simplifies the method of deploying, managing, and scaling containerized functions utilizing Kubernetes. In sure eventualities, you would possibly need to deploy a non-public Utility Load Balancer (ALB) in entrance of your personal EKS cluster to deal with incoming visitors effectively. On this information, we’ll stroll by means of the method of establishing a non-public ALB in your personal EKS cluster utilizing Terraform, together with finest practices and complex particulars.

Conditions

Earlier than you start, guarantee you could have the next conditions:

• AWS Account: Entry to an AWS account with needed permissions to create sources.
• Terraform: Put in Terraform CLI in your native machine.
• AWS CLI: Put in AWS Command Line Interface to configure your AWS credentials.

Step-by-Step Information

1. Configure AWS Credentials

Open your terminal and run the next command to configure your AWS credentials:

aws configure

Enter your AWS Entry Key ID, Secret Entry Key, default area, and most popular output format.

2. Create a VPC

With a view to arrange a non-public ALB and EKS cluster, you want a Digital Personal Cloud (VPC) with personal subnets. Create a brand new Terraform configuration file (e.g., vpc.tf) and outline your VPC, personal subnets, and needed networking parts.

useful resource "aws_vpc" "my_vpc" {
  cidr_block = "10.0.0.0/16"
}

useful resource "aws_subnet" "private_subnets" {
  depend = 2
  cidr_block = "10.0.${depend.index}.0/24"
  vpc_id = aws_vpc.my_vpc.id

  tags = {
    Title = "private-subnet-${depend.index}"
  }
}

3. Create an EKS Cluster

Outline your EKS cluster configuration in a brand new Terraform configuration file (e.g., eks.tf). Specify your required Kubernetes model, cluster identify, and VPC configuration.

module "eks_cluster" {
  supply          = "terraform-aws-modules/eks/aws"
  cluster_name    = "my-eks-cluster"
  subnets         = aws_subnet.private_subnets[*].id
  vpc_id          = aws_vpc.my_vpc.id
  cluster_version = "1.21"
  tags = {
    Terraform = "true"
  }
}

4. Create a Safety Group for EKS Nodes

You should create a safety group to regulate inbound and outbound visitors in your EKS nodes. Add the next to your eks.tf file:

useful resource "aws_security_group" "eks_nodes" {
  name_prefix = "eks-nodes-"
  vpc_id      = aws_vpc.my_vpc.id
  // Outline your safety group guidelines right here
}

5. Create an ALB Safety Group

Equally, create a safety group for the personal ALB. Add the next to your eks.tf file:

useful resource "aws_security_group" "alb_sg" {
  name_prefix = "alb-sg-"
  vpc_id      = aws_vpc.my_vpc.id
  // Outline your ALB safety group guidelines right here
}

6. Create the Personal ALB

Create a brand new Terraform configuration file (e.g., alb.tf) to outline the personal ALB. Specify your listener configurations, safety teams, and goal group.

useful resource "aws_lb" "private_alb" {
  identify               = "private-alb"
  inner           = true
  load_balancer_type = "utility"
  subnets            = aws_subnet.private_subnets[*].id

  enable_deletion_protection = false
}

useful resource "aws_lb_listener" "alb_listener" {
  load_balancer_arn = aws_lb.private_alb.arn
  port              = 80
  protocol          = "HTTP"

  default_action {
    target_group_arn = aws_lb_target_group.alb_target_group.arn
    kind             = "fixed-response"

    fixed_response {
      content_type = "textual content/plain"
      message_body = "Hey, that is the ALB!"
      status_code  = "200"
    }
  }
}

useful resource "aws_lb_target_group" "alb_target_group" {
  identify        = "alb-target-group"
  port        = 80
  protocol    = "HTTP"
  vpc_id      = aws_vpc.my_vpc.id
  target_type = "ip"
}

7. Replace EKS Node Safety Group

Replace the EKS node safety group to permit visitors from the ALB safety group. Modify your eks.tf file:

useful resource "aws_security_group_rule" "alb_ingress" {
  kind        = "ingress"
  from_port   = 80
  to_port     = 80
  protocol    = "tcp"
  cidr_blocks = [aws_security_group.alb_sg.id]
  security_group_id = aws_security_group.eks_nodes.id
}

8. Deploy the Configuration

In your terminal, navigate to the listing containing your Terraform recordsdata and run the next instructions:

terraform init
terraform apply

Terraform will provision the sources outlined in your configuration recordsdata.

In Closing

Organising a non-public ALB in entrance of a non-public EKS cluster utilizing Terraform requires cautious planning and configuration. By following the steps outlined on this information, you may effectively deploy and handle your infrastructure, adhering to finest practices. This method lets you securely deal with incoming visitors and make sure the clean operation of your personal EKS cluster.

Do not forget that this information offers a fundamental setup for demonstration functions. In real-world eventualities, it is best to customise the configurations to match your utility’s necessities and think about safety, scalability, and excessive availability components.