AWS adds private CA support to Bedrock AgentCore Identity

Amazon Bedrock AgentCore Identity now supports private certificate authority certificates for privately hosted identity providers, allowing agents to connect to systems such as Keycloak and PingFederate while trusting an organization’s existing CA.
- AgentCore Identity now supports private CA certificates for private identity providers.
- CA certificates can be stored in AWS Secrets Manager or Amazon S3.
- Private CA support requires Amazon VPC Lattice.
- Certificates must be PEM-encoded and no larger than 16 KB.
- Agents can use the capability across supported OAuth flows without code changes.
Support for privately hosted identity providers
AWS said the capability lets AgentCore Identity validate the server certificate presented by an identity provider’s discovery, JSON Web Key Set, and token endpoints. The CA certificate is stored in AWS Secrets Manager or Amazon Simple Storage Service, Amazon S3, and referenced from the credential provider.
The stored certificate is PEM-encoded and contains only the public certificate, not its private key. AgentCore Identity supports private enterprise, third-party, and self-signed root CAs. The walkthrough in the AWS post uses AWS Private Certificate Authority and Keycloak, although the feature is not limited to those services.
AWS said agents using machine-to-machine, on-behalf-of, and user-delegated flows can use the private CA without changes to their code.
How the private connection works
In AWS’s example, an agent running on AgentCore Runtime needs to call an internal wiki API protected by a Keycloak identity provider. Keycloak runs inside a virtual private cloud behind an internal Application Load Balancer, which presents an AWS Certificate Manager private certificate signed by AWS Private CA.
The CA certificate trusted by AgentCore Identity is stored in Secrets Manager or Amazon S3. AgentCore Identity reaches the identity provider privately through Amazon VPC Lattice, which connects to the customer’s VPC through a resource gateway. AWS says VPC Lattice is required for private CA support. With the managed option, AgentCore Identity creates and manages the VPC Lattice resources.
The flow begins when an administrator creates a credential provider that points to the identity provider and CA certificate. AgentCore Identity checks that the certificate is a valid CA certificate. When the agent requests an access token, AgentCore Identity connects to the identity provider through VPC Lattice, validates the load balancer certificate against the CA, and returns the token issued by the identity provider.
Certificate requirements and operational controls
The CA file must be PEM-encoded, no larger than 16 KB, and contain only root or intermediate CA certificates that are within their validity period. Each credential provider references one secret or one S3 object. Organizations that need to trust more than one CA can place the certificates in the same PEM file.
The secret or S3 object must be in the same AWS Region as the credential provider. Secrets Manager secrets must also be in the same account. S3 objects can be stored in another account when bucketOwnerAccountId is provided and the bucket policy grants access.
AWS said the principal calling CreateOauth2CredentialProvider needs permission to read the certificate through secretsmanager:GetSecretValue or s3:GetObject. If the certificate is encrypted with a customer managed AWS Key Management Service key, the principal also needs kms:Decrypt.
Because AgentCore Identity trusts the CA rather than a specific server certificate, the credential provider does not need to be updated each time the identity provider’s server certificate is renewed. AWS’s walkthrough also covers rotating the CA while minimizing downtime and restricting write access so only the identity provider team can change the certificate.


