Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore – Part 1
Machine Learning Blog
This article demonstrates how to govern AI agent access using Okta Cross App Access and Amazon Bedrock AgentCore, enabling administrators to control which agents can act for which users in which applications.
- Okta Cross App Access (XAA) acts as the governance plane, deciding which agent can access which resource for which user
- Amazon Bedrock AgentCore Identity executes Okta's decisions by redeeming tokens and managing short-lived credentials
- The solution uses a three-token chain: ID token, Identity Assertion JWT Authorization Grant (ID-JAG), and access token
- AgentCore runtime validates Okta's grants via JWT authorizer, accepting only agent-specific ID-JAGs
- User authority is enforced through groups claims in tokens and checked at both the runtime and MCP server levels
- Administrator actions like removing user assignments take effect within 1 second for new requests
- AgentCore Identity adds approximately 0.6 seconds latency to requests taking about 30 seconds end-to-end
- Best practices include minting fresh ID-JAGs per request, carrying per-user authority in groups claims, and keeping token lifetimes short
The pattern applies across industries where agents need fine-grained access control tied to user identity and authorization, with Okta managing governance and AgentCore executing it securely.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
2026
2026
2026
2026
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.