AWS 演示 Okta XAA 治理 AgentCore 智能体访问
What happened
2026年11月7日，AWS Machine Learning Blog 发布文章，介绍将 Okta Cross App Access（XAA）与 Amazon Bedrock AgentCore 组合，用于治理 AI 智能体的访问。文章称，该方案在身份提供商（IdP）侧决定哪个智能体可以代表哪个用户访问哪个应用。该文标注为“上篇”，当时披露的信息限于方案定位与作用范围，尚未涉及具体配置步骤或实施细节。同日，AWS 发布教程第二部分，在 Amazon Bedrock AgentCore 上引入 Gateway 作为统一入口，由 Gateway 统一兑换 Okta 的授权，替代第一部分中每个 MCP 服务器各自校验的模式。
Written by AI from the reports · updated 1 h ago
Developments
- Nov 7 01:09 · 1 reportsAWS 博客演示用 AgentCore Gateway 统一治理 Agent 访问AWS Machine Learning Blog：Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore – Part 2
- Nov 7 01:09 · 1 reportsAWS 博客演示用 Okta XAA 治理 AgentCore 智能体访问AWS Machine Learning Blog：Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore – Part 1
Timeline
Follow the reports to see the event from each side.
- AWS Machine Learning BlogGovern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore – Part 2
In Part 1 you built one governed agent. Part 2 scales the pattern to an enterprise: Amazon Bedrock AgentCore Gateway becomes the single front door and redeems Okta's grant, Cedar policies bind each tool to the agent, a second agent runs on Amazon EKS, and AgentCore Observability traces every allow and deny beside Okta's log in Amazon CloudWatch.
- AWS Machine Learning BlogGovern 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 you stop it.
Heat of this event
Not enough continuous observations yet to draw a trend.