AWS IAM documentation change
Summary
Simplified terminology from 'federated user session' to 'federated session' in permission denial explanation
Security assessment
Change reduces redundancy in terminology ('user' removed from 'federated user session') without altering security meaning. No evidence of security vulnerability being addressed or new security documentation being added.
Diff
diff --git a/IAM/latest/UserGuide/id_credentials_temp_control-access_disable-perms.md b/IAM/latest/UserGuide/id_credentials_temp_control-access_disable-perms.md index d54f80d8f..cf679857d 100644 --- a//IAM/latest/UserGuide/id_credentials_temp_control-access_disable-perms.md +++ b//IAM/latest/UserGuide/id_credentials_temp_control-access_disable-perms.md @@ -197 +197 @@ The caller-specified role session name, which is part of the unique identifier f - * `account-id:<federated-user-caller-specified-name>` represents the unique ID for an AWS STS federated user session. An IAM user creates this session by calling the `GetFederationToken` API. Specifying the unique ID for an AWS STS federated user session denies the named federated user session without affecting the permissions of the IAM user that created the credentials. + * `account-id:<federated-user-caller-specified-name>` represents the unique ID for an AWS STS federated user session. An IAM user creates this session by calling the `GetFederationToken` API. Specifying the unique ID for an AWS STS federated user session denies the named federated session without affecting the permissions of the IAM user that created the credentials.