AWS Security ChangesHomeSearch

AWS singlesignon: Document cross-Region trusted identity propagation requirements

Service: singlesignon · 2026-10-24 · Documentation medium

File: singlesignon/latest/userguide/multi-region-application-use.md · Type: authz

Summary

Replaces the statement that identity propagation applications must be in the same Region with guidance that cross-Region propagation works with a multi-Region instance and a multi-Region customer managed KMS key.

Security assessment

The added lines describe authorization behavior (aws services in a receiving Region authorizing based on propagated user attributes) and state an encryption requirement (multi-Region customer managed KMS key), which is security-relevant configuration guidance rather than a fix for a specific vulnerability.

Evidence

Cross-Region trusted identity propagation requires a multi-Region IAM Identity Center instance with a multi-Region customer managed KMS key.

Diff

diff --git a/singlesignon/latest/userguide/multi-region-application-use.md b/singlesignon/latest/userguide/multi-region-application-use.md
index 4d02f51..6c7bff2 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
-You can use trusted identity propagation with AWS managed applications that support it in any enabled Region of your IAM Identity Center instance. 
+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.
@@ -50 +50 @@ You can use trusted identity propagation with AWS managed applications that supp
-All applications that propagate identity context to each other must be in the same Region.
+Cross-Region trusted identity propagation requires a multi-Region IAM Identity Center instance with a multi-Region customer managed KMS key. If you have already enabled multi-Region replication and set up trusted identity propagation for your AWS services, cross-Region trusted identity propagation works across the additional Regions automatically.