AWS, Cloud Computing

4 Mins Read

Multi-AZ deployment of Amazon EKS

Introduction

Amazon Elastic Kubernetes Service (EKS) is a managed Kubernetes service provided by Amazon Web Services (AWS). It allows you to deploy, manage, and scale containerized applications using Kubernetes on AWS infrastructure. Multi-AZ (Availability Zone) deployment in Amazon EKS ensures high availability and fault tolerance for your Kubernetes clusters by distributing resources across multiple Availability Zones within an AWS region.

Benefits of Multi-AZ Deployment in Amazon EKS

  • High Availability: Distributing your cluster across multiple AZs ensures that your applications remain available in case of an AZ failure.
  • Fault Tolerance: If one AZ experiences issues, the workload can be shifted to another AZ, maintaining continuity.
  • Improved Performance: Distributing nodes across AZs can enhance the performance of your applications by leveraging resources from multiple locations.
  • Automatic Failover: Amazon EKS handles the deployment of nodes across AZs and ensures that your cluster is resilient to failures.

Pioneers in Cloud Consulting & Migration Services

  • Reduced infrastructural costs
  • Accelerated application deployment
Get Started

Steps to Deploy Multi-AZ Amazon EKS Cluster

Step 1: Spin up two Amazon EKS clusters in two different regions. Cluster 1 is in Mumbai, and Cluster 2 is in Singapore. The naming convention can be changed according to use case.

step1

step1b

Step 2: Create an OIDC provider for both the cluster after the cluster’s creation.

step2

Step 3: Create a policy and service account for the load balancer controller.

step3

Step 4: Create a load balancer controller with helm Amazon EKS charts and deploy it in both clusters. It will be visible in the kube-system namespace.

step4

step4b

step4c

step4d

Step 5: Deploy a sample application in both the clusters and ingress to create load balancers for public access.

step5

step5b

step5c

step5d

Step 6: Create a global accelerator, add a listener with endpoint groups for the two regions used, and add an endpoint for the ingress load balancer. Set traffic dial for the Mumbai region to 100% and the Singapore region to 0%.

step6

Step 7: After creating the global accelerator is completed, check the listener rule for the healthy and unhealthy status of the load balancer. Check the accessibility in the browser.

step7

step7b

Step 8: Stop the running sample application in the Singapore region and check the health status again. There will be 30 seconds of downtime before it routes to the healthy listener.

step8

step8b

Healthy listener

lis

Unhealthy listener

lis2

lis3

Conclusion

In conclusion, deploying a multi-AZ Amazon EKS cluster provides a robust foundation for running containerized applications with high availability and fault tolerance on the AWS cloud. Leveraging the managed Kubernetes service, Amazon EKS, and the eksctl command-line utility streamlines the process of creating and managing clusters, allowing you to focus on your applications rather than the underlying infrastructure. As you embark on your journey with multi-AZ Amazon EKS clusters, stay informed about the latest AWS updates and best practices. Regularly consult the official documentation for any changes or optimizations that may enhance the security, performance, and efficiency of your Kubernetes workloads on Amazon EKS.

With a well-designed and properly configured multi-AZ EKS cluster, you can confidently deploy and manage containerized applications with the reliability and scalability demanded by modern cloud-native architectures.

Drop a query if you have any questions regarding Amazon EKS cluster and we will get back to you quickly.

Making IT Networks Enterprise-ready – Cloud Management Services

  • Accelerated cloud migration
  • End-to-end view of the cloud environment
Get Started

About CloudThat

CloudThat is a leading provider of Cloud Training and Consulting services with a global presence in India, the USA, Asia, Europe, and Africa. Specializing in AWS, Microsoft Azure, GCP, VMware, Databricks, and more, the company serves mid-market and enterprise clients, offering comprehensive expertise in Cloud Migration, Data Platforms, DevOps, IoT, AI/ML, and more.

CloudThat is recognized as a top-tier partner with AWS and Microsoft, including the prestigious ‘Think Big’ partner award from AWS and the Microsoft Superstars FY 2023 award in Asia & India. Having trained 650k+ professionals in 500+ cloud certifications and completed 300+ consulting projects globally, CloudThat is an official AWS Advanced Consulting Partner, AWS Training Partner, AWS Migration Partner, AWS Data and Analytics Partner, AWS DevOps Competency Partner, Amazon QuickSight Service Delivery Partner, Amazon EKS Service Delivery Partner, Microsoft Gold Partner, AWS Microsoft Workload Partners, Amazon EC2 Service Delivery Partner, and many more.

To get started, go through our Consultancy page and Managed Services PackageCloudThat’s offerings.

FAQs

1. Why is Multi-AZ Deployment important for Amazon EKS Clusters?

ANS: – Multi-AZ deployment in Amazon EKS ensures high availability by distributing resources across multiple Availability Zones. This helps prevent downtime and improves the fault tolerance of your Kubernetes clusters, making them more resilient to infrastructure failures.

2. How can I check the number of nodes in each Availability Zone in my Amazon EKS Cluster?

ANS: – You can use the kubectl get nodes command to view the nodes in your EKS cluster. The output will display the nodes and their corresponding Availability Zones, allowing you to verify the distribution across multiple AZs.

WRITTEN BY Jeet Patel

Share

Comments

    Click to Comment

Get The Most Out Of Us

Our support doesn't end here. We have monthly newsletters, study guides, practice questions, and more to assist you in upgrading your cloud career. Subscribe to get them all!