What changed
Amazon Bedrock AgentCore Identity now supports private certificate authority (CA) certificates for private identity providers (IdPs). This allows agents to connect to self-hosted IdPs such as Keycloak or PingFederate while trusting the private CA that an organization already uses.
What this means in practice
With private CA support, agents can securely connect to IdPs running in a private network. The CA certificate, stored in AWS Secrets Manager or Amazon S3, is used to validate the server certificate presented by the IdP’s discovery, JSON Web Key Set (JWKS), and token endpoints. This setup enables secure communication without requiring changes to the agent’s code, supporting machine-to-machine, on-behalf-of, and user-delegated flows.
Limitations and availability
Private CA support requires VPC Lattice for private endpoint connections. The CA certificate must be in PEM format, no larger than 16 KB, and contain only valid root or intermediate CA certificates. The certificate must be stored in the same AWS Region as the credential provider, with Secrets Manager secrets also in the same account. The feature is available in AWS Regions where AgentCore Identity supports private IdPs. The walkthrough uses AWS Private CA and Keycloak as the IdP, but any private CA is supported.
