AWS Security ChangesHomeSearch

AWS IAM medium security documentation change

Service: IAM · 2026-03-19 · Security-related medium

File: IAM/latest/UserGuide/id_root-user-privileged-task.md

Summary

Updated documentation to clarify that centralized root access requires IAM user/role with sts:AssumeRoot permission, and explicitly states that root user credentials cannot call sts:AssumeRoot.

Security assessment

This change clarifies important security controls around root access delegation. By explicitly stating that root user credentials cannot call sts:AssumeRoot, it prevents potential security misconfigurations where users might incorrectly use root credentials for this operation. This addresses a potential security issue where improper use of root credentials could lead to privilege escalation or credential exposure.

Diff

diff --git a/IAM/latest/UserGuide/id_root-user-privileged-task.md b/IAM/latest/UserGuide/id_root-user-privileged-task.md
index cadac2a96..2a54e3a11 100644
--- a//IAM/latest/UserGuide/id_root-user-privileged-task.md
+++ b//IAM/latest/UserGuide/id_root-user-privileged-task.md
@@ -9 +9 @@ PrerequisitesTaking a privileged action on a member account (console)Taking a pr
-The AWS Organizations management account or a delegated administrator account for IAM can perform some root user tasks on member accounts using short-term root access. These tasks can only be performed when you sign in as the root user of an account. Short-term privileged sessions give you temporary credentials that you can scope to take privileged actions on a member account in your organization.
+The AWS Organizations management account or a delegated administrator account for IAM can perform some privileged tasks on member accounts that would otherwise require root user credentials. With centralized root access, these tasks are performed through short-term privileged sessions. These sessions provide temporary credentials scoped to specific privileged actions, without requiring root user sign-in on the member account.
@@ -15 +15 @@ Once you launch a privileged session, you can delete a misconfigured Amazon S3 b
-To use centralized root access, you must sign in via a management account or a delegated administrator account and must have the `sts:AssumeRoot` permission explicitly granted.
+To use centralized root access, you must sign in via a management account or a delegated administrator account as an IAM user or role with the `sts:AssumeRoot` permission explicitly granted. You cannot use root user credentials to call `sts:AssumeRoot`.