Hi @joneszc, thanks for opening the issue, That was an amazing catch; I completely agree that there should be an optional setting in the node_group settings in our nebari-config.

I also don't see a problem with compatibility as the majority of the users would use the default AMI options by default, and this config while present will only be modified by users "looking for it", though appropriate docs will be required to guide users to avoid silly mistakes like per-zone AMIs etc..

Hello @viniciusdc

The option to specify an ami id could definitely cause some confusion to users not wanting to get into the weeds of EKS.
There is also added risk of users experiencing nodes failing to join the cluster if they are required to manually input or tamper with the /etc/eks/bootstrap.sh command. I feel it would be appropriate to hard code the bootstrap.sh command into the terraform, with proper logic/directives for triggering, and spare the user the responsibility of formulating the command and of potentially troubleshooting faulty nodes. Perhaps, down the road it would be beneficial as a separate use case to enable specific pointed overrides for arguments like --kubelet-extra-args.
I've combined testing of the custom ami option and #2603 at this fork

@viniciusdc will review this as part of the PR linked above.

This feature was introduced in #2668