# Amazon — Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore – Part 1

- Company: Amazon (amazon.com)
- Announced: 2026-11-06T17:09:18+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/govern-ai-agent-access-with-okta-cross-app-access-and-amazon-bedrock-agentcore-part-1/
- Record: https://forck.live/items/32596-govern-ai-agent-access-with-okta-cross-app-access-and-amazon-bedrock-agentcore
- Subject: Bedrock / Nova

Amazon's first of two posts shows how to govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore, so an identity team can say which agent may act for which user in which application. Okta is the governance plane, deciding which agent may act for which user against which resource, while AgentCore Identity is the execution plane, holding the agent's credentials and turning Okta's decision into a token the resource accepts. Each request carries three tokens: the ID token says who the user is, the Identity Assertion JWT Authorization Grant is Okta's decision, and the access token is what the resource accepts. The ID-JAG is single-use and expires in 5 minutes, and the access token Okta returns also lasts 5 minutes and names both the user and the agent. In tests, after an administrator removed a user's assignment to the agent, Okta refused the agent's new requests for that user within about 1 second, and tokens already issued expired within 5 minutes. AgentCore Identity added about 0.6 seconds to a request that took about 30 seconds end to end. The walkthrough takes about 1 hour, builds on the AWS sample 08-okta-xaa-delegation-chain, and the code is sample code for non-production use.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/govern-ai-agent-access-with-okta-cross-app-access-and-amazon-bedrock-agentcore-part-1/:

> An AI agent that updates a ticket or reads a customer record acts for a person, inside applications that person can reach. Your identity team then has to answer a question that per-app OAuth consent and shared service accounts leave open: which agent might act for which user in which application, and how you stop it. Okta Cross App Access (XAA) answers it in your identity provider (IdP). You register the agent in Okta, an administrator approves the applications it might reach, and Okta evaluates policy each time the agent asks to act for a user. In our tests, after an administrator removed a user’s assignment to the agent, Okta refused the agent’s new requests for that user within about 1 second, and tokens already issued expired within 5 minutes.
> 
> Amazon Bedrock AgentCore is a platform to build, connect, and optimize agents at scale, with any framework or model. This solution uses two of its capabilities to carry out Okta’s decision on AWS. Amazon Bedrock AgentCore runtime, a capability of Amazon Bedrock AgentCore, validates Okta’s grant.

---

Record: https://forck.live/items/32596-govern-ai-agent-access-with-okta-cross-app-access-and-amazon-bedrock-agentcore
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
