Oriel — AI & technology worth noticing, every day.

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

Web page · 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 acts for a user raises an identity question that per-app OAuth and service accounts leave open: which agent may act for which user, and how you stop it. In this first post of two, you build a task agent on Amazon Bedrock AgentCore that governs access through Okta Cross App Access and AgentCore Identity, and enforces each user's authority.

First seen by Oriel on .

AI summary

This AWS walkthrough shows how to govern user-authorized AI agent access with Okta Cross App Access, Amazon Bedrock AgentCore runtime, and AgentCore Identity using short-lived, policy-controlled token exchanges.

  • Okta evaluates whether an agent, user, target authorization server, and requested scopes are permitted, issuing a single-use ID-JAG that expires in 5 minutes.
  • AgentCore runtime validates the ID-JAG, while AgentCore Identity redeems it for a 5-minute access token containing both user and agent identities.
  • The agent calls MCP servers with the access token, and task-manager tools enforce group and scope permissions such as xaa:read and xaa:write.
  • Removing a user’s agent assignment blocked new requests within about 1 second, while already issued tokens expired within 5 minutes.
  • AgentCore Identity added about 0.6 seconds to requests taking roughly 30 seconds end to end, and its token vault reused tokens within a request.

#okta #amazon bedrock agentcore #oauth #ai agents

Generated by gpt-5.6-sol. Check the original for details.

Aliases

SourceExternal IDURL
AWS Machine Learning Blogc0f0c6e1e028e85f24cb91645e1a321ffca6e02ahttps://aws.amazon.com/blogs/machine-learning/govern-ai-agent-access-with-okta-cross-app-access-and-amazon-bedrock-agentcore-part-1/ Read discussion