From a09bc3062643744955e29f3a0d61ee1830e4308e Mon Sep 17 00:00:00 2001 From: Christian DiRubbio <117473198+cdirubbio@users.noreply.github.com> Date: Wed, 15 Oct 2025 09:54:04 -0400 Subject: [PATCH] [AL2 EOS Prep] Update launch-templates.adoc, NodeADM info rather than bootstrap script --- latest/ug/nodes/launch-templates.adoc | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/latest/ug/nodes/launch-templates.adoc b/latest/ug/nodes/launch-templates.adoc index 147ea554..136fea7b 100644 --- a/latest/ug/nodes/launch-templates.adoc +++ b/latest/ug/nodes/launch-templates.adoc @@ -59,13 +59,7 @@ a|*Application and OS Images (Amazon Machine Image)* under *Launch template cont * Using a custom AMI. If you specify an AMI that doesn't meet the requirements listed in <>, the node group deployment will fail. -* Want to provide user data to provide arguments to the `bootstrap.sh` file included with an Amazon EKS optimized AMI. You can enable your instances to assign a significantly higher number of IP addresses to Pods, assign IP addresses to Pods from a different CIDR block than the instance's, or deploy a private cluster without outbound internet access. For more information, see the following topics: - -+ -** <> -** <> -** <> -** <> +* Want to provide additional arguments to the NodeConfig specification of an Amazon EKS optimized AMI. For more information, see https://awslabs.github.io/amazon-eks-ami/nodeadm/doc/api/#nodeconfig[NodeConfig API reference] and https://awslabs.github.io/amazon-eks-ami/nodeadm/doc/examples/[NodeConfig examples]. |*Disk size* under *Node group compute configuration* on *Set compute and scaling configuration* page – Console displays *Specified in launch template*.