# Amazon — Automating AWS Agent Registry updates with push-based architecture

- Company: Amazon (amazon.com)
- Announced: 2026-11-11T20:52:48+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/automating-aws-agent-registry-updates-with-push-based-architecture/
- Record: https://forck.live/items/34851-automating-aws-agent-registry-updates-with-push-based-architecture
- Subject: Bedrock / Nova

Amazon's guide shows how to keep AWS Agent Registry records current by wiring CloudTrail, EventBridge and Lambda into a push-based sync for MCP servers. The problem it addresses is staleness: when an MCP server gains a tool or changes its schema, the registry record must be updated or consumers discover outdated metadata. The post says stale metadata reduces registry reliability and pushes teams toward hardcoded endpoints, informal knowledge sharing and stale documentation. The pipeline captures UpdateAgentRuntime API calls in CloudTrail, routes them through EventBridge to a Lambda in the registry account, which authenticates through AgentCore Identity, calls the MCP server's initialize and tools/list, diffs the result and updates the matching record. CloudTrail records the event as a management event with a delivery delay of approximately 5–15 minutes. The sample uses two accounts, with the registry account owning the registry, EventBridge rule, Lambda and CloudTrail logs, and the MCP server account hosting the runtime and Cognito OAuth provider; a single-account setup skips cross-account forwarding. The Lambda updates existing records only and does not create new ones, so the MCP server must already be pre-registered.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/automating-aws-agent-registry-updates-with-push-based-architecture/:

> Every time a Model Context Protocol (MCP) server published in the AWS Agent Registry, a capability of Amazon Bedrock AgentCore, gains a new tool or updates its schema, the registry record must be updated too. Without automated push-based sync, consumers discover stale metadata. For organizations managing multiple MCP servers across accounts, such a sync keeps catalog records current within an existing governance workflow.
> 
> In most enterprise deployments, a catalog’s value depends on its freshness. If a developer deploys a new tool on Monday, but the registry record still reflects last week’s schema, consumers lose trust in the catalog. Stale metadata directly reduces registry reliability, leading teams to inadvertently build dependencies on inaccurate information.
> 
> When an engineer adds a tool to an MCP server but forgets to update the catalog:
> 
> Consumers miss out on the new capability entirely.
> 
> Applications might call the tool using an outdated schema, causing unexpected runtime behavior or silent workflow deviations.
> 
> Multiplied across teams, this lack of automation erodes trust in the registry.

---

Record: https://forck.live/items/34851-automating-aws-agent-registry-updates-with-push-based-architecture
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
