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…
Same story
Filed as part of the same story as Use decision models with Amazon Bedrock AgentCore Evaluations (AWS, 2026-11-04).
What moved
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. …
Why it matters
Filed as a public note from AWS, 2026-11-06. The desk tags this brief Agents / Enterprise.
On the record
- Filed from the AWS official RSS on 2026-11-06.
- Primary source host: aws.amazon.com.
- 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.
Primary source
aws.amazon.com
aws.amazon.com
Desk
Logged as brief 9080
Logged as brief 9080
Cite this brief
Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore – Part 1 (AWS, 2026-11-06) — https://labledgerdesk.pages.dev/b/2026/11/06/govern-ai-agent-access-with-okta-cross-app-access-and-amazon-bedrock-9080/