# Amazon — Private certificate authority support in Amazon Bedrock AgentCore Identity

- Company: Amazon (amazon.com)
- Announced: 2026-11-18T20:53:41+00:00
- Category: not stated
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://aws.amazon.com/blogs/machine-learning/private-certificate-authority-support-in-amazon-bedrock-agentcore-identity/
- Record: https://forck.live/items/38237-private-certificate-authority-support-in-amazon-bedrock-agentcore-identity
- Subject: Bedrock / Nova

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. …

---

Record: https://forck.live/items/38237-private-certificate-authority-support-in-amazon-bedrock-agentcore-identity
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
