HIGH

Ensure EKS cluster uses IRSA for pod permissions

Pods should use IAM Roles for Service Accounts (IRSA) instead of node-level IAM roles.

Security Impact

Node-level IAM roles grant all pods on the node the same permissions, violating least privilege.

How to Remediate

Enable OIDC provider for cluster. Create IAM roles with service account annotations.

Affected Resources

AWS::EKS::ClusterAWS::IAM::Role

Compliance Frameworks

SOC 2PCI-DSSNIST 800-53CIS EKS

How TigerGate Helps

TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all Elastic Kubernetes Service (EKS) resources across your AWS accounts every hour

  • Instant Alerts

    Get notified via Slack, email, or webhooks when this misconfiguration is detected

  • One-Click Remediation

    Fix this issue directly from the TigerGate dashboard with our guided remediation

  • Compliance Evidence

    Automatically collect audit evidence for SOC 2, PCI-DSS, NIST 800-53 compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-eks-7
Service
Elastic Kubernetes Service (EKS)
Category
Identity Management
Severity
HIGH

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related Elastic Kubernetes Service (EKS) Checks

View all checks
aws-eks-1high

Ensure EKS cluster endpoint is not publicly accessible

aws-eks-2high

Ensure EKS cluster has secrets encryption enabled

aws-eks-3medium

Ensure EKS cluster logging is enabled

aws-eks-4medium

Ensure EKS node groups use managed node groups

aws-eks-5high

Ensure EKS clusters use the latest Kubernetes version