← ClaudeAtlas

eks-designlisted

Use when designing EKS architecture. Generates design documents with Mermaid diagrams, ADRs, security architecture, and validation reports. Translates requirements into tailored EKS designs guided by Well-Architected best practices. Covers cluster architecture, compute, networking, security, addons, observability, cost, and upgrade strategy. Also use when reviewing or validating existing EKS architectures, planning networking or security, evaluating deployment models, or generating architecture diagrams. Skip for short advisory recommendations without a formal document (eks-best-practices), Internal Developer Platforms or progressive delivery (eks-platform-engineering), and GenAI/LLM workload design — GPU vs Neuron, vLLM/Ray serving, distributed training (eks-genai).
aws-samples/sample-apex-skills · ★ 37 · AI & Automation · score 73
Install: claude install-skill aws-samples/sample-apex-skills
# EKS Design Generate architecture design documents for production-ready EKS deployments. All output is structured for direct handoff to `eks-build` for code generation. ## When to Use - Designing a new EKS cluster architecture from requirements - Reviewing or validating existing EKS architecture decisions - Choosing between EKS compute options (Karpenter, MNG, Auto Mode, Fargate) - Planning EKS networking or security architecture - Evaluating EKS deployment models (Standard, Auto Mode, Outposts, Anywhere) - Optimizing EKS cost and scalability - Generating architecture documentation, ADRs, or Mermaid diagrams for EKS - Generating standalone Mermaid architecture diagrams (EKS topology, VPC layout, subnet tiers, node groups, pod networking flows, load balancer placement) - Creating design artifacts that feed into `eks-build` for implementation ## Don't Use - Generating Terraform code or Helm charts (use `eks-build`) - EKS cluster reconnaissance or discovery (use `eks-recon`) - Terraform module design or testing (use `terraform-skill`) - Detailed reference material on autoscaling, networking, security, observability, cost, reliability, or upgrades (use `eks-best-practices`) - Internal Developer Platforms, Backstage portals, golden paths, progressive delivery, or developer self-service (use `eks-platform-engineering`) - GenAI / LLM workload design — GPU vs Trainium/Inferentia selection, vLLM / Ray Serve / distributed-training architecture, ML storage (FSx for Lustre), or GPU