Skip to content

AgentCore Federation

Amazon Bedrock AgentCore

AgentCore Federation connects an external Amazon Bedrock AgentCore gateway to Jarvis Registry so platform admins can import and govern resources from one control plane.

This page focuses on the operational flow:

  1. Admin creates a federation connection in the UI.
  2. Registry syncs MCP servers and A2A agents from AgentCore.
  3. Admin reviews imported resources and shares them using the same ACL model used across the registry.

Federation Creation Flow

A federation starts with a simple creation form in Jarvis Registry.

Admins provide:

  • Federation Name — friendly name for the AgentCore source
  • Connection Settings — aws region and agentcore assume role
  • Resource Tags Filter — sync only specific tagged resources or sync all.

AgentCore Federation Create Form

After save, Jarvis Registry validates the connection and establishes the federation link.

Automatic Import from AgentCore

Once federation is active, Jarvis Registry can automatically pull resources from AgentCore.

Imported resources include:

  • MCP servers exposed by the federated AgentCore gateway
  • A2A agents available from the same federated source

The sync process normalizes external metadata into registry-native entries so they appear in the same catalog experience as local resources.

Admin Governance After Sync

Federated resources are not automatically open to all users. Admins still control visibility and access.

After sync, admins can:

  • Keep imported resources private for validation
  • Share with specific users or groups
  • Publish to everyone with VIEW access when ready

The sharing model is exactly the same as other resources in Jarvis Registry:

Security enforcement (authentication, RBAC, ACL) remains consistent for federated and local resources. See Security Control Design.

Next Steps