AWS shows how to govern AI agent access with Okta and Bedrock AgentCore Gateway
AWS published Part 2 of a tutorial on governing AI agent access using Okta Cross App Access (XAA) and Amazon Bedrock AgentCore. The post moves from a small topology—one agent and two Model Context Protocol (MCP) servers—to an enterprise-scale pattern with a single front door: the AgentCore Gateway. The Gateway redeems Okta’s Identity Assertion JWT Authorization Grant (ID-JAG) for each target,…
Key points
- AgentCore Gateway becomes single front door redeeming Okta ID-JAG for each target with Cedar policies
- Second agent on Amazon EKS joins under its own Okta identity proving location-independent governance
The story so far
6 episodes →- AWS shows how to govern AI agent access with Okta and Bedrock AgentCore Gatewaythis story
Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore
AWS Machine Learning Blog · 6 November 2026
Loading the full article…
This text was published by AWS Machine Learning Blog and written by Hammad Ausaf. It is reproduced here with attribution so you can read it in full; the rights remain with the publisher. Read it at the source ↗
The headline, key points and digest above were generated by Digest AI's editorial model from the linked sources. Automated summaries can contain errors: the sources are the record. Spotted a mistake? Tell us. Published by Martin K., who runs Digest AI and handles corrections.
More in Agents & Tools
All →- Perplexity launches Teammates agents for Perplexity Max users · 3 src
- Zapier Sidekick automates deal reports, Slack channels and more for users · 1 src
- Zapier’s Sidekick shifts AI approvals from tools to protected resources · 1 src
- OpenAI, Meta and xAI launch AI agents for long-term task delegation · 8 src
- Study finds AI agents waste 18% of tokens on unnecessary tasks · 1 src
Comments
via GitHub Discussions