eks-best-practices

Guide Amazon EKS architecture decisions for compute, networking, security, and Terraform planning.

39|14|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/aws-samples/sample-apex-skills --skill eks-best-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eks-best-practices
Source: https://github.com/aws-samples/sample-apex-skills/tree/main/skills/eks-best-practices
Command: npx skills add https://github.com/aws-samples/sample-apex-skills --skill eks-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you make correct, production-grade Amazon EKS architecture decisions and avoids common reliability, security, scaling, and cost pitfalls during cluster planning and Terraform-based implementations.

Core Features & Use Cases

  • EKS architecture decision guidance: Choose compute and operating models (Karpenter, Managed Node Groups, Fargate, Auto Mode, self-managed) based on workload needs and operational constraints.
  • Multi-tenant platform and isolation patterns: Apply namespace, RBAC, network policies, and quotas for tenant isolation with practical AWS-aligned recommendations.
  • Security, reliability, upgrades, and operations: Cover Pod Security, IAM/Pod Identity/IRSA, ingress patterns, PDBs, health probes, rollout/upgrade strategies (in-place vs blue-green), and observability essentials.
  • Terraform planning triggers and implementation support: Provide guidance when users discuss EKS configuration and Terraform with terraform-aws-modules/terraform-aws-eks, including add-ons, access entries, node group patterns, and IRSA integration.

Quick Start

Activate this skill when you’re planning an EKS cluster and need “the right way” to choose compute, networking, security, and upgrade strategy for a production multi-tenant platform.

Frequently Asked Questions about eks-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to choose between Karpenter, Managed Node Groups, and Fargate for EKS architecture?

EKS multi-tenant isolation is achieved by combining namespaces, RBAC, resource quotas, and network policies. This approach restricts tenant access and resource consumption, ensuring secure and stable multi-tenant platform operations.

How do I configure IRSA and Pod Identity for EKS security?

To configure EKS security, use IAM Roles for Service Accounts (IRSA) or EKS Pod Identity to grant pods specific AWS permissions. This avoids attaching broad IAM permissions to node instances, securing multi-tenant workloads.

Does the terraform-aws-eks module support EKS add-ons and access entries?

Yes, the terraform-aws-eks module supports configuring EKS add-ons, access entries, and node group patterns. It integrates IRSA and handles cluster architecture implementation while avoiding generic non-EKS Kubernetes guidance.

How do I plan EKS VPC networking and ingress for high pod density?

Plan EKS VPC networking by allocating sufficient IP subnets for pods and configuring ingress patterns carefully. Proper VPC and IP planning prevents address exhaustion and ensures reliable traffic routing for multi-tenant workloads.

What EKS upgrade strategies should I use for Kubernetes reliability?

For EKS reliability, use in-place or blue-green upgrade strategies, configure Pod Disruption Budgets, and implement health probes. These practices ensure minimal disruption during cluster updates and maintain workload availability.