Amazon Bedrock AgentCore Identity Adds Private Certificate Authority Support for Private IdPs
AgentCore Identity now allows connections to self-hosted identity providers secured with private certificate authorities, improving secure integration with internal authentication systems while leveraging AWS infrastructure.
What changed?
Amazon Bedrock AgentCore Identity now supports the use of private certificate authorities (CAs) for validating self-hosted identity providers (IdPs). Developers can store a PEM-encoded CA certificate in AWS Secrets Manager or Amazon S3 and reference it from their credential provider. This allows AgentCore Identity to trust internal IdPs that use private or enterprise CA-signed certificates when establishing secure TLS connections. The feature requires the IdP to be accessed through a private endpoint, using Amazon VPC Lattice to maintain a secure, private network connection.

Why does it matter to an everyday developer?
Many organizations run their own identity providers, such as Keycloak, on private networks with certificates from internal CAs, rather than public certificate authorities. Previously, integrating these IdPs with AgentCore Identity could be complex if only publicly trusted certificates were supported. With private CA support, developers can directly connect to internal IdPs using their organization's existing trust infrastructure without code changes. This enables secure OAuth flows for agents in controlled environments, reduces certificate management overhead, and supports compliance or enterprise security policies.
What can the developer do now?
Developers can integrate their Bedrock AgentCore agents with private, OpenID Connect-compliant IdPs that use certificates signed by an internal CA. Required steps include exporting the relevant CA certificate in PEM format, storing it in AWS Secrets Manager or S3, configuring the credential provider to reference this CA, and ensuring the IdP is accessible through a private VPC Lattice endpoint. Developers should ensure the CA file is within validity and size limits, and that storage location and access permissions comply with AWS requirements. No agent code changes are needed for OAuth flows if using machine-to-machine or delegated auth scenarios.
