AIAIAI.FYI
LIVE

AWS adds private CA support to Amazon Bedrock AgentCore Identity for self-hosted identity providers

Agents can now trust a private certificate authority when calling IdPs such as Keycloak, using a PEM CA certificate stored in Secrets Manager or S3 and VPC Lattice for private access.

What happened

Many companies run their own login system, called an identity provider, inside a private network. These systems often use security certificates issued by the company's own certificate authority, a body that vouches for who a server is. AWS says its AgentCore Identity service can now trust that private authority.

Why it matters to you

Teams can let AI agents get access tokens from internal login systems without changing the agent code or moving the login system onto the public internet.

The takeaway

AI agents on AWS can now sign in to private company login systems that use in-house certificates.

What it means for you

If you build software

Set up a credential provider with certificateConfigurations, grant the caller secretsmanager:GetSecretValue or s3:GetObject, and alarm on the expiry metric before rotating the CA.

If you run a business

Companies that self-host Keycloak or PingFederate behind a private CA can connect AgentCore agents to them without replacing their existing certificate setup.

Get stories like this every morning