[Update] Records Linked to a Domain in AWS Agent Registry Can Now Be Published Outside the Organization

[Update] Records Linked to a Domain in AWS Agent Registry Can Now Be Published Outside the Organization

I tried out the new AWS Agent Registry feature! By linking a domain to a record, you can publish agents and MCP servers so people outside your organization can discover them too.
2026.11.22

This page has been translated by machine translation. View original

Introduction

Hello, I'm Jinno from the Consulting Department, and I love supermarkets.

On November 20, 2026, AWS Agent Registry gained the ability to link a verified domain to a record and publish it outside your organization!

https://aws.amazon.com/about-aws/whats-new/2026/11/agent-registry-naming-public-discovery/

What's good about it... what kind of update is this...?
I didn't understand it at first...

It seems to be a feature that lets people outside your organization (your own AWS account) discover your company's MCP servers and agents. I see, a feature for publishing publicly...!

In my previous article, I searched for an A2A agent in my own Registry and called it, but it looks like that search scope could be extended beyond the organization if you wanted.

https://dev.classmethod.jp/articles/aws-agent-registry-dynamic-a2a-strands-agents/

Let's dig a little deeper into scenarios where it seems useful...!

Scenarios where it seems useful

Published records can be searched from other accounts or organizations as long as they have AWS credentials, so it seems usable in scenarios like these:

  • SaaS or tool providers use it as a gateway for customers to discover their MCP servers and agents
  • Agents in separate AWS accounts or organizations, such as business partners or subsidiaries, find and connect with each other

Is it handy when a trusted organization or provider says, "Come connect here and do whatever agent integration you like!"...
At this point, I personally haven't fully grasped how this feature will develop...??

What kind of setup is needed

The publishing side first sets up something called a publisher, an unfamiliar term. It's a setting that represents the identity of the issuer. (Hereafter, "publisher")

It holds one domain whose ownership has been confirmed via DNS, and the records you publish are associated with this publisher, so the searcher sees this domain as the provider.

Here's an image of the relationship between the provider and the user.

The provider associates a record with a publisher whose domain has been verified and approves it, and then an agent of a customer or business partner can find it from another account via public search. They can verify the provider by the domain in the results before connecting

Flow up to publishing

It isn't the case that things are suddenly published publicly; you can publish after going through the following 3 steps.

  1. Create a publisher with a registered domain and verify ownership with a DNS TXT record
  2. Associate an approved record with the publisher
  3. Approve the association

The flow up to publishing. Create a publisher and verify the domain with a DNS TXT record, and it becomes ACTIVE. Once a record is registered and approved, it can be searched within the organization; when it is associated with an ACTIVE publisher and the association is approved, it appears in public search

There are two approvals! Well, it would be scary if things were suddenly made public...
Approving a record makes it searchable within the organization, and approving the association then makes it a target of public search.

https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-public-discovery.html

At present there is no additional charge, and it is available in all Regions where Registry can be used. The endpoints that the searching side calls are in three locations: N. Virginia, Ireland, and Tokyo.

Prerequisites

I'll proceed with verification under the following prerequisites!

  • Region
    • N. Virginia (us-east-1)
  • I use a Route 53 public hosted zone. The domain in the article is replaced with example.com, and account IDs and resource IDs are replaced with example values
  • AWS CLI 2.42.0, jq (used to create the JSON for registering records)

Trying it out

Now, let's try it right away!

Create a publisher and verify the domain

First, create a publisher by specifying a domain.

Create publisher
export AWS_REGION=us-east-1
aws agent-registry-control create-publisher \
  --value '{"domain": "example.com"}'
Execution result (excerpt)
{
    "value": {
        "domain": "example.com"
    },
    "identifierType": "DOMAIN",
    "status": "ACTION_REQUIRED",
    "domainChallenge": {
        "recordName": "_acme-challenge.example.com",
        "recordValue": "aws-ard:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
    },
    "publisherArn": "arn:aws:agent-registry::123456789012:publisher/domain/example.com/0123456789abcdef"
}

Create a TXT record using the name and value in domainChallenge. This time I added it to Route 53.

Add TXT record
cat > txt-change.json <<'EOF'
{"Changes": [{"Action": "CREATE", "ResourceRecordSet": {
  "Name": "_acme-challenge.example.com", "Type": "TXT", "TTL": 60,
  "ResourceRecords": [{"Value": "\"<recordValueの値>\""}]}}]}
EOF

aws route53 change-resource-record-sets \
  --hosted-zone-id <ホストゾーンID> --change-batch file://txt-change.json

When I ran validate-publisher, which requests re-verification, right after adding it, it returned Verification already in progress. Registry checks DNS periodically, so simply waiting was fine.

Check status
aws agent-registry-control get-publisher \
  --publisher-arn <パブリッシャーARN> --query status --output text
Execution result
ACTIVE

It became ACTIVE in under a minute after creation!

Associate a record and approve it

The steps to create a registry and to register and approve an MCP server record are the same as before.

Create a registry and record

I put a dummy endpoint for verification in the record. Because Registry is a mechanism that holds metadata, you can verify through to publishing even if the endpoint isn't actually running.

server.json
{
  "name": "com.example/weather-forecast",
  "description": "指定した都市の天気予報を返すMCPサーバー(検証用のサンプル)",
  "version": "1.0.0",
  "remotes": [{"type": "streamable-http", "url": "https://weather.example.com/mcp"}]
}
Create and approve registry and record
aws agent-registry-control create-registry \
  --name public-discovery-test \
  --approval-configuration '{"autoApprovalRules": []}'
aws agent-registry-control wait registry-ready --registry-id <レジストリID>

jq -n --rawfile s server.json '{mcpServer: {data: $s, dataSchemaVersion: "2025-12-11"}}' > descriptors.json

aws agent-registry-control create-registry-record \
  --registry-id <レジストリID> \
  --name weather-forecast --display-name "Weather Forecast" \
  --description "指定した都市の天気予報を返すMCPサーバー(検証用のサンプル)" \
  --record-type MCP --record-version 1.0.0 \
  --descriptors file://descriptors.json

# Creation is asynchronous, so request approval after the status becomes DRAFT
aws agent-registry-control get-registry-record \
  --registry-id <レジストリID> --record-id <レコードID> --query status --output text

aws agent-registry-control submit-registry-record-for-approval \
  --registry-id <レジストリID> --record-id <レコードID>
aws agent-registry-control update-registry-record-status \
  --registry-id <レジストリID> --record-id <レコードID> \
  --status APPROVED --status-reason "public discovery test"

Just to be safe, I checked, and trying to associate a record that is still an unapproved draft (DRAFT) was rejected with Record cannot be associated while in DRAFT state.
So it doesn't get suddenly published, which is good.

Now let's approve it and then associate it.

Associate with publisher
aws agent-registry-control associate-publisher \
  --record-arn <レコードARN> \
  --publisher-arn <パブリッシャーARN> \
  --categories weather
Execution result
{
    "recordArn": "arn:aws:agent-registry:us-east-1:123456789012:registry/AbCdEfGh12345678/record/AbCdEf123456",
    "publicIdentifier": "urn:air:example.com:weather/weather-forecast:mcp",
    "publisher": "arn:aws:agent-registry::123456789012:publisher/domain/example.com/0123456789abcdef",
    "status": "PENDING_APPROVAL"
}

A public name (publicIdentifier) was issued.
In the value returned this time, the domain is followed by the category, record name, and type (mcp).

An example of the public name returned this time. After urn:air: come the verified domain, category (optional), record name, and type

Right after association, public search returned 0 results. Next, approve the association.

Approve association
aws agent-registry-control update-publisher-association-approval-status \
  --record-arn <レコードARN> \
  --approval-status APPROVED \
  --approval-status-reason "public discovery test"

Public search is run with the agent-discovery command.

Public search
aws agent-discovery search-public-records \
  --search-query "天気予報を返すMCPサーバー"
Execution result (excerpt)
{
    "records": [
        {
            "identifier": {
                "uri": "urn:air:example.com:weather/weather-forecast:mcp"
            },
            "displayName": "Weather Forecast",
            "description": "指定した都市の天気予報を返すMCPサーバー(検証用のサンプル)",
            "recordType": "TOOL",
            "domain": "example.com",
            "descriptors": {
                "mcpServer": {
                    "data": "{\n  \"name\": \"com.example/weather-forecast\", ... \"url\": \"https://weather.example.com/mcp\"}]\n}\n",
                    "version": "2025-12-11"
                }
            },
            "recordVersion": "1.0.0"
        }
    ]
}

It showed up about 30 seconds after approval!

The verified domain is in domain, so the searching side can verify the provider with this value.

The endpoint URL is also included as is in the descriptor. An MCP server record was returned with the type TOOL in public search.

I also ran the same search from a different AWS account.

Search from another account
AWS_PROFILE=<別アカウントのプロファイル> aws agent-discovery search-public-records \
  --search-query "天気予報を返すMCPサーバー" \
  --query 'records[].[identifier.uri, domain, displayName]' --output text
Execution result
urn:air:example.com:weather/weather-forecast:mcp	example.com	Weather Forecast

It was found even from an account that doesn't share the registry! The record published in N. Virginia could also be searched from the Tokyo (ap-northeast-1) and Ireland (eu-west-1) endpoints.

Stop publishing

Disassociating removes it from public search.

Remove association
aws agent-registry-control disassociate-publisher --record-arn <レコードARN>

About 10 seconds after disassociation, public search returned 0 results. The record remains APPROVED and can still be found in searches of your own registry.

Looking for records that are public as of today

I wondered whether anyone is already making full use of this feature and publishing, so I searched as of November 22, 2026.

Find public records
aws agent-discovery search-public-records \
  --search-query "MCP server" --max-results 100 \
  --query 'records[].[identifier.uri, recordType, domain]' --output text
Execution result (as of 17:50 on November 22, 2026)
urn:air:eventplanner.net:eventplanner-net-bot:webbot	WEB_BOT	eventplanner.net
urn:air:optinstack.com:OptinStack-Bot:webbot	WEB_BOT	optinstack.com
urn:air:eventplanner.net:eventplanner-net-preview:webbot	WEB_BOT	eventplanner.net

Three were found, and all were records of bots that sign HTTP requests (WEB_BOT). No MCP server or agent records were found...
Even when I changed the query to "weather forecast" or "payment", the same 3 were returned, so it seems there are still few public records.

Cleanup

Delete the record and registry, and then delete the publisher and the TXT record.

Cleanup
aws agent-registry-control delete-registry-record \
  --registry-id <レジストリID> --record-id <レコードID>
aws agent-registry-control delete-registry --registry-id <レジストリID>

aws agent-registry-control delete-publisher --publisher-arn <パブリッシャーARN>

# Change the Action in txt-change.json to DELETE and run
aws route53 change-resource-record-sets \
  --hosted-zone-id <ホストゾーンID> --change-batch file://txt-change.json

Conclusion

You can now link agents and tools to a verified domain and publish them publicly!

Being able to publish to third parties is convenient, but we should be careful about accidents such as inadvertently including internal descriptions or endpoints. On the user side as well, we should check the verified domain and avoid using anything from an unfamiliar provider...
I don't know whether this feature will become widespread, but if there are updates or use cases, I'd like to verify them!

I hope this article was at least a little helpful! Thank you for reading to the end!

Share this article