AWS singlesignon: Reword trusted identity propagation description
Summary
Rephrased the multi-Region trusted identity propagation paragraph to use second-person phrasing; no substantive change to behavior.
Security assessment
Editorial rewording of existing identity propagation documentation with no new security guidance or fix.
Evidence
With a multi-Region IAM Identity Center instance, you can use trusted identity propagation across the Regions where you replicated your instance.
Diff
diff --git a/singlesignon/latest/userguide/multi-region-application-use.md b/singlesignon/latest/userguide/multi-region-application-use.md index 6c7bff2..60898b8 100644 --- a//singlesignon/latest/userguide/multi-region-application-use.md +++ b//singlesignon/latest/userguide/multi-region-application-use.md @@ -48 +48 @@ If your AWS managed application is using a cross-Region connection to IAM Identi -With a multi-Region IAM Identity Center instance, trusted identity propagation works across the Regions where you replicated your instance. When a user authenticates in one Region and accesses an AWS service, the user's identity context can be propagated to AWS services in other AWS Regions. The AWS service in the receiving Region authorizes access based on user attributes such as group associations, providing fine-grained, identity-based access control for cross-Region workloads. +With a multi-Region IAM Identity Center instance, you can use trusted identity propagation across the Regions where you replicated your instance. When your users authenticate in one Region and access an AWS service, you can propagate their identity context to AWS services in other AWS Regions. The AWS service in the receiving Region authorizes access based on user attributes such as group associations. This gives you fine-grained, identity-based access control for cross-Region workloads.