AmazonEKSWorkerNodePolicy

ReaderAWS managedActivePermissions reviewedShow on map Compare

Summary

This policy allows Amazon EKS worker nodes to connect to Amazon EKS Clusters.

Permissions imported from the AWS Managed Policy Reference Guide; other sections pending editorial review.

Identity

ARN: arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy
Default version: v3
Created: 2018-05-27
Last edited: 2023-11-27
Services: ec2, eks, eks-auth

Control-plane actions (10)

By access level: 8 List, 2 Read.

Control-plane actions by service
Service	Granted	Access levels and limits	Granted by
EC2	8 of 834	8 List; 0 restricted, 0 conditional	ec2:DescribeInstanceTypes, ec2:DescribeInstances, ec2:DescribeRouteTables, ec2:DescribeSecurityGroups, ec2:DescribeSubnets, ec2:DescribeVolumes, ec2:DescribeVolumesModifications, ec2:DescribeVpcs
EKS	1 of 74	1 Read; 0 restricted, 0 conditional	eks:DescribeCluster
EKS Auth	All 1 actions (see the EKS Auth page)	1 Read; 0 restricted, 0 conditional	eks-auth:AssumeRoleForPodIdentity

EC2: 8 actions

ec2:DescribeInstanceTypes (List)
ec2:DescribeInstances (List)
ec2:DescribeRouteTables (List)
ec2:DescribeSecurityGroups (List)
ec2:DescribeSubnets (List)
ec2:DescribeVolumes (List)
ec2:DescribeVolumesModifications (List)
ec2:DescribeVpcs (List)

EKS: 1 actions

eks:DescribeCluster (Read)

Data-plane actions (0)

By access level: none.

This policy grants no actions in this plane.

Excluded and conditional actions

No patterns are excluded by NotAction or Deny statements.

Resource scope and attachment

Resource scope across granted actions: all-resources.

Can be attached: Yes, to users, groups and roles.

Why this tier

Grants only List and Read actions.

Guidance

Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.

Same service

Same domain

Frequently asked questions

Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "WorkerNodePermissions",
      "Effect": "Allow",
      "Action": [
        "ec2:DescribeInstances",
        "ec2:DescribeInstanceTypes",
        "ec2:DescribeRouteTables",
        "ec2:DescribeSecurityGroups",
        "ec2:DescribeSubnets",
        "ec2:DescribeVolumes",
        "ec2:DescribeVolumesModifications",
        "ec2:DescribeVpcs",
        "eks:DescribeCluster",
        "eks-auth:AssumeRoleForPodIdentity"
      ],
      "Resource": "*"
    }
  ]
}

Version history

Current version v3, edited by AWS on 2023-11-27. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.

Attach snippets

AWS CLI

aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy

CloudFormation

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy

Terraform

resource "aws_iam_role_policy_attachment" "amazoneksworkernodepolicy" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("AmazonEKSWorkerNodePolicy"),
);

Sources

Pending editorial review. No editorial sources are listed yet.