From 12e37d08d757af8ca62f4a8587834f622c706346 Mon Sep 17 00:00:00 2001 From: Alessandro Germer Date: Fri, 3 Oct 2025 13:01:25 -0700 Subject: [PATCH 1/2] AL2-only compatibility for EKS Local Clusters in Outposts Making it explicit that AL2023 is currently incompatible to aid troubleshooting until the planned support is released. --- .../ug/outposts/eks-outposts-self-managed-nodes.adoc | 11 +++++++++++ latest/ug/outposts/eks-outposts-troubleshooting.adoc | 2 +- 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc b/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc index f298a359..d47a0743 100644 --- a/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc +++ b/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc @@ -10,6 +10,17 @@ include::../attributes.txt[] Learn how to launch Auto Scaling groups of Amazon Linux nodes on an Outpost that register with your Amazon EKS cluster. The cluster can be on the {aws} Cloud or on an Outpost. -- +[IMPORTANT] +==== +Amazon EKS Local Clusters on Outposts currently supports only nodes created from Amazon EKS-optimized Amazon Linux 2 AMIs, which include: + +* Standard Amazon Linux 2 (`amazon-linux-2`) +* GPU-enabled Amazon Linux 2 (`amazon-linux-2-gpu`) +* Arm64-based Amazon Linux 2 (`amazon-linux-2-arm64`) + +Nodes based on Amazon Linux 2023 (`AL2023`) AMIs are not currently supported and will fail to join the cluster. Support for `AL2023`-based nodes is planned for a future release, and this documentation will be updated when the feature becomes available. +==== + This topic describes how you can launch Auto Scaling groups of Amazon Linux nodes on an Outpost that register with your Amazon EKS cluster. The cluster can be on the {aws} Cloud or on an Outpost. * An existing Outpost. For more information, see link:outposts/latest/userguide/what-is-outposts.html[What is {aws} Outposts,type="documentation"]. diff --git a/latest/ug/outposts/eks-outposts-troubleshooting.adoc b/latest/ug/outposts/eks-outposts-troubleshooting.adoc index 287d6622..5bd4109d 100644 --- a/latest/ug/outposts/eks-outposts-troubleshooting.adoc +++ b/latest/ug/outposts/eks-outposts-troubleshooting.adoc @@ -271,7 +271,7 @@ The most common issues are the following: * AMI issues: + -** You're using an unsupported AMI. You must use https://github.com/awslabs/amazon-eks-ami/releases/tag/v20220620[v20220620] or later for the <> Amazon EKS optimized Amazon Linux. +** You may be using an incompatible AMI. Only Amazon EKS optimized Amazon Linux 2 AMIs are currently supported (`amazon-linux-2`,`amazon-linux-2-gpu`, `amazon-linux-2-arm64`), attempting to join `AL2023`-based AMIs to EKS LocalClusters on {aws} Outposts will fail until the compatibility is added in a future release. See <>) ** If you used an {aws} CloudFormation template to create your nodes, make sure it wasn't using an unsupported AMI. * Missing the {aws} IAM Authenticator `ConfigMap` – If it's missing, you must create it. For more information, see <> . * The wrong security group is used – Make sure to use `eks-cluster-sg-[.replaceable]``cluster-name``-[.replaceable]``uniqueid``` for your worker nodes' security group. The selected security group is changed by {aws} CloudFormation to allow a new security group each time the stack is used. From 393801971f4c94174c542cd3ec02a98f97867584 Mon Sep 17 00:00:00 2001 From: Donovan Date: Mon, 6 Oct 2025 11:50:40 -0700 Subject: [PATCH 2/2] Apply suggestions from code review PR #1127 --- latest/ug/outposts/eks-outposts-self-managed-nodes.adoc | 4 ++-- latest/ug/outposts/eks-outposts-troubleshooting.adoc | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc b/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc index d47a0743..40ea99fc 100644 --- a/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc +++ b/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc @@ -12,13 +12,13 @@ Learn how to launch Auto Scaling groups of Amazon Linux nodes on an Outpost that [IMPORTANT] ==== -Amazon EKS Local Clusters on Outposts currently supports only nodes created from Amazon EKS-optimized Amazon Linux 2 AMIs, which include: +Amazon EKS Local Clusters on Outposts only supports nodes created from the following Amazon EKS-optimized Amazon Linux 2 AMIs: * Standard Amazon Linux 2 (`amazon-linux-2`) * GPU-enabled Amazon Linux 2 (`amazon-linux-2-gpu`) * Arm64-based Amazon Linux 2 (`amazon-linux-2-arm64`) -Nodes based on Amazon Linux 2023 (`AL2023`) AMIs are not currently supported and will fail to join the cluster. Support for `AL2023`-based nodes is planned for a future release, and this documentation will be updated when the feature becomes available. +Nodes on Local Clusters that run Amazon Linux 2023 (AL2023) AMIs aren't supported and fail to join the cluster. ==== This topic describes how you can launch Auto Scaling groups of Amazon Linux nodes on an Outpost that register with your Amazon EKS cluster. The cluster can be on the {aws} Cloud or on an Outpost. diff --git a/latest/ug/outposts/eks-outposts-troubleshooting.adoc b/latest/ug/outposts/eks-outposts-troubleshooting.adoc index 5bd4109d..9940b6fd 100644 --- a/latest/ug/outposts/eks-outposts-troubleshooting.adoc +++ b/latest/ug/outposts/eks-outposts-troubleshooting.adoc @@ -271,7 +271,7 @@ The most common issues are the following: * AMI issues: + -** You may be using an incompatible AMI. Only Amazon EKS optimized Amazon Linux 2 AMIs are currently supported (`amazon-linux-2`,`amazon-linux-2-gpu`, `amazon-linux-2-arm64`), attempting to join `AL2023`-based AMIs to EKS LocalClusters on {aws} Outposts will fail until the compatibility is added in a future release. See <>) +** You're using an incompatible AMI. Only Amazon EKS optimized Amazon Linux 2 AMIs are supported (`amazon-linux-2`,`amazon-linux-2-gpu`, `amazon-linux-2-arm64`). If you attempt to join AL2023 nodes to EKS LocalClusters on {aws} Outposts, the nodes fail to join the cluster. For more information, see <>. ** If you used an {aws} CloudFormation template to create your nodes, make sure it wasn't using an unsupported AMI. * Missing the {aws} IAM Authenticator `ConfigMap` – If it's missing, you must create it. For more information, see <> . * The wrong security group is used – Make sure to use `eks-cluster-sg-[.replaceable]``cluster-name``-[.replaceable]``uniqueid``` for your worker nodes' security group. The selected security group is changed by {aws} CloudFormation to allow a new security group each time the stack is used.