Skip to content
context Security

Amazon Bedrock AgentCore Identity adds support for private certificate authorities for internal identity providers

only one source so far

Amazon has expanded AgentCore Identity with support for private certificate authorities, allowing AI agents to securely connect to internal identity providers such as Keycloak or PingFederate without a publicly trusted certificate.

Amazon Bedrock AgentCore Identity, part of the Amazon Bedrock AgentCore platform, now supports certificates from private certificate authorities (CAs) for connecting to internal identity providers (IdPs) such as Keycloak or PingFederate. Previously, these IdPs had to present a certificate from a publicly trusted CA; now a certificate signed by a corporate, third-party-operated, or even self-signed root CA can be used.

The CA certificate in PEM format is stored in AWS Secrets Manager or Amazon S3, and the credential provider references it. This is only the public part of the certificate without the private key, which AgentCore Identity uses to verify the server certificate presented by the discovery, JWKS, and token endpoints of the given IdP. The feature requires a connection via Amazon VPC Lattice, since it applies only to private IdPs, and supports standard OAuth 2.0 flows including machine-to-machine, on-behalf-of, and user-delegated, without requiring any changes to agent code.

Amazon describes in the guide a procedure for rotating the CA certificate with minimized downtime and recommends restricting write access to the certificate storage to the IdP admin team only. The documentation further notes conditions such as the need to set up a private endpoint, otherwise the request fails with an error stating that the feature can only be used with a private IdP. The source article is an implementation guide, not a press release about a standalone product release; the rest of the text with further configuration steps is not available.

What changed

Why it matters

Companies running their own identity provider within a private network previously could not easily connect AI agents in AgentCore to this IdP without a publicly trusted certificate. The new private CA support enables secure authentication without bypassing TLS validation or needing to expose the internal service to the public internet.

Relevant practical impact

What this means

01

For a business

Teams running their own IdP (Keycloak, PingFederate) and using AWS Bedrock AgentCore for AI agents can now securely connect agents to these internal systems via VPC Lattice without requiring publicly trusted certificates, which reduces the security risk associated with exposing internal endpoints.

Risks and compliance
What to decide If a company runs AI agents on AWS Bedrock AgentCore and an internal identity provider with a private CA, verify whether the new private CA support enables a more secure connection without a public certificate.
More business impacts →
AgentCore Amazon Bedrock AWS security identity management OAuth 2.0 private certificate authority

Check the original

Event sources

only one source so far · 1 publisher, 0 independent. We count feeds from the same owner only once.

1
AWS Machine Learning Blog primary source · first detected Private certificate authority support in Amazon Bedrock AgentCore Identity