AWS brings Agent Registry to GovCloud, with discovery limits
AWS Agent Registry is now generally available in AWS GovCloud (US-West), giving public-sector teams and their partners a managed catalog for finding AI agents, tools and reusable skills. AWS announced the regional expansion on November 6. The service had already reached general availability in commercial regions in August.
The useful change is a shared discovery and review process inside the new region. Teams still need to decide who may see each catalog and validate the software it points to. AWS’s documentation makes those boundaries particularly important for organizations handling restricted projects.
A catalog for finding resources
The service overview describes records for MCP servers, tools, agents, skills and custom resources. Consumers can combine natural-language and keyword search, browse approved entries or connect through a Model Context Protocol endpoint. IAM credentials or a corporate identity provider can govern discovery access.
Registry holds descriptions of resources. AgentCore Runtime runs agents and MCP servers, while AgentCore Gateway converts APIs and Lambda functions into tools. Finding an entry therefore leaves the separate question of whether a caller can connect to and use its underlying service.
Approval needs a review process
AWS’s review workflow lets curators inspect submitted records against their organization’s requirements, then approve or reject them. Publishers can correct and resubmit rejected records. This gives teams a place to make review decisions, but the quality of those decisions still depends on their own checks.
An auto-approval option makes submissions discoverable immediately and skips human review. AWS recommends limiting submitters, triggering automated checks through EventBridge and validating metadata on the consumer side when using it. Control-plane calls are logged as CloudTrail management events by default.
Removing an obsolete listing also needs care. Deprecation removes a record from discovery and the registry’s MCP endpoint while retaining it for control-plane auditing. It is a terminal state: the record cannot be edited or restored. Treat that as a catalog lifecycle decision, rather than a substitute for revoking access to a running service.
Search access covers the whole registry
The most consequential deployment detail is in the IAM permissions guide. Search and list operations authorize access at registry level. A caller with those permissions can discover every approved record, including entries denied through a GetDiscoverableRegistryRecord policy. The same rule applies to MCP search and list tools. Batch retrieval checks the individual record permissions.
That means catalog design should follow visibility requirements. As a practical example, a team that must conceal one project’s tool inventory from another should assess separate registries with separate discovery access. A denial on record retrieval alone should not be treated as a way to hide that record from search.
Check what each entry points to
AWS’s data-protection guidance says Registry validates metadata against its descriptor schema but does not verify referenced packages, repositories or endpoints. Consumers remain responsible for checking those references before an agent installs, downloads or connects to them.
AWS suggests approved package sources and pinned versions, allowed repository hosts and owners, and permitted endpoint schemes and domains. These checks make the distinction concrete: a well-formed catalog record can still point somewhere an organization has not approved for use.
Pricing and a sensible first deployment
AWS’s published Registry pricing lists monthly free allowances of 5,000 records, one million searches and two million combined list/get calls. Beyond those levels, the listed rates per 1,000 are $0.40 for records, $0.02 for searches and $0.004 for list/get calls. Resellers do not qualify for those allowances.
The GovCloud announcement does not separately specify regional rates or free-tier eligibility. Confirm the applicable billing terms before budgeting a deployment, along with charges for the services that actually run the agents.
A useful pilot would test three things: whether an unapproved entry stays out of discovery, exactly what each consumer can find, and what happens after a record is deprecated. Those checks address the catalog’s role without assuming it provides every downstream permission or compliance control. ByteForward has not independently tested the service.
For a separate approach to managing reusable agent instructions, our Google Agent Registry coverage explains revision packages and scanning controls. The two products share a name but their capabilities should be evaluated separately.
Featured image: AI-generated editorial illustration by ByteForward. AWS logo used for editorial identification. ByteForward is not affiliated with or endorsed by AWS.
