# IAM outbound federation supports VPC endpoints for OIDC discovery

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

AWS announced on 25 September 2026 that IAM outbound identity federation supports interface VPC endpoints for the OpenID Connect discovery APIs. Services that verify AWS-issued tokens can reach the discovery metadata and JSON Web Key Set endpoints privately through AWS PrivateLink instead of the public internet.

AWS explains that workloads request short-lived JSON Web Tokens from AWS STS, and external services verify them with public keys at OIDC discovery endpoints. Previously those endpoints were reachable only over the public internet, so a verifier in a VPC without internet access could not fetch them.

The feature is available in all commercial Regions, AWS GovCloud (US) and China Regions. AWS lists no extra charge beyond standard PrivateLink pricing.

## Related pages

- [AWS HealthOmics supports IAM session policies](/news/healthomics-session-policies/)
- [Amazon ECS extends CPU and memory condition keys to RunTask](/news/ecs-condition-keys-runtask/)
- [Lambda functions accept full IAM resource-based policies](/news/lambda-full-resource-based-policies/)
- [All of them](/news/)

## Sources

- https://aws.amazon.com/about-aws/whats-new/2026/09/aws-sts-vpc-oidc/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://iampolicygenerator.com/news/outbound-federation-vpc-endpoints/

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