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.
When a developer updates an MCP server in Account B, it triggers the UpdateAgentRuntime API in Amazon Bedrock AgentCore. This event is captured by AWS CloudTrail and stored as a management event. The event is then forwarded to Account A's EventBridge bus through a cross-account rule. In Account A, a Lambda function is triggered by the event and extracts the MCP server ARN from the event payload.
It then constructs the MCP server's invocation URL. The Lambda authenticates with a secure OAuth bearer token obtained from AgentCore Identity. Next, it fetches the latest tools information from the MCP server using the API and compares it with the existing registry record. If changes are detected, the Lambda updates the registry record in Account A. This automated process ensures that MCP server updates are reflected in the AWS Agent Registry in real-time, providing fresh metadata for consumers and reducing the risk of building dependencies on stale or inaccurate information.
Written by urgent.news from AWS Machine Learning's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
