AWS发布AgentCore智能体访问治理指南
AWS Machine Learning Blog发布了第一部分实操指南,介绍如何使用Okta Cross App Access和Amazon Bedrock AgentCore治理AI智能体访问。该方案由Okta逐次判断用户与智能体的授权关系,再由AgentCore验证授权并通过令牌库获取短期凭据,避免向智能体代码暴露凭据。AWS实测显示,撤销用户分配后约1秒内拒绝新请求,已签发令牌在5分钟内过期,AgentCore Identity为约30秒的请求增加约0.6秒。
该指南展示了AI智能体生产部署中按用户授权、委托令牌交换和凭据隔离的具体实现路径。
An AI agent that updates a ticket or reads a customer record acts for a person, inside applications that person can reach. Your identity team then has to answer a question that per-app OAuth consent and shared service accounts leave open: which agent might act for which user in which application, and how you stop it. Okta Cross App Access (XAA) answers it in your identity provider (IdP). You register the agent in Okta, an administrator approves the applications it might reach, and Okta evaluates policy each time the agent asks to act for a user. In our tests, after an administrator removed a user’s assignment to the agent, Okta refused the agent’s new requests for that user within about 1 second, and tokens already issued expired within 5 minutes.
Amazon Bedrock AgentCore is a platform to build, connect, and optimize agents at scale, with any framework or model. This solution uses two of its capabilities to carry out Okta’s decision on AWS. Amazon Bedrock AgentCore runtime, a capability of Amazon Bedrock AgentCore, validates Okta’s grant. Amazon Bedrock AgentCore Identity, a capability of Amazon Bedrock AgentCore, redeems it for a short-lived access token with credentials your agent code doesn’t see, and keeps that token in its token vault. In our tests, AgentCore Identity added about 0.6 seconds to a request that took about 30 seconds end to end.
#Amazon Web Services#Okta#Okta Cross App Access#Amazon Bedrock AgentCore#Amazon Bedrock AgentCore Identity#Amazon Bedrock AgentCore runtime