AWS Enables Per-Pod ECR Image Pull Controls on EKS to Harden Multi-Tenant Isolation

AWS has detailed a new architecture for Amazon Elastic Kubernetes Service (Amazon EKS) clusters running version 1.35 and above, enabling fine-grained, per-pod image pull permissions for Amazon Elastic Container Registry (Amazon ECR). The approach leverages Kubernetes Enhancement Proposal (KEP) 4412—which introduces per-pod credential support for kubelet image pulls—alongside the AWS ecr-credential-provider binary and standard ECR repository resource-based policies. Historically, Amazon EKS has delegated container image pulling to the underlying worker node's IAM role. Because every workload co-located on a shared EC2 instance inherits that instance's credential context during image retrieval, any pod could theoretically request and pull container images from any ECR repository accessible to the node role. For enterprise platform engineers running consolidated multi-tenant clusters, this broad access represented a structural compliance and security hurdle. Teams frequently resorted to maintaining segregated node groups, deploying heavy admission webhooks, or implementing third-party policy engines like OPA/Gatekeeper simply to enforce namespace-level image restrictions. This release fits into the broader cloud-native movement toward least-privilege workload identity and zero-trust orchestration. Kubernetes has progressively replaced coarse-grained node privileges with granular pod identities—exemplified by Pod Certificates, projected service account tokens, and IAM Roles for Service Accounts (IRSA / EKS Pod Identities). Extending scoped identity directly into the kubelet's image acquisition phase eliminates one of the last major out-of-band operational vectors where node-level privileges bypassed Kubernetes tenant boundaries. In practice, platform operators can now provision a dedicated IAM pull role per tenant team, anchored to their Kubernetes namespace via OpenID Connect (OIDC) federation. By pairing pod service account annotations with ECR repository deny policies that check caller identity, cross-tenant image pulling is rejected at the registry layer. Platform architects should evaluate this pattern on EKS 1.35+ clusters to simplify node consolidation, streamline compliance auditing, and phase out brittle mutating webhooks historically used to inspect image provenance.