From the AWS edition of November 6, 2026
AWS Agent Registry generally available in AWS GovCloud (US-West) via Bedrock AgentCore for governed MCP, tool and agent catalogs
Amazon Web Services · Cloud platform / generative AI tooling / government cloud · United States (AWS GovCloud US-West Region as stated)
- Publisher
- AWS What's New
- Original publication
- 2026-11-06
- Source retrieved
- 2026-11-07
- Event date
- 2026-11-06
What happened
AWS says AWS Agent Registry, available through Amazon Bedrock AgentCore, is now generally available in the AWS GovCloud (US-West) Region. It is described as a fully managed discovery service and central catalog for organizing, curating and discovering MCP servers, tools, agents, agent skills and custom resources, with an approval workflow controlling what becomes discoverable. People and AI agents can find resources through hybrid search, catalog browsing and a native MCP endpoint. AWS pitches public sector organizations and partners for a single governed inventory, citing approval workflows and CloudTrail audit logs for compliance and oversight. The announcement does not state GovCloud (US-East) availability, pricing, measured adoption or independent compliance outcomes.
Why it matters
Directly relevant to SLED and partner teams already building agentic workloads in GovCloud (US-West) who need a governed inventory of agents and MCP tools rather than ad-hoc discovery.
Evidence and measured results
Primary AWS product announcement; vendor claims only. Supporting AgentCore registry documentation opened for workflow detail.
Limitations and uncertainty
GovCloud (US-West) only in this post; no US-East claim; no pricing; no SLED customer case; catalog does not equal runtime permission.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Public-sector AgentCore teams need a governed way to discover approved agents and MCP tools instead of tribal knowledge.
- Stakeholders
- Cloud platform owner
- CISO / security reviewer
- Agent application owner
- Partner integrator
- Discovery questions
- Is the workload already in GovCloud (US-West)?
- Who approves registry records for production discoverability?
- Does CloudTrail retention meet oversight requirements?
- Value hypothesis
- A managed registry may reduce duplicate agent/tool builds and strengthen oversight; compliance and cost are unproven here.
- Potential engagement
- Time-boxed non-production registry with curator workflow and a small approved catalog.
- Unsupported claims
- Automatic compliance from using the registry
- GovCloud (US-East) availability
- Pricing or TCO claims
Pre-sales engineering
Role takeaway
- Fit
- Strong fit for eligible GovCloud (US-West) AgentCore programs; not shown for commercial-only or US-East GovCloud accounts.
- Architecture and integration
- Create registry with IAM/JWT auth and approval settings; publish MCP/agent records; expose MCP endpoint to approved clients.
- Prerequisites
- Eligible GovCloud (US-West) account
- Bedrock AgentCore access
- Curator and publisher IAM roles
- CloudTrail enabled
- Constraints
- Announced only in GovCloud (US-West)
- Catalog is not runtime permission
- No price in announcement
- Security
- Vendor-claimed approval workflows and CloudTrail; independent audit evidence absent; treat catalog as discovery control only.
- Proof of value
- Rejected records are not discoverable in test
- CloudTrail contains approve/reject events
- Hybrid search returns only approved records
Delivery
Role takeaway
- Work
- Stand up non-prod registry, curator runbook and sample MCP/agent records.
- Dependencies
- AgentCore
- IAM or corporate JWT IdP
- CloudTrail
- Change-control board
- Ownership
- Platform team owns the registry; application teams publish; security owns approval criteria.
- Skills and adoption
- MCP record authoring, curator review discipline, IAM least privilege.
- Governance checkpoints
- Approval-policy sign-off
- Production discoverability gate
- Logging and retention review
- Acceptance criteria
- Proposed: no unapproved record is discoverable
- Proposed: audit events for every approve/reject
- Proposed: curator SLA met for pilot set
- Risks
- Shadow tools outside registry
- False sense of compliance
- Region mismatch for US-East workloads
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Central registry per account with IAM or JWT auth; publishers submit records; curators approve; consumers use search, catalog or MCP endpoint. Distinct from AgentCore Runtime hosting.
Governance
Who approves, reviews and stays accountable for outcomes?
Approval workflows and CloudTrail are positioned for oversight; agencies still define curation criteria, who may publish and what is production-discoverable.
Security and privacy
What data, permissions and controls need testing?
Vendor claims approval gating and CloudTrail support; cataloging a tool does not by itself deploy or authorize runtime use. Independent verification absent.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
None reported.
Procurement
What should contracts, pricing and exit terms secure?
No price stated in the announcement; confirm SKU and eligibility for GovCloud accounts.
Operating model
Which teams own the service once it runs?
Requires administrator, publisher and curator operating model before production discovery is enabled.
Publication history
- 2026-11-06AWS · Issue 095 resources
Stable resource ID: aws-agent-registry-govcloud-us-west-20261106