# AWS Sign-In supports OAuth 2.0 Token Exchange

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

AWS announced on 4 November 2026 that AWS Sign-In supports OAuth 2.0 Token Exchange (RFC 8693). Applications can swap third-party OpenID Connect tokens for short-lived, AWS service-scoped OAuth access tokens, so third-party applications reach supported AWS services without AWS credentials being shared.

AWS says access controls are still maintained through AWS Identity and Access Management. The capability applies to supported AWS services that use AWS Sign-In OAuth, and lets customers use their existing identity providers.

The announcement refers readers to the AWS Sign-In User Guide, the AWS MCP Server User Guide and an AWS Glue launch announcement for details.

## Related pages

- [Service reference adds global condition keys and a data plane flag](/news/service-reference-global-keys-data-plane/)
- [IAM outbound federation supports VPC endpoints for OIDC discovery](/news/outbound-federation-vpc-endpoints/)
- [AWS HealthOmics supports IAM session policies](/news/healthomics-session-policies/)
- [All of them](/news/)

## Sources

- https://aws.amazon.com/about-aws/whats-new/2026/11/aws-signin-token-exchange/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://iampolicygenerator.com/news/signin-oauth-token-exchange/

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