AWS eks documentation change
Summary
Updated migration guidance links and clarified AMI build instructions
Security assessment
Changes primarily improve documentation structure and link references without introducing new security content. Mentions of security features like IMDSv2/SELinux are existing content enhancements rather than new security disclosures.
Diff
diff --git a/eks/latest/userguide/eks-ami-deprecation-faqs.md b/eks/latest/userguide/eks-ami-deprecation-faqs.md index 78e76a811..ac0962268 100644 --- a//eks/latest/userguide/eks-ami-deprecation-faqs.md +++ b//eks/latest/userguide/eks-ami-deprecation-faqs.md @@ -15 +15 @@ AWS will end support for EKS AL2-optimized and AL2-accelerated AMIs, effective N - * AL2023 enables a secure-by-default approach with preconfigured security policies, SELinux in permissive mode, IMDSv2-only mode enabled by default, optimized boot times, and improved package management for enhanced security and performance, well-suited for infrastructure requiring significant customizations like direct OS-level access or extensive node changes. + * AL2023 enables a secure-by-default approach with preconfigured security policies, SELinux in permissive mode, IMDSv2-only mode enabled by default, optimized boot times, and improved package management for enhanced security and performance, well-suited for infrastructure requiring significant customizations like direct OS-level access or extensive node changes. To learn more, see [AL2023 FAQs](https://aws.amazon.com/linux/amazon-linux-2023/faqs/) or view our detailed migration guidance at [Upgrade from Amazon Linux 2 to Amazon Linux 2023](./al2023.html). @@ -17 +17 @@ AWS will end support for EKS AL2-optimized and AL2-accelerated AMIs, effective N - * Bottlerocket enables enhanced security, faster boot times, and a smaller attack surface for improved efficiency with its purpose-built, container-optimized design, well-suited for container-native approaches with minimal node customizations. + * Bottlerocket enables enhanced security, faster boot times, and a smaller attack surface for improved efficiency with its purpose-built, container-optimized design, well-suited for container-native approaches with minimal node customizations. To learn more, see [Bottlerocket FAQs](https://aws.amazon.com/bottlerocket/faqs/) or view our detailed migration guidance at [Create nodes with optimized Bottlerocket AMIs](./eks-optimized-ami-bottlerocket.html). @@ -22 +22 @@ AWS will end support for EKS AL2-optimized and AL2-accelerated AMIs, effective N -Alternatively, you can [Build a custom Amazon Linux AMI](./eks-ami-build-scripts.html) until the EOS date (November 26, 2025), or build a custom AMI with an Amazon Linux 2 base instance until the Amazon Linux 2 EOS date (June 30, 2026). For more information, please visit [AL2023 FAQs](https://aws.amazon.com/linux/amazon-linux-2023/faqs/), [Bottlerocket FAQs](https://aws.amazon.com/bottlerocket/faqs/) or refer to [Upgrade from Amazon Linux 2 to Amazon Linux 2023](./al2023.html) or [Create nodes with optimized Bottlerocket AMIs](./eks-optimized-ami-bottlerocket.html) documentation for detailed migration guidance. +Alternatively, you can [Build a custom EKS-optimized Amazon Linux AMI](./eks-ami-build-scripts.html) until the EOS date (November 26, 2025). Additionally, you can build a custom AMI with an Amazon Linux 2 base instance until the Amazon Linux 2 EOS date (June 30, 2026). @@ -48 +48 @@ You cannot run your full Neuron-powered applications natively on an AL2-based AM -Switching to a bare Amazon Linux 2 base instance lacks the specific optimizations, container runtime configurations, and customizations provided by the official EKS AL2-optimized and AL2-accelerated AMIs. Instead, if you must continue using an AL2-based solution, we recommend building a custom AMI using the EKS AMI recipes at [Build a custom Amazon Linux AMI](./eks-ami-build-scripts.html) or [Amazon EKS AMI Build Specification](https://github.com/awslabs/amazon-eks-ami). This ensures compatibility with your existing workloads and includes AL2 kernel updates until the Amazon Linux 2 EOS date (June 30, 2026). +Switching to a bare Amazon Linux 2 base instance lacks the specific optimizations, container runtime configurations, and customizations provided by the official EKS AL2-optimized and AL2-accelerated AMIs. Instead, if you must continue using an AL2-based solution, we recommend building a custom AMI using the EKS AMI recipes at [Build a custom EKS-optimized Amazon Linux AMI](./eks-ami-build-scripts.html) or [Amazon EKS AMI Build Specification](https://github.com/awslabs/amazon-eks-ami). This ensures compatibility with your existing workloads and includes AL2 kernel updates until the Amazon Linux 2 EOS date (June 30, 2026). @@ -60 +60 @@ When running on Amazon EKS nodes with AL2023, Java applications relying on JDK 8 - * **Build a custom AMI** : If you must continue using an AL2-based solution, you can build a custom AL2-based AMI (until November 26, 2025) using [Build a custom Amazon Linux AMI](./eks-ami-build-scripts.html) or [Amazon EKS AMI Build Specification](https://github.com/awslabs/amazon-eks-ami). For example, you can build an AL2-based v1.33 AMI (until November 26, 2025). Amazon EKS will provide AL2-based AMIs until the EKS AL2 EOS date (November 26, 2025). After the EOS date (November 26, 2025), you will need to build your own AMI. + * **Build a custom AMI** : If you must continue using an AL2-based solution, you can build a custom AL2-based AMI (until November 26, 2025) using [Build a custom EKS-optimized Amazon Linux AMI](./eks-ami-build-scripts.html) or [Amazon EKS AMI Build Specification](https://github.com/awslabs/amazon-eks-ami). For example, you can build an AL2-based v1.33 AMI (until November 26, 2025). Amazon EKS will provide AL2-based AMIs until the EKS AL2 EOS date (November 26, 2025). After the EOS date (November 26, 2025), you will need to build your own AMI.