Course contentsShow
← Cloud and Infrastructure
Lesson 1467 of 2,98930. Managed Kubernetes ServicesFree lesson

EKS IAM Authentication

How aws-auth ConfigMap maps IAM roles to Kubernetes RBAC groups for cluster access.

EKS IAM Authentication

You'll learn: How Amazon EKS uses the aws-auth ConfigMap to bridge AWS IAM identities with Kubernetes RBAC permissions.

The Problem: Two Identity Systems

EKS clusters face a unique challenge: AWS uses IAM for authentication, while Kubernetes uses RBAC for authorization. When an AWS user or role tries to access your cluster, EKS needs to translate that IAM identity into Kubernetes permissions.

The aws-auth ConfigMap Solution

The aws-auth ConfigMap (located in the kube-system namespace) acts as a translation table. It maps IAM roles and users to Kubernetes RBAC groups, creating a bridge between AWS and Kubernetes identity systems.

Think of it like an airport customs checkpoint: your passport (IAM identity) gets checked and translated into a visitor badge (Kubernetes group) that determines where you can go inside the country (cluster permissions).

How It Works

When you authenticate to EKS using AWS credentials, the process flows like this:

  1. You present your IAM credentials (user or role)
  2. EKS checks the aws-auth ConfigMap for a matching entry
  3. If found, EKS assigns you to specified Kubernetes groups
  4. Those groups have RBAC Roles/ClusterRoles bound to them
  5. You now have Kubernetes permissions based on those bindings

Common Mappings

The aws-auth ConfigMap typically contains:

  • mapRoles: Maps IAM roles → Kubernetes groups (common for node groups and service accounts)
  • mapUsers: Maps specific IAM users → Kubernetes groups (for individual developer access)

For example, your node group's IAM role gets mapped to the system:bootstrappers and system:nodes groups, giving worker nodes the permissions they need to join the cluster.

Key Takeaway: The aws-auth ConfigMap is EKS's critical integration point—it translates AWS IAM identities into Kubernetes RBAC groups, enabling AWS users and roles to access your cluster with appropriate permissions.