Self-managed node updates - Amazon EKS
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Self-managed node updates

When a new Amazon EKS optimized AMI is released, consider replacing the nodes in your self-managed node group with the new AMI. Likewise, if you have updated the Kubernetes version for your Amazon EKS cluster, update the nodes to use nodes with the same Kubernetes version.


This topic covers node updates for self-managed nodes. If you are using Managed node groups, see Updating a managed node group.

There are two basic ways to update self-managed node groups in your clusters to use a new AMI:

Migrating to a new node group

Create a new node group and migrate your Pods to that group. Migrating to a new node group is more graceful than simply updating the AMI ID in an existing Amazon CloudFormation stack. This is because the migration process taints the old node group as NoSchedule and drains the nodes after a new stack is ready to accept the existing Pod workload.

Updating an existing self-managed node group

Update the Amazon CloudFormation stack for an existing node group to use the new AMI. This method isn't supported for node groups that were created with eksctl.