AgentCore Identity支持私有CA证书
Amazon Bedrock AgentCore Identity 现已支持私有 CA 证书,可让智能体连接自托管身份提供商。AWS Machine Learning Blog 表示,用户可将 PEM 编码的根 CA 或中间 CA 证书存储在 AWS Secrets Manager 或 Amazon S3,并在凭证提供程序中引用,用于验证相关端点;私有连接需要 VPC Lattice。
这项更新使 AI 智能体能够信任企业现有的私有 CA,并连接 Keycloak 等私有身份提供商,同时提供了证书验证和轮换的具体配置方法。
Many teams that build applications self-host their identity provider (IdP), such as Keycloak or PingFederate, inside a private network. These IdPs usually present a TLS server certificate from a private certificate authority (CA). With private CA support in AgentCore Identity, a capability of Amazon Bedrock AgentCore, your agents can now connect to these IdPs while trusting the private CA that your organization already uses.
AgentCore Identity now supports private CA certificates for private identity providers. You store the PEM-encoded CA certificate in AWS Secrets Manager or Amazon Simple Storage Service (Amazon S3) and reference it from your credential provider. The CA certificate contains only the public certificate, not its private key. AgentCore Identity uses it to validate the server certificate presented by your IdP’s discovery, JSON Web Key Set (JWKS), and token endpoints. The CA certificate must be a root or intermediate CA certificate.
In this post, we show you how to issue an IdP certificate with AWS Private Certificate Authority. We then configure an AgentCore Identity credential provider to trust it and rotate the CA while minimizing downtime. We also show how to protect the CA certificate so that only your IdP team can change it. Although AgentCore Identity supports any private CA, including enterprise, third-party, and self-signed root CAs, the walkthrough in this post uses AWS Private CA and Keycloak as the IdP.
#Amazon Bedrock AgentCore Identity#Amazon Bedrock AgentCore Gateway#AWS Private Certificate Authority#AWS Secrets Manager#Amazon S3#Amazon VPC Lattice#Keycloak#AWS Certificate Manager