dhi.io/amazon-eks-pod-identity-webhook
Amazon EKS Pod Identity Webhook
The Amazon EKS Pod Identity Webhook is a Kubernetes mutating admission webhook that injects AWS IAM Roles for Service Accounts (IRSA) credentials into pods, letting workloads assume an IAM role via a projected service account token instead of long-lived credentials.
pushed 1 day ago
linux/amd64, linux/arm64
40.69 MB
for linux/amd64
151
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 Amazon EKS Pod Identity Webhook
The Amazon EKS Pod Identity Webhook is a Kubernetes mutating admission webhook that implements IAM Roles for Service
Accounts (IRSA). It watches for pods whose service account is annotated with an IAM role ARN and injects the
AWS_ROLE_ARN and AWS_WEB_IDENTITY_TOKEN_FILE environment variables, along with a projected service account token
volume, so AWS SDKs inside the pod can assume that role without long-lived credentials.
It typically runs as a Deployment inside the cluster and is registered with the Kubernetes API server via a
MutatingWebhookConfiguration, which calls the webhook's /mutate endpoint for every pod creation.
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.