AWS IAM documentation change
Summary
Specified 'AWS STS federated user principal' in the list of valid principal types
Security assessment
The change refines terminology for policy elements but does not mitigate a security issue or document new security features. It ensures consistency with other documentation updates.
Diff
diff --git a/IAM/latest/UserGuide/reference_policies_elements_notprincipal.md b/IAM/latest/UserGuide/reference_policies_elements_notprincipal.md index b3b3ae14f..ae4beb483 100644 --- a//IAM/latest/UserGuide/reference_policies_elements_notprincipal.md +++ b//IAM/latest/UserGuide/reference_policies_elements_notprincipal.md @@ -9 +9 @@ Key pointsAlternatives to the NotPrincipal elementExample scenario using an IAM -The `NotPrincipal` element uses `"Effect":"Deny"` to deny access to all principals **_except_** the principal specified in the `NotPrincipal` element. A principal can be an IAM user, federated user, IAM role, assumed role session, AWS account, AWS service, or other principal type. For more information about principals, see [AWS JSON policy elements: Principal](./reference_policies_elements_principal.html). +The `NotPrincipal` element uses `"Effect":"Deny"` to deny access to all principals **_except_** the principal specified in the `NotPrincipal` element. A principal can be an IAM user, AWS STS federated user principal, IAM role, assumed role session, AWS account, AWS service, or other principal type. For more information about principals, see [AWS JSON policy elements: Principal](./reference_policies_elements_principal.html).