Does AWS charge AWS EKS node group when upgrading by customizing the AMI in the launch template?

Question

I am upgrading my EKS cluster from version 1.28 to 1.29, the way I use it is as follows:

- Go to nodegroup -> Autoscaling group -> LaunchTemplate -> modify AMI to imge "amazon-eks-arm64-node-1.29-v20240904". After modifying, scale up so that the newly created instance receives the new image, then scale down to terminate the instance with the old version.

- When I kubectl get nodes, the node has successfully upgraded and received the new image version, but when I access the EKS dashboard console, the nodegroup still displays the old version 1.28 and the "upgrade now" button.

My question is, if the old version 1.28 is still displayed on AWS's EKS console even though the nodes in the nodegroup have upgraded to version 1.29 as custom lauch template, will AWS charge a fee if the old standard support version expires?

re:Post Agent · Accepted Answer

Based on the information provided, AWS does not charge additional fees for EKS node groups solely based on the version displayed in the EKS console. The actual version running on the nodes is what matters for support and functionality.

In your scenario, you've manually updated the AMI in the launch template to use the newer 1.29 version. This approach effectively upgrades the nodes, as evidenced by the `kubectl get nodes` command showing the new version. However, the EKS console may not automatically reflect these manual changes.

The discrepancy you're seeing between the actual node version and what's displayed in the EKS console is likely due to the console not being aware of the manual AMI update in the launch template. The "upgrade now" button and the displayed version 1.28 are based on the EKS service's understanding of the node group's configuration, which hasn't been updated through the EKS API.

Regarding potential charges, AWS typically bases its support and pricing on the actual resources and versions in use, not on what's displayed in the console. Since your nodes are running the newer 1.29 version, you should be operating within the supported version range.

However, it's important to note that this manual update method, while functional, may lead to inconsistencies between the EKS service's understanding of your node group and its actual state. To ensure full compatibility and avoid potential issues, it's generally recommended to use EKS-provided upgrade mechanisms, such as the `UpdateNodegroupVersion` API or the corresponding CLI/console options, which would update both the nodes and the EKS service's metadata about your node group.

If you're concerned about potential charges or support implications, it would be advisable to contact AWS support for clarification on your specific account and setup. They can provide the most accurate information regarding your account's billing and support status.  
**Sources**  
[UpdateNodegroupVersion - Amazon EKS](https://docs.aws.amazon.com/eks/latest/APIReference/API_UpdateNodegroupVersion.html)  
[Update a managed node group for your cluster - Amazon EKS](https://docs.aws.amazon.com/eks/latest/userguide/update-managed-node-group.html)  
[Customize managed nodes with launch templates - Amazon EKS](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html)

Does AWS charge AWS EKS node group when upgrading by customizing the AMI in the launch template?

Relevant content