AWS Security ChangesHomeSearch

AWS singlesignon: Cross-Region trusted identity propagation prerequisites and SCP guidance

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

File: singlesignon/latest/userguide/trustedidentitypropagation-overall-prerequisites.md · Type: iam

Summary

Restructures trusted identity propagation prerequisites to describe same-Region vs. cross-Region deployments (multi-Region IAM Identity Center instance with a multi-Region customer managed KMS key) and adds a new 'Considerations for cross-Region trusted identity propagation' section covering eventual consistency, token re-authentication, and using a service control policy with the aws:RequestedRegion condition key to block cross-Region calls.

Security assessment

The change documents a defense-in-depth control (SCP with aws:RequestedRegion to restrict/deny cross-Region requests) plus encryption via a multi-Region customer managed KMS key and token re-authentication after replication. This is security best-practice guidance for identity propagation, not a fix for a specific vulnerability or incident.

Evidence

    * If you do not want AWS services to make cross-Region calls, you can block them by using a service control policy (SCP). You can build this policy using the `aws:RequestedRegion` condition key to allow only the Regions you use and deny requests to all others. For more information about an example policy that uses this condition key, see [AWS: Denies access to AWS based on the requested Region](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_examples_aws_deny-requested-region.html).

Diff

diff --git a/singlesignon/latest/userguide/trustedidentitypropagation-overall-prerequisites.md b/singlesignon/latest/userguide/trustedidentitypropagation-overall-prerequisites.md
index b573dbf..5a91e93 100644
--- a//singlesignon/latest/userguide/trustedidentitypropagation-overall-prerequisites.md
+++ b//singlesignon/latest/userguide/trustedidentitypropagation-overall-prerequisites.md
@@ -7 +7 @@
-PrerequisitesConsiderationsConsiderations for customer managed applications
+PrerequisitesConsiderationsConsiderations for cross-Region trusted identity propagationConsiderations for customer managed applications
@@ -18,0 +19,2 @@ Before you set up trusted identity propagation, review the following prerequisit
+  * Considerations for cross-Region trusted identity propagation
+
@@ -30 +32,3 @@ To use trusted identity propagation, ensure your environment meets the following
-    * To use trusted identity propagation, you must enable IAM Identity Center in the same AWS Region where the AWS applications and services your users will access are enabled. For information, see [Enable IAM Identity Center](./enable-identity-center.html).
+    * You can use trusted identity propagation with your AWS services deployed in the same Region or in different Regions. Choose the deployment that fits your architecture:
+
+      * **Same-Region** – Enable IAM Identity Center in the same AWS Region as the AWS services your users access.
@@ -32 +36,3 @@ To use trusted identity propagation, ensure your environment meets the following
-      * IAM Identity Center Organization instance is recommended - We recommend you use an [organization instance](./organization-instances-identity-center.html) of IAM Identity Center that you enable in the management account of AWS Organizations. You can [delegate administration](./organization-instances-identity-center.html) of an organization instance of IAM Identity Center to a member account. If you choose an [account instance](./account-instances-identity-center.html) of IAM Identity Center, all AWS services that you want users to access with trusted identity propagation must reside in the same AWS account where you enable IAM Identity Center. For more information, see [Account instances of IAM Identity Center](./account-instances-identity-center.html).
+      * **Cross-Region** – Create a multi-Region IAM Identity Center instance configured with a multi-Region customer managed KMS key. Trusted identity propagation then works across the additional AWS Regions where you replicated your instance, with no additional configuration. For more information, see [Implementing customer managed KMS keys in AWS IAM Identity Center](./identity-center-customer-managed-keys.html) and [Using IAM Identity Center across multiple AWS Regions](./multi-region-iam-identity-center.html).
+
+      * **Organization instance** – We recommend you use an [organization instance](./organization-instances-identity-center.html) of IAM Identity Center that you enable in the management account of AWS Organizations. You can [delegate administration](./organization-instances-identity-center.html) of an organization instance of IAM Identity Center to a member account. If you choose an [account instance](./account-instances-identity-center.html) of IAM Identity Center, all AWS services that you want users to access with trusted identity propagation must reside in the same AWS account where you enable IAM Identity Center. For more information, see [Account instances of IAM Identity Center](./account-instances-identity-center.html).
@@ -55,0 +62,19 @@ Keep in mind the following considerations when configuring and using trusted ide
+## Considerations for cross-Region trusted identity propagation
+
+Keep in mind the following considerations when using cross-Region trusted identity propagation.
+
+  * **Eventual consistency**
+
+    * IAM Identity Center replicates identity metadata to additional Regions asynchronously, with eventual consistency.
+
+  * **Tokens and re-authentication**
+
+    * After you enable multi-Region replication for additional Regions, those Regions do not accept tokens issued before you enabled replication. Your users must re-authenticate once so that newly issued tokens work across all enabled Regions.
+
+  * **Blocking cross-Region calls**
+
+    * If you do not want AWS services to make cross-Region calls, you can block them by using a service control policy (SCP). You can build this policy using the `aws:RequestedRegion` condition key to allow only the Regions you use and deny requests to all others. For more information about an example policy that uses this condition key, see [AWS: Denies access to AWS based on the requested Region](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_examples_aws_deny-requested-region.html).
+
+
+
+