Amazon Web Services (AWS) announced a significant enhancement to its Identity and Access Management (IAM) outbound identity federation capabilities. Workloads operating across AWS partitions—such as Commercial, China, GovCloud (US), and European Sovereign Cloud—can now securely obtain short-lived, AWS-signed JSON Web Tokens (JWTs) in the source partition and exchange them for temporary credentials in a destination partition. This new feature supports cross-partition AWS resource access without the need for long-term credential storage or rotation.
Traditionally, partitions represent strict isolation boundaries within AWS, with independent IAM instances. As a result, credentials issued in one partition are invalid in another, preventing direct role assumption across partitions via the sts:AssumeRole API. The new mechanism employs sts:GetWebIdentityToken in the source partition to obtain JWTs, which are then presented to sts:AssumeRoleWithWebIdentity in the destination partition. AWS STS endpoints handle token validation and return scoped temporary credentials, enabling resource access such as Amazon S3 buckets.
Key benefits include carrying origin identity information to authorization decisions, as destination trust policies can condition access based on the source identity context, including account ID, organization ID, source region, and principal. Additionally, AWS CloudTrail logs in both source and destination regions provide a correlated audit trail of cross-partition activity using unique token identifiers. The approach emphasizes security by relying entirely on temporary credentials and a fully managed token infrastructure, obviating the need for organizations to maintain their own public key infrastructure or token providers.
The feature is illustrated with a walkthrough involving cross-partition access to an S3 bucket, detailing setup steps such as enabling outbound identity federation in the source partition, configuring trust policies in the destination account, and performing token exchange via AWS CLI commands. The process supports automation in workloads running on AWS compute services like EC2, Lambda, or EKS, reducing manual intervention for token handling.
However, AWS strongly advises consulting compliance teams to ensure the cross-partition access implementation meets regulatory requirements like FedRAMP, ITAR, DoD CC SRG, and GDPR. Security best practices also include applying the principle of least privilege, restricting token audiences, using short-lived tokens, enabling end-to-end CloudTrail monitoring, and controlling cross-partition trust via IAM condition keys and resource control policies.
A key limitation is that cross-partition federation is not enabled by default and requires explicit account-level activation and configuration. Furthermore, the system relies on condition keys and trust policies to allowlist approved issuers or partitions, imposing administrative overhead to maintain secure boundaries. Access paths should also be initiated from more restrictive to less restrictive partitions to align with governance protocols.
Overall, this extension to AWS IAM outbound identity federation simplifies secure and auditable cross-partition access for multi-cloud or segmented AWS environments. It reduces operational complexity by leveraging native AWS managed token services and IAM role trust policies, while maintaining compliance and minimizing long-term credential risks.
Source & further reading
Simplify cross-partition access with AWS IAM outbound identity federation ↗Source published 2026-11-09. Claims and limitations should be checked against the original announcement or research.