Understand this story
On October 21, 2026, AWS presented a solution for securing AI agent identities using Keyfactor EJBCA combined with AWS services. According to an article published by AWS Machine Learning, AWS and Keyfactor jointly released a reference architecture that uses Keyfactor EJBCA's X.509 PKI to establish verifiable, revocable cryptographic identities for AI agents, filling the gap left by MCP's lack of a built-in authentication standard. The solution combines Amazon Bedrock, the AWS Strands Agents SDK, AWS Secrets Manager, and Amazon RDS, and covers three trust boundaries—user authentication, agent-to-agent communication, and MCP tool invocation—through four layers of mechanisms: signed request envelopes, user-signed delegation assertions, RFC 8693 audience-restricted tokens, and real-time OCSP revocation checks. Currently, the solution is presented publicly only as a reference architecture, and there are no public facts regarding subsequent implementation progress.
AI-generated from public reports
Latest development · Report
How AWS Uses X.509 PKI to Secure AI Agent IdentityDevelopments
1 confirmed developments
AWS presents: Securing AI agent identities with Keyfactor EJBCA and AWS services
Source:AWS Machine Learning
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Oct 21
AWS Machine LearningFirst-party
How AWS Uses X.509 PKI to Secure AI Agent Identity
AWS and Keyfactor jointly released a reference architecture that uses Keyfactor EJBCA's X.509 PKI to establish verifiable, revocable cryptographic identities for AI agents, filling the gap left by MCP's lack of a built-in authentication standard. The solution combines Amazon Bedrock, the AWS Strands Agents SDK, AWS Secrets Manager, and Amazon RDS, and covers three trust boundaries—user authentication, agent-to-agent communication, and MCP tool invocation—through four layers of mechanisms: signed request envelopes, user-signed delegation assertions, RFC 8693 audience-restricted tokens, and real-time OCSP revocation checks.