From the source
- AWS's second post in a series shows how to move a working Okta Cross App Access agent setup from a single agent and two MCP servers to a topology that holds hundreds of agents and thousands of tools.
- The first post proved the governance mechanism, where Okta decided which agent could act for which user and
Amazon Bedrock AgentCore Identity redeemed that grant inside the agent on Amazon Bedrock AgentCore runtime.
- Amazon Bedrock AgentCore Gateway becomes the single front door and redeems Okta's grant for each target, while Policy in Amazon Bedrock AgentCore evaluates Cedar policies that bind each tool to the agent and the scope Okta delegated.
- A second reporting agent on Amazon Elastic Kubernetes Service joins under its own Okta identity, showing the front door does not care where an agent runs.
- Amazon Bedrock AgentCore Observability with Amazon CloudWatch gives one place to read every decision, including Okta's, which streams its System Log through Amazon EventBridge.
- AWS says the additions take about 90 minutes and that the EKS control plane costs $0.10 per hour, plus nodes and the Auto Mode management fee.






