amazon-eks-pod-identity-webhook

Amazon EKS Pod Identity Webhook is a Kubernetes mutating admission webhook that injects AWS IAM (Identity and Access Management) Roles for Service Accounts…

  • Infrastructure
  • Security
  • Tools & Utilities
Amazon EKS Pod Identity Webhook is a Kubernetes mutating admission webhook that injects AWS IAM (Identity and Access Management) 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.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

69/100 Good

Maintained
91last commit 10 days ago
Popular
57692 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
76no serious findings, 3 minor, CI, tests, OpenSSF Scorecard 6.7/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
692
Open issues
110
Last commit
2026-11-11
Latest release
v0.6.19
License
Apache-2.0
Activity
declining

Checked 3 days ago - source: GitHub (aws/amazon-eks-pod-identity-webhook)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Use --in-cluster=false (deprecated flag) After v0.3.0 the --in-cluster=true flag no longer works and is deprecated. Configure the webhook with --in-cluster=false and manage the cluster certificate with cert-manager or another external certificate provisioning system, since certificates using the legacy-unknown signer are no longer signed via the v1 certificates API. source

Fetched 42 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can the webhook be deployed in a self-managed Kubernetes cluster?

Yes. It can be deployed in self-managed Kubernetes environments with proper configuration, even though it is designed for Amazon EKS.

Should I remove the webhook after an EKS cluster upgrade?

Not without verification. One report says IAM roles stopped working after removing it following a cluster upgrade, and the cluster may not manage the webhook automatically.

How do I install and verify the webhook?

Use the provided configuration files for installation. The installation guide covers prerequisites, installation steps, and verification procedures.

How can self-hosted Bitbucket runners on EKS be configured to access AWS resources?

Configure them with autoscaling and Pod Identity Agent authentication so pipelines can assume IAM roles for access to AWS resources such as ECR.

Does EKS Pod Identity provide isolated credentials for pods?

Yes. It grants pods access to AWS services with least privilege access, credential isolation, and auditability.

Answers sourced from community.atlassian.com, deepwiki.com, deepwiki.com, docs.aws.amazon.com, www.reddit.com

Community

Collected 48 days ago - public community threads