Breaking02 / IT
AWS adds Gateway policy layer to Okta agent delegation setup
Per-user permission decisions stay on the tool servers, and the AWS post gives no measurements at the scale of hundreds of agents.

AWS published Part 2 of its Okta delegation setup on 7 Nov 2026, extending a Part 1 build that used AgentCore Python SDK 1.24.1. Developers following the guide now manage connections between tools and agents through Gateway policies written in Cedar, a language for defining access rules.
According to AWS, agents reach the tool servers through a single Gateway. The Gateway handles token exchange, and the agent role loses its exchange and secret permissions. Cedar policies are evaluated before a tool runs, and the default is deny.
Part 1 used one agent and two tool servers. In the Part 2 tests, a test user named Bob saw six tools through agent A and four through the read-only agent B. AWS's Part 2 validation table shows that Cedar policies hid the write tools from the list on agent B.
Compatibility. AWS said the Okta configuration and tool servers from Part 1 stay in place, and per-user permission decisions remain on those servers. Each agent has its own Gateway and credential provider. If a client does not follow the page cursor, later tools drop out of the list.
The control plane for EKS, Amazon's managed Kubernetes service, costs $0.10 per hour, AWS said, with node charges and the Auto Mode management fee on top. AgentCore features are billed by usage. The post labels its code as a sample for non-production use.
Where it runs. AWS's documentation shows that the setup requires an AWS account and an Okta organisation. The Part 1 tests used the US West (Oregon) Region and an Okta Integrator Free Plan organisation. The second agent also requires eksctl, kubectl and Docker.
AWS's validation covered a two-agent setup. The post gives no measurements at the scale of hundreds of agents.