AWS Bedrock

Agent Management discovers Bedrock AgentCore Harnesses and Runtimes in the AWS region configured on the connection.

Connection and discovery

Use a Bedrock Agents connection with AWS credentials and a region. The credentials must allow listing and reading the relevant Bedrock resources. Log collection requires access to their CloudWatch Logs; platform metrics require access to CloudWatch metrics. Uptime tests and agent reviews also require permission to invoke the agent.

Supported capabilities

  • Inventory and structure: AgentCore Harnesses expose configuration, models, tools, and deployment metadata. Runtime metadata is limited to configuration and deployment information.

  • Interaction logs, traces, tokens, and cost: supported for AgentCore Harnesses and Runtimes using the HTTP protocol, with an identified CloudWatch log group and compatible telemetry.

  • Platform metrics: AgentCore metrics require an identified backing Runtime ARN, Runtime name, and endpoint name.

  • Uptime tests and agent reviews: invocation is supported for AgentCore Harnesses, and HTTP Runtimes.

  • Usage: AgentCore telemetry can provide conversation counts. Active-user metrics are unavailable.

Limitations and platform actions

non-HTTP AgentCore Runtimes can appear in the inventory without supporting interaction-log collection or cost attribution.

Agent Management can disable and re-enable AgentCore Runtimes. Disabling a Runtime blocks new invocations across all its endpoints, including DEFAULT, while preserving the Runtime, versions, and endpoints. It does not guarantee that running sessions terminate immediately.

Stopping an AgentCore Harness permanently deletes the Harness parent and makes its endpoints unusable. Its managed memory remains as independent AWS resources. Agent Management cannot re-enable the deleted Harness.