# AWS STS supports cross-partition federation for AWS identities

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

AWS announced on 9 November 2026 that AWS STS lets a workload use its IAM identity in one partition to get temporary credentials for a role in another, such as from commercial Regions to GovCloud, without long-term credentials. It works through the existing GetWebIdentityToken and AssumeRoleWithWebIdentity APIs.

AWS says each partition has an independent instance of IAM, a hard boundary, and that organizations running workloads across partitions commonly relied on long-term credentials such as IAM user access keys. With this launch a workload requests a short-lived token from STS in its own partition and exchanges it in the other.

Administrators control which identities can access each role and audit token use in CloudTrail in both partitions. AWS notes that IAM Roles Anywhere is another option if you operate a public key infrastructure. The feature is available at no additional charge in the commercial, GovCloud, China and European Sovereign Cloud Regions.

## Related pages

- [IAM Roles Anywhere checks certificate revocation automatically](/news/roles-anywhere-crl-distribution-points/)
- [AWS introduces account access manager for assigning IAM roles to workforce users](/news/account-access-manager/)
- [AWS Sign-In supports OAuth 2.0 Token Exchange](/news/signin-oauth-token-exchange/)
- [All of them](/news/)

## Sources

- https://aws.amazon.com/about-aws/whats-new/2026/11/aws-sts-cross-partition (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://iampolicygenerator.com/news/sts-cross-partition-federation/

This site is not affiliated with Amazon Web Services. AWS service and product names are used only to describe AWS services.
