Guidelines and best practices

• Use multiple Availability Zones: Use multiple Availability Zones to ensure high availability and fault tolerance of your Kubernetes cluster. Spread your nodes across multiple Availability Zones to ensure that if one zone becomes unavailable, your application remains available in another zone. Specify a VPC and at least two subnets that are in different Availability Zones, and make sure that VPC has a sufficient number of IP addresses available for the cluster. The VPC must have a DNS hostname and DNS resolution support.

• Use security groups to control the network traffic to your Kubernetes cluster. Restrict access to only the necessary ports and protocols.

• Use IAM Roles: Use IAM roles to manage access to your Kubernetes cluster. This allows you to control who can manage and deploy resources to your cluster.

• Use IAM Roles when multiple users need identical access to the cluster.

• Use Kubernetes Labels: Use Kubernetes labels to organize your resources and manage your cluster. This allows you to easily group and manage your resources.

• Use Kubernetes namespaces to isolate your workloads and manage resource usage. This allows you to separate your workloads and manage them more effectively.

• Use AWS CloudWatch or third-party tools to monitor your Kubernetes cluster. This allows you to detect and resolve issues before they become critical.

• Use cluster autoscaler or karpenter to automatically scale your workloads based on demand. This ensures that your application remains responsive and available during peak periods.

For a full list of EKS best practices please refer to the official EKS Best Practices Guides.