Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore – Part 2
AWS Machine Learning Blog · 人工智能
In Part 1 , you built a task agent on Amazon Bedrock AgentCore , a platform to build, connect, and optimize agents at scale, with any framework or model. The agent runs on Amazon Bedrock AgentCore runtime, a capability of Amazon Bedrock AgentCore, and acts for signed-in users through Okta Cross App Access (XAA). Okta decided which agent might act for which user, and Amazon Bedrock AgentCore Identity, a capability of Amazon Bedrock AgentCore, redeemed Okta’s grant inside the agent. That proves the governance mechanism, and it runs on a deliberately small topology: one agent, two Model Context Protocol (MCP) servers, and the authorization check written into each server. The mechanism scales. The topology doesn’t. Three things that are fine for one agent and two tools become the work in an enterprise with hundreds of agents and thousands of tools: What Part 1 does Why it stops scaling What Part 2 does instead The agent holds each MCP server’s runtime ARN and calls it directly N agents against M servers is a wiring matrix, and every new tool touches every agent that needs it Agents reach one Gateway endpoint, and the Gateway holds the target registry The agent’s role holds the token-exchange permission and reads the provider’s secret Every agent that acts for users gets a credential path to every resource it might reach The Gateway redeems the grant, and the agent’s role holds no token-exchange or secret permissions Each MCP server carries the same groups check in its own code The same rule, copied into thousands of servers, drifts and can’t be audited or changed in one place One default-deny Cedar policy set, evaluated at the Gateway before tools run In this post, you make that change on the Part 1 solution. Amazon Bedrock AgentCore Gateway, a capability of Amazon Bedrock AgentCore, becomes the single front door and redeems Okta’s grant for each target. Policy in Amazon Bedrock AgentCore evaluates Cedar policies that bind each tool to the agent and the scope Okta deleg