From the source
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.






