Implement per-pod image pull permissions with ECR repository policies on Amazon EKS
AWS describes a walkthrough for scoping Amazon ECR image pull permissions to individual Kubernetes pods on Amazon EKS. The approach uses KEP 4412 per-pod credential support in kubelet, with the ecr-credential-provider assuming a team IAM role through a service account annotation and ECR repository policies enforcing access. The post states the feature needs Kubernetes 1.34 or later, with full support on EKS v1.35 or later.
What changes for platform teams
Platform teams on multi-tenant EKS can give each namespace its own ECR pull role instead of relying on the shared node role, but they must create a ClusterRole and ClusterRoleBinding for the sts.amazonaws.com audience before nodes join, and must update node credential provider configuration. Pods without the annotation fall back to the node role.
Read the original at AWS Containers Blog ↗
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules