dhi.io/aws-eks-pod-identity-agent
AWS EKS Pod Identity Agent
The AWS EKS Pod Identity Agent runs on Amazon EKS nodes and exchanges Kubernetes service account tokens for temporary AWS IAM credentials, providing pods with IAM roles without using IRSA or instance profiles.
pushed 1 day ago
linux/amd64, linux/arm64
20.94 MB
for linux/amd64
88
for linux/amd64
Active support
-
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About AWS EKS Pod Identity Agent
The AWS EKS Pod Identity Agent is a Kubernetes node agent that delivers temporary AWS IAM credentials to pods running on Amazon EKS clusters. It exchanges projected Kubernetes service account tokens for short-lived AWS credentials by calling the EKS Auth API, then serves those credentials to pods via a local credential proxy.
The agent runs as a DaemonSet on each EKS node and exposes a local HTTP endpoint that the AWS SDKs and CLI inside workload pods can use to obtain credentials. The Pod Identity association mapping (which IAM role each service account maps to) is configured in EKS rather than annotated on the service account, which simplifies cross-account access and removes the need for the OIDC provider configuration required by IRSA.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
Kubernetes® is a registered trademark of The Linux Foundation. Amazon Web Services, AWS, EKS, and the AWS logo are trademarks of Amazon.com, Inc. or its affiliates. All rights in these marks are reserved to their respective owners. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.