← All posts
SecurityEKSDevSecOps

A practical checklist for hardening EKS

IAM roles for service accounts, network policies, image scanning and the rest of my go-to list.

Security on Kubernetes is a stack of small, unglamorous defaults. This is the checklist I run through on every new EKS cluster.

Identity

  • IAM Roles for Service Accounts instead of node-wide permissions
  • SSO-backed access for humans, mapped to Kubernetes RBAC groups
  • No long-lived kubeconfigs on laptops

Network

  • Private API endpoint where possible
  • Default-deny network policies per namespace
  • TLS everywhere, with certificates managed automatically

Supply chain

  • Scan images in CI and block critical CVEs
  • Pin base images and rebuild weekly
  • Run as non-root with a read-only root filesystem

None of these are exciting on their own. Together they close most of the doors attackers actually walk through.