eks-best-practiceslisted

Advisory guidance for Amazon EKS architecture and configuration decisions — compute strategy, networking, security, reliability, cost, autoscaling, observability, multi-tenancy, and upgrade planning. Also answers Terraform configuration questions about terraform-aws-modules/terraform-aws-eks. Use for any EKS planning or architectural judgment call, even when phrased casually. Do NOT use for generating documents or code (eks-design, eks-build), scoring or auditing a live cluster (eks-operation-review, eks-upgrade-check), discovering what is running (eks-recon), MCP tooling setup (eks-mcp-server), building developer platforms and IDPs (eks-platform-engineering), GenAI/LLM workload decisions — GPU vs Trainium/Inferentia, vLLM/Ray serving, distributed training, ML storage (eks-genai), or compliance-regime hardening and audit prep — HIPAA/PCI/FedRAMP, CIS benchmarks, GuardDuty, image signing (eks-security).
aws-samples/sample-apex-skills · ★ 37 · AI & Automation · score 73

Install: claude install-skill aws-samples/sample-apex-skills

# EKS Best Practices Comprehensive guidance for designing, deploying, and operating Amazon EKS clusters. Consolidates guidance from the AWS EKS Best Practices Guide, AWS EKS HA/Resiliency Guide, and terraform-aws-modules/terraform-aws-eks examples. ## When to Use This Skill **Activate this skill when:** - Designing a new EKS cluster architecture - Choosing between EKS compute options (Fargate, MNG, Karpenter, Auto Mode) - Configuring EKS networking (VPC CNI, ingress, service mesh) - Implementing EKS security (IAM, pod security, secrets) - Planning cluster upgrades or migrations - Reviewing EKS architecture decisions - Working with terraform-aws-modules/terraform-aws-eks examples - Optimizing EKS cost or scaling to large clusters **Don't use this skill for:** - Generic Kubernetes concepts (Claude knows these) - Provider-specific API reference (link to AWS docs) - Non-EKS container orchestration (ECS, Lambda) - Step-by-step EKS upgrade execution — this skill covers upgrade strategy and architectural decisions, not the per-version procedures themselves. ## EKS Architecture Decision Framework ### When to Use EKS | Requirement | EKS | ECS | Lambda | |-------------|-----|-----|--------| | **Kubernetes ecosystem** | ✅ Native K8s | ❌ AWS-proprietary | ❌ | | **Portable across clouds** | ✅ Standard K8s API | ❌ AWS-only | ❌ AWS-only | | **Long-running services** | ✅ | ✅ | ⚠️ 15 min limit | | **Minimal ops overhead** | Medium | Low | Lowest | | **GPU/ML workloads** | ✅ Best suppor