AWS published a technical post on November 18, 2026, documenting private certificate authority (CA) support in Amazon Bedrock AgentCore Identity for private identity providers (IdPs). The service uses the configured CA certificate to validate TLS connections to an IdP’s discovery, JWKS and token endpoints, so the IdP can remain inside a private network. AWS’s documented setup requires a private endpoint using Amazon VPC Lattice. AWS’s technical post describes the configuration and its trust-lifecycle requirements.

Treat the stored CA certificate and the credential-provider configuration as one change: editing the stored certificate alone does not refresh AgentCore Identity’s trust.

What the private-IdP configuration requires

Amazon Bedrock AgentCore console with the Add root certificate panel open, AWS Secrets Manager selected, and Amazon S3 offered as another source.

The CA file must be a valid PEM-encoded root or intermediate certificate no larger than 16 KB. It contains public certificate data, not the CA’s private key. One credential provider can reference a single Secrets Manager secret or S3 object, and that PEM file can contain more than one trusted CA. AWS’s walkthrough uses AWS Private CA and Keycloak, but AWS says enterprise, third-party and self-signed root CAs are also supported.

The referenced secret or object must be in the same AWS Region as the credential provider. A Secrets Manager secret must also be in the same AWS account. An S3 object can be in another account if the provider configuration includes bucketOwnerAccountId and the bucket policy grants the required access. The principal creating or updating the provider needs permission to read the object; if a customer-managed KMS key encrypts it, that principal also needs kms:Decrypt.

The IdP’s server certificate must chain to a CA in the configured trust set, and its subject alternative name (SAN) must match the IdP hostname. Amazon VPC Lattice provides the required private network connection; AgentCore Identity can manage the VPC Lattice resources, or customers can manage them themselves.

The AgentCore console’s root-certificate panel offers AWS Secrets Manager and Amazon S3 as certificate sources. In the captured interface, Secrets Manager is selected.

How CA changes affect trust

Changing the file in Secrets Manager or S3 does not make AgentCore Identity reread it. Update the credential provider and include certificateConfigurations; omitting that configuration from an update removes the provider’s private-CA trust.

For a CA rotation, AWS describes adding the old and new CA certificates to the trust set, updating the provider and waiting for READY, then replacing the IdP server certificate and checking token requests. After that works, remove the old CA and update the provider again. This staged sequence lets the provider trust certificates issued by either CA during the transition.

AWS also documents the CloudWatch metric EarliestCertificateDaysToExpiry in the AWS/Bedrock-AgentCore namespace. It reports the days remaining until the earliest certificate expiry in the PEM file when agents request tokens through a provider using a private CA. The metric has the dimensions ProviderName, ProviderArn and TokenVault.

How AgentCore Identity handles certificate revocation

AgentCore Identity does not check certificate revocation lists (CRLs) or use Online Certificate Status Protocol (OCSP) for this private-CA trust path. A compromised IdP server certificate can remain trusted until it expires or its issuing CA is removed from the configured trust set and the provider is updated.

What the reported Keycloak sample did

An AWS Labs AgentCore Samples pull request reports an end-to-end test in us-east-1: an AgentCore Runtime agent obtained a Keycloak token through the credential provider and called an AgentCore Gateway. The pull request also reports that, in that sample, omitting certificateConfigurations caused token requests to fail with HTTP request failed against private endpoint, and the Gateway entered FAILED with Failed to validate discovery url. Those outcomes are specific to the reported sample test. The AWS Labs pull request does not establish a general result for every deployment.