# IAM outbound identity federation supports VPC endpoints for OIDC discovery

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

AWS announced on 25 September 2026 that IAM outbound identity federation supports interface VPC endpoints for OIDC discovery and JWKS key endpoints through AWS PrivateLink. Workloads that get short-lived tokens from AWS STS can have them verified without internet access, instead of using long-lived credentials.

AWS Identity and Access Management outbound identity federation now supports Amazon VPC endpoints for the OpenID Connect discovery APIs, per an AWS announcement dated 25 September 2026. You can reach the OIDC discovery metadata and the JSON Web Key Set verification key endpoints from inside your VPC with AWS PrivateLink, so the traffic that retrieves verification keys stays inside the AWS network and does not cross the public internet.

AWS explains that outbound federation removes the need for long-lived credentials when AWS workloads access external services: workloads request short-lived JSON Web Tokens from AWS STS and external services verify them with public keys. Until now the discovery endpoints were reachable only over the public internet, so a verifier in a VPC without internet access could not fetch them. The feature costs only standard PrivateLink pricing.

## Related pages

- [New AgentCore Runtime keeps hardware-enforced session isolation](/news/agentcore-runtime-v2-session-isolation/)
- [Policy Troubleshooter can now explain access denials for agents](/news/policy-troubleshooter-agent-access-denials/)
- [Google agent platform shell and computer use sandboxes reach GA with VPC-SC](/news/agent-platform-sandboxes-vpc-sc-psc-ga/)
- [All of them](/news/)

## Sources

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

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