Documentation / AWS Agent Registry

Connect AWS Agent Registry

Early access. Meridian lists agents in one AWS account and region. The daily read posts mapping records only when dry-run is turned off. You create a read-only role. Meridian does not store an access key.

See AWS Agent Registry Now Feeds Onaro Meridian.

1. Create the registry record

The agent card must include protocolVersion set to "0.3.0" andpreferredTransport. Without both, CreateRegistryRecord fails with “does not match any supported version”.

A new record starts as DRAFT. Meridian still lists and previews DRAFT records. Leave the record in DRAFT for this read. Approving it is a separate step and is not required for the Settings preview.

Put the owner's email in a tag named oasa-owner, or in custom metadata text of the same name. When that email matches exactly one member and Meridian's owner is blank, the daily read fills the owner. Zero matches or more than one match keeps the email beside the agent. An owner you set in Meridian wins. A tag namedoasa-department fills a blank department the same way.

2. Connect the account

Open AWS Agent Registry in Settings. Enter the 12-digit account id and the region, then choose Connect. The card shows an external ID, a trust policy, and a permissions policy.

In that account, create a role named MeridianAgentRegistryRead. Attach the trust and the permissions from the card. The trust names the broker shown on the card and requires the external ID. Staging's broker ismeridian-agent-registry-broker-staging. Production's broker ismeridian-agent-registry-broker. Use the one the card shows.

The role can list and get registries and records, and list tags. It cannot create or approve records. ListRegistries has no resource type, so that statement uses *.

3. Check and preview

Choose Check connection. The four checks are the account, the broker, the customer role, and registries. Preview then shows each record's display name, theoasa-owner email, and whether Meridian would assign that owner. While dry-run is on, preview writes nothing.

Stop import skips this account on the next daily read. Resume import runs the check again and starts the read when the check passes. Disconnect clears the saved account in Meridian. It does not change AWS.

For owners and departments, see Agent ownership and cost attribution.

Troubleshooting

The service account is not configured yet. The API reads onlyGCP_SERVICE_ACCOUNT_INFO. That value must be the runtime account for this environment: onaro-staging-runtime on staging, andonaro-api-runtime on production. The KMS key andGOOGLE_APPLICATION_CREDENTIALS are different accounts and are not used for this read.

The request was signed for the wrong AWS service. Onaro signs agent-registry.The host stays agent-registry-control in the region. The SigV4 service name is agent-registry. A customer policy change does not fix this.

The broker role refused the Google token. The runtime account's token did not match the broker trust. Staging usesmeridian-agent-registry-broker-staging. Production usesmeridian-agent-registry-broker. The audience condition, when it is locked, is the runtime account email, not the numeric unique ID.

The customer role MeridianAgentRegistryRead refused the assume. Check that its trust names the broker and the external ID.The role must exist in the account on the card, its trust must name the broker the card shows, and the external ID must match the card. A 403 from a read the role is allowed to make is reported as this refusal.