Skip to content

Update warning on EKS Local Clusters in AWS Outposts AMI Compatibility #1127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 6, 2025
Merged

Update warning on EKS Local Clusters in AWS Outposts AMI Compatibility #1127

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
12e37d0
AL2-only compatibility for EKS Local Clusters in Outposts
alegermer Oct 3, 2025
3938019
Apply suggestions from code review PR #1127
fincd-aws Oct 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions latest/ug/outposts/eks-outposts-self-managed-nodes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 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 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.

* An existing Outpost. For more information, see link:outposts/latest/userguide/what-is-outposts.html[What is {aws} Outposts,type="documentation"].
Expand Down
2 changes: 1 addition & 1 deletion latest/ug/outposts/eks-outposts-troubleshooting.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <<eks-optimized-ami,Create nodes with optimized Amazon Linux AMIs>> Amazon EKS optimized Amazon Linux.
** 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 <<eks-outposts-self-managed-nodes,Create Amazon Linux nodes on {aws} Outposts>>.
** 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 <<aws-auth-configmap>> .
* 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.
Expand Down