AWS IAM documentation change
Summary
Updated documentation link from 'session principals' to 'principals'
Security assessment
This is a routine documentation link correction with no security implications or changes to security guidance.
Diff
diff --git a/IAM/latest/UserGuide/id_federation_common_scenarios.md b/IAM/latest/UserGuide/id_federation_common_scenarios.md index 2f95f4ca5..600561f73 100644 --- a//IAM/latest/UserGuide/id_federation_common_scenarios.md +++ b//IAM/latest/UserGuide/id_federation_common_scenarios.md @@ -105 +105 @@ Typically, if the user is not already signed in, the IdP takes care of displayin - 6. Using the temporary security credentials from the `AssumeRoleWithWebIdentity` response, your app makes signed requests to AWS API operations. The user ID information from the IdP can distinguish users in your app. For example, you can put objects into Amazon S3 folders that include the user ID as prefixes or suffixes. This lets you create access control policies that lock the folder so only the user with that ID can access it. For more information, see [AWS STS federated user session principals](./reference_policies_elements_principal.html#sts-session-principals). + 6. Using the temporary security credentials from the `AssumeRoleWithWebIdentity` response, your app makes signed requests to AWS API operations. The user ID information from the IdP can distinguish users in your app. For example, you can put objects into Amazon S3 folders that include the user ID as prefixes or suffixes. This lets you create access control policies that lock the folder so only the user with that ID can access it. For more information, see [AWS STS federated user principals](./reference_policies_elements_principal.html#sts-session-principals).