[Feature] Support AMIs specified by SSM Parameters

[cbgbt]

What feature/behavior/change do you want?

AWS Autoscaling has added support for identifying AMIs in Launch Templates via SSM parameters: https://docs.aws.amazon.com/autoscaling/ec2/userguide/using-systems-manager-parameters.html

When creating a self-managed nodegroup, it would be excellent if an SSM parameter could be specified instead of an AMI ID.

Why do you want this feature?

This feature would allow eksctl users to make a choice for new nodes to be launched with the latest version of a given AMI. This could be used e.g. to expedite security patching: referring to the official SSM parameters for an AMI would ensure new nodes always have the latest patches at launch.

[github-actions]

Hello cbgbt 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.

[kitsirota]

+1
We are have to modify launch templates manually after deploying them with eksctl.

If we could define which param store value of the latest AMI that the ASG should use, then we can ensure we are able to use the bottlerocket update operator in conjunction with kubernetes autoscaler.

Reference ticket: bottlerocket-os/bottlerocket-update-operator#45 (comment)

Can we please re-open this issue?

[aledbf]

I am also interested in this feature. The change to enable this feature looked simple, but the MixedInstancesPolicy creates a limitation? (I am using managedGroups)