AWS Security ChangesHomeSearch

AWS eks documentation change

Service: eks · 2026-02-28 · Documentation low

File: eks/latest/eksctl/fargate.md

Summary

Updated terminology from 'whitelisted' to 'allowed' namespaces

Security assessment

Change updates language to modern standards but doesn't alter security functionality or address vulnerabilities

Diff

diff --git a/eks/latest/eksctl/fargate.md b/eks/latest/eksctl/fargate.md
index a376d1c20..0838a9d28 100644
--- a//eks/latest/eksctl/fargate.md
+++ b//eks/latest/eksctl/fargate.md
@@ -162 +162 @@ The following config file declares an EKS cluster with both a nodegroup composed
-Each selector entry has up to two components, namespace and a list of key-value pairs. Only the namespace component is required to create a selector entry. All rules (namespaces, key value pairs) must apply to a pod to match a selector entry. A pod only needs to match one selector entry to run on the profile. Any pod that matches all the conditions in a selector field would be scheduled to be run on Fargate. Any pods not matching either the whitelisted Namespaces but where the user manually set the scheduler: fargate-scheduler filed would be stuck in a Pending state, as they were not authorized to run on Fargate.
+Each selector entry has up to two components, namespace and a list of key-value pairs. Only the namespace component is required to create a selector entry. All rules (namespaces, key value pairs) must apply to a pod to match a selector entry. A pod only needs to match one selector entry to run on the profile. Any pod that matches all the conditions in a selector field would be scheduled to be run on Fargate. Any pods not matching either the whitelisted Namespaces but where the user manually set the scheduler: fargate-scheduler field would be stuck in a Pending state, as they were not authorized to run on Fargate.
@@ -206 +206 @@ This operation is only supported on clusters that run on the EKS platform versio
-If the existing was created with a version of `eksctl` prior to 0.11.0, you will need to run `eksctl upgrade cluster` before creating the Fargate profile.
+If the existing cluster was created with a version of `eksctl` prior to 0.11.0, you will need to run `eksctl upgrade cluster` before creating the Fargate profile.