AWS wires Okta Cross App Access into Bedrock AgentCore: 5-minute single-use grants, and removing a user's assignment is refused within about a second
A measured walkthrough of letting the identity provider decide which agent may act for which user in which app, with the timings of each revocation.
// Key points
- Okta mints an ID-JAG per request after checking the agent is active, the user is assigned and an admin connected the target; the grant is single-use and expires in 5 minutes
- AgentCore Identity redeems it for a 5-minute access token naming both user and agent; across 10 requests the first redemption took about half a second, and a reused token came back in a median of 58 ms
- Deleting the agent's resource connection refuses new requests immediately; removing the user's assignment refuses them within about 1 second; deactivating the agent was queued for 86 minutes in the test org
- Tokens already issued keep working for up to 5 minutes; AgentCore Identity added about 0.6 seconds to a request of about 30 seconds end to end
Builder's takeThe number I'd remember is 86 minutes: "deactivate the agent" is not your kill switch, deleting its connection is. With the 11-04 ServiceNow on-behalf-of post, the pattern is settling on short tokens that carry both user and agent; I'd make that the default for any agent we let touch the AI cloud drive's sharing APIs.
// Background · from #AI agents
Full timeline →- Nov 7 AWS runs Claude Code as a remote agent on Bedrock AgentCore: one microVM per task, up to three attempts, and a draft pull request unless verification passes
- Nov 7 Anthropic on agent memory: "dreaming" over 128 sessions lifts a wiki-only score from 13% to 48%, and wiki plus search saves about 20,000 tokens per question
- Nov 7 Mistral Studio adds managed agents and apps, with skills, sandboxes, subagents, hooks and OpenTelemetry traces, deployable in your own VPC or on-premises