Skip to main content
deleted 445 characters in body
Source Link
Recoba20
  • 662
  • 3
  • 4

This is actually pretty well described in the docsdocs.

Before you create worker nodes, you must create an IAM role with the following IAM policies:

AmazonEKSWorkerNodePolicy

AmazonEKS_CNI_Policy

AmazonEC2ContainerRegistryReadOnly

Also you need to make sure that this role could be assumed by EKS.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "ec2.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

Edit:

On the time of answering this question, AWS was not providing a Managed Node Group, there the policies are encapsulated for you in a role coming with the Node Group by default.

https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html

This is actually pretty well described in the docs.

Before you create worker nodes, you must create an IAM role with the following IAM policies:

AmazonEKSWorkerNodePolicy

AmazonEKS_CNI_Policy

AmazonEC2ContainerRegistryReadOnly

Also you need to make sure that this role could be assumed by EKS.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "ec2.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

Edit:

On the time of answering this question, AWS was not providing a Managed Node Group, there the policies are encapsulated for you in a role coming with the Node Group by default.

https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html

This is actually pretty well described in the docs.

Before you create worker nodes, you must create an IAM role with the following IAM policies:

AmazonEKSWorkerNodePolicy

AmazonEKS_CNI_Policy

AmazonEC2ContainerRegistryReadOnly

Also you need to make sure that this role could be assumed by EKS.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "ec2.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}
added 348 characters in body
Source Link
Recoba20
  • 662
  • 3
  • 4

This is actually pretty well described in the docs.

Before you create worker nodes, you must create an IAM role with the following IAM policies:

AmazonEKSWorkerNodePolicy

AmazonEKS_CNI_Policy

AmazonEC2ContainerRegistryReadOnly

Also you need to make sure that this role could be assumed by EKS.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "ec2.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

Edit:

On the time of answering this question, AWS was not providing a Managed Node Group, there the policies are encapsulated for you in a role coming with the Node Group by default.

https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html

This is actually pretty well described in the docs.

Before you create worker nodes, you must create an IAM role with the following IAM policies:

AmazonEKSWorkerNodePolicy

AmazonEKS_CNI_Policy

AmazonEC2ContainerRegistryReadOnly

Also you need to make sure that this role could be assumed by EKS.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "ec2.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

This is actually pretty well described in the docs.

Before you create worker nodes, you must create an IAM role with the following IAM policies:

AmazonEKSWorkerNodePolicy

AmazonEKS_CNI_Policy

AmazonEC2ContainerRegistryReadOnly

Also you need to make sure that this role could be assumed by EKS.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "ec2.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

Edit:

On the time of answering this question, AWS was not providing a Managed Node Group, there the policies are encapsulated for you in a role coming with the Node Group by default.

https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html

Source Link
Recoba20
  • 662
  • 3
  • 4

This is actually pretty well described in the docs.

Before you create worker nodes, you must create an IAM role with the following IAM policies:

AmazonEKSWorkerNodePolicy

AmazonEKS_CNI_Policy

AmazonEC2ContainerRegistryReadOnly

Also you need to make sure that this role could be assumed by EKS.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "ec2.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}