Automating AWS Agent Registry updates with push-based architecture
This post shows how to keep the AWS Agent Registry current automatically. Using AWS CloudTrail, Amazon EventBridge, AWS Lambda, and AgentCore Identity, an event-driven pipeline detects MCP server changes and pushes updated tool metadata to the registry with no stored secrets, across single- and multi-account environments.
First seen by Oriel on .
AI summary
AWS presents an event-driven, push-based architecture that automatically synchronizes MCP server tool schemas with existing AWS Agent Registry records after runtime updates.
- AWS CloudTrail captures UpdateAgentRuntime calls, and Amazon EventBridge routes them to an AWS Lambda function, including cross-account forwarding to a central registry account.
- The Lambda constructs the MCP invocation endpoint from the runtime ARN, authenticates through AgentCore Identity, then calls initialize and tools/list to retrieve current definitions.
- The function matches an APPROVED registry record using the decoded ARN, encoded ARN, or full MCP URL, then compares normalized tool names, descriptions, and inputSchema values.
- Updates arrive after CloudTrail’s approximately 5–15-minute delivery delay, and the sample updates only pre-registered records rather than creating new ones.
- Credential providers can be configured per account, allowing one Lambda function to authenticate MCP servers distributed across multiple AWS accounts.
#aws agent registry #model context protocol #event-driven architecture #aws lambda
Generated by gpt-5.6-sol. Check the original for details.
Aliases
| Source | External ID | URL |
|---|---|---|
| AWS Machine Learning Blog | eee5d43fead189e55bac9d295c979e1d24fbb7ff | https://aws.amazon.com/blogs/machine-learning/automating-aws-agent-registry-updates-with-push-based-architecture/ Read discussion |