EKS Platform Engineering

Guidance for designing and building an Internal Developer Platform (IDP) on Amazon EKS. This skill is opinionated: it teaches one proven, integrated golden-path stack end to end rather than cataloguing every option. The reference architecture and tool choices below are the recommended default; deviate only with a reason.

This is the "how do I build a platform that other teams self-serve from" skill. For "how do I run a single EKS cluster well" (compute, networking, security, cost, upgrades), use eks-best-practices instead.

When to Use This Skill

Activate when the user wants to:

• Build or design an Internal Developer Platform / developer self-service on EKS
• Stand up or wire together a developer portal (Backstage), GitOps (ArgoCD/Argo Workflows), progressive delivery (Argo Rollouts), or promotion (Kargo)
• Define golden paths — standardized, paved ways for app teams to ship
• Abstract AWS resources behind Kubernetes (ACK, kro) or applications behind OAM/KubeVela
• Enable self-service environment or resource provisioning
• Measure platform success (DORA metrics)
• Use GenAI (Amazon Q Developer) to author platform templates/manifests
• Extend the platform to AI/ML or data-engineering workloads