An external agent is a third-party agent you register on the platform so it can be used like a native one — for example to reuse an agent that already runs in another system.
Overview
External agents are added today via Amazon Bedrock — the platform reads the Bedrock agent's configuration and makes it available here. They appear in the AI Agents manager with the External type. (The Agent-to-Agent — A2A — protocol is used for the reverse direction: exposing this platform's own agents to outside callers, via A2A Servers.)
Adding an External Agent
From the AI Agents manager's create dropdown, choose Add External AI Agent from Bedrock. That opens the New External AI Agent form — "Integrate a third-party AI Agent to leverage it's capabilities on the platform." Fill it in:
Under Connect Agent via Bedrock, choose an Amazon Bedrock Connection (or create one).
Pick the Agent from the list of agents available in that connection.
Optionally, set a Display Name — the name used for the agent once it's integrated.
Under Configure Agent, choose a Latency: Standardised (balanced performance and cost, the default) or Optimised (faster responses in latency-sensitive apps).
Click Create.
Once added, it's managed like any other agent.
Viewing and Configuring an External Agent
Open the external agent and use its Overview tab — external agents show Overview in place of the usual Configuration tab. Basic Details shows the agent as received from Amazon Bedrock: its Provider, Connection, Agent, Added By, and Last Updated By. These details are read-only. The only setting you can change here is Latency under Configure Agent (Standardised or Optimised), and it saves automatically.
What It Can Do Once Connected
A connected external agent is invoked through the platform like an internal one — including as a member of an AI team, where the team manager can delegate to it. This lets you compose internal and external agents together without rebuilding the external one on the platform.