AWS Agent Registry and AWS Organizations
AWS Agent Registry is a fully managed discovery service. It provides a centralized catalog for organizing, curating, and discovering resources across your organization. With AWS Agent Registry, you can publish Model Context Protocol (MCP) servers, tools, agents, agent skills, and custom resources into a searchable registry. You can control access through an approval workflow. Both human users and AI agents can then discover the right tools and agents through hybrid search, catalog browsing, and a native MCP endpoint.
With AWS Agent Registry, you can automatically discover and catalog supported resources (currently Amazon Bedrock AgentCore Runtimes and Gateways) across member accounts, giving you a single organization-wide catalog with no per-account setup. The catalog stays in sync as resources and accounts change, and detection is fully managed with nothing to install in member accounts. For more information, see Using AWS Agent Registry with AWS Organizations in the Amazon Bedrock AgentCore Developer Guide.
Use the following information to help you integrate AWS Agent Registry with AWS Organizations.
Service-linked roles created when you enable integration
The following service-linked role is automatically created in your organization's management account when you enable trusted access. This role allows AWS Agent Registry to perform supported operations within your organization's accounts in your organization.
You can delete or modify this role only if you disable trusted access between AWS Agent Registry and Organizations, or if you remove the member account from the organization.
For more information, see Using service-linked roles for AWS Agent Registry in the Amazon Bedrock AgentCore Developer Guide.
-
AWSServiceRoleForAgentRegistry– Allows AWS Agent Registry to access AWS services and resources used or managed by AWS Agent Registry on your behalf.
Service principals used by AWS Agent Registry
The service-linked role in the previous section can be assumed only by the service principals authorized by the trust relationships defined for the role. The service-linked roles used by AWS Agent Registry grant access to the following service principals:
-
agent-registry.amazonaws.com
Enabling trusted access with AWS Agent Registry
For information about the permissions needed to enable trusted access, see Permissions required to enable trusted access.
When you grant trusted access for AWS Agent Registry to your AWS Organization, the service gains permission to create AWS Config service-linked configuration recorders in member accounts. These recorders obtain information about active resources and notify AWS Agent Registry of create, update, and delete events. AWS Agent Registry then creates, updates, or deletes registry records according to these events using the credentials of the registry owner.
You can enable trusted access using either the AWS Agent Registry console or the AWS Organizations console.
Important
We strongly recommend that whenever possible, you use the AWS Agent Registry console or tools to enable integration with Organizations. This lets AWS Agent Registry perform any configuration that it requires, such as creating resources needed by the service. Proceed with these steps only if you can’t enable integration using the tools provided by AWS Agent Registry. For more information, see this note.
If you enable trusted access by using the AWS Agent Registry console or tools then you don’t need to complete these steps.
To enable trusted access from the AWS Agent Registry console, see Using AWS Agent Registry with AWS Organizations in the Amazon Bedrock AgentCore Developer Guide.
You can enable trusted access by using either the AWS Organizations console, by running a AWS CLI command, or by calling an API operation in one of the AWS SDKs.
Disabling trusted access
For information about the permissions needed to disable trusted access, see Permissions required to disable trusted access.
To disable trusted access from the AWS Agent Registry console, see Using AWS Agent Registry with AWS Organizations in the Amazon Bedrock AgentCore Developer Guide. All delegated administrators must be removed before you can disable trusted access.
You can disable trusted access using either the AWS Agent Registry or the AWS Organizations tools.
Important
We strongly recommend that whenever possible, you use the AWS Agent Registry console or tools to disable integration with Organizations. This lets AWS Agent Registry perform any clean up that it requires, such as deleting resources or access roles that are no longer needed by the service. Proceed with these steps only if you can’t disable integration using the tools provided by AWS Agent Registry.
If you disable trusted access by using the AWS Agent Registry console or tools then you don’t need to complete these steps.
You can disable trusted access by running a Organizations AWS CLI command, or by calling an Organizations API operation in one of the AWS SDKs.
Enabling a delegated administrator account for AWS Agent Registry
A delegated administrator for AWS Agent Registry can create and manage registries with organization-wide auto-detection on behalf of the organization, without using the management account. For more information, see Using AWS Agent Registry with AWS Organizations in the Amazon Bedrock AgentCore Developer Guide.
Minimum permissions
Only an administrator in the Organizations management account can configure a delegated administrator for AWS Agent Registry.
Disabling a delegated administrator account for AWS Agent Registry
Only an administrator in the Organizations management account can remove a delegated
administrator account from the organization. You can remove a delegated administrator using the AWS Agent Registry
console, or by using the Organizations DeregisterDelegatedAdministrator CLI or SDK
operation. To remove a delegated administrator using the AWS Agent Registry console, see
Using
AWS Agent Registry with AWS Organizations in the Amazon Bedrock AgentCore
Developer Guide.
