Private certificate authority support in Amazon Bedrock AgentCore Identity
Amazon Bedrock AgentCore Identity now supports private certificate authorities, allowing agents to authenticate to self‑hosted IdPs (e.g., Keycloak) that present TLS certificates signed by an internal CA. The PEM‑encoded root or intermediate CA is stored in AWS Secrets Manager or Amazon S3 and referenced by an AgentCore Identity credential provider, with traffic routed through VPC Lattice. This enables seamless OAuth 2.0 token retrieval for machine‑to‑machine, on‑behalf‑of, and user‑delegated flows without code changes, while preserving existing private‑CA trust chains.
⚡ Key Takeaways
- Private CA certificates are stored as PEM files in AWS Secrets Manager or Amazon S3 and referenced by an AgentCore Identity credential provider.
- AgentCore Identity validates IdP discovery, JWKS, and token endpoints against the supplied private CA via VPC Lattice.
- VPC Lattice is required for private CA support; the managed option lets AgentCore Identity create and manage the necessary Lattice resources.
- Integration works with any private CA (enterprise, third‑party, or self‑signed), demonstrated using AWS Private CA and Keycloak.
- The CA certificate must be a root or intermediate certificate; only the public part is stored—no private key is required.
Engineers can now connect Bedrock agents to internal, TLS‑secured identity providers without exposing private keys or re‑architecting authentication flows, accelerating secure enterprise deployments.
✅ Practical Steps
- Store your private CA’s PEM‑encoded certificate in AWS Secrets Manager or Amazon S3.
- Create an AgentCore Identity credential provider that points to your IdP endpoints and references the stored CA certificate.
- Deploy the agent on AgentCore Runtime; AgentCore Identity will route IdP calls through VPC Lattice, validate the load balancer’s private certificate, and return OAuth 2.0 tokens to the agent.
Want the full story? Read the original article.
Read on AWS ML Blog ↗