AWS eks documentation change

Service: eks · 2026-05-16 · Documentation low

File: eks/latest/userguide/argocd-permissions.md

Summary

Corrected field name from 'rbacRoleMapping' to 'rbacRoleMappings' in multiple locations, updated IAM role ARN placeholder, and strengthened token handling warning.

Security assessment

Field name correction fixes configuration accuracy but isn't security-related. The token warning change ('Don't' to 'Do not') reinforces existing security advice but doesn't introduce new security documentation.

Diff

diff --git a/eks/latest/userguide/argocd-permissions.md b/eks/latest/userguide/argocd-permissions.md
index 91cff0896..354df4b62 100644
--- a//eks/latest/userguide/argocd-permissions.md
+++ b//eks/latest/userguide/argocd-permissions.md
@@ -159 +159 @@ Map AWS Identity Center users and groups to Argo CD roles when creating or updat
-      "rbacRoleMapping": {
+      "rbacRoleMappings": {
@@ -182 +182 @@ EKS Capabilities integration with AWS Identity Center supports up to 1,000 ident
-      --role-arn "arn:aws:iam::[.replaceable]111122223333:role/[.replaceable]`EKSCapabilityRole`" \
+      --role-arn "arn:aws:iam::111122223333:role/EKSCapabilityRole" \
@@ -215 +215 @@ The admin account is designed for initial setup and administrative tasks like re
-  * Don’t commit account tokens to version control
+  * Do not commit account tokens to version control
@@ -428 +428 @@ Use Identity Center group IDs (not group names) in the `groups` field. You can a
-      "rbacRoleMapping": {
+      "rbacRoleMappings": {
@@ -439 +439 @@ ADMIN users can see and manage all project-scoped resources without additional c
-      "rbacRoleMapping": {
+      "rbacRoleMappings": {
@@ -468 +468 @@ ADMIN users can see and manage all project-scoped resources without additional c
-      "rbacRoleMapping": {
+      "rbacRoleMappings": {