eks-platform-engineeringlisted

Use whenever someone is designing or building an Internal Developer Platform (IDP) or doing platform engineering on Amazon EKS — phrased as "build a developer platform", "self-service for developers", "golden paths", "IDP", or "set up Backstage / ArgoCD / Kargo". Covers the opinionated platform stack — developer portal (Backstage), GitOps delivery (ArgoCD, Argo Workflows), progressive delivery (Argo Rollouts) and multi-stage promotion (Kargo), infrastructure abstraction (ACK, kro), the developer-facing app abstraction (Backstage templates + kro, or KubeVela/OAM), self-service provisioning, hub-and-spoke topology with the GitOps Bridge, identity/SSO (Keycloak, Pod Identity), measuring success (DORA, Apache DevLake), GenAI-assisted platform engineering (Kiro), and golden paths for AI/ML and data. Trigger even if "platform engineering" is never said. Skip for single-cluster EKS architecture or cost/ops tuning with no platform angle (use eks-best-practices); for standalone Terraform use terraform-skill.
aws-samples/sample-apex-skills · ★ 37 · DevOps & Infrastructure · score 73

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

# 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 a developer-facing model (Backstage templates + kro, or OAM/KubeVela) - Enable self-service environment or resource provisioning - Measure platform success (DORA metrics) - Use GenAI (Kiro) to author platform templates/manifests - Extend the platform to AI/ML or data-engineering workloads **Don't use this skill for:** - Single-cluster EKS architecture, sizing, cost, or upgrade decisions with no self-service/platform angle → `eks-best-practices` - Standalone Terraform/OpenTofu module au