AIToday
Large Language ModelsAI Business & IndustryAmazon AI BlogPublished: Aug 14, 2026, 04:01 JST

AWS enables observability for AI agents running outside its cloud

AWS enables observability for AI agents running outside its cloud

3 Key Points

  1. What happened

    AWS released a capability to monitor AI agents built with frameworks like Strands Agents, LangGraph, and CrewAI running on-premises or on other clouds (Google Cloud Platform, Microsoft Azure). The solution uses AWS Distro for OpenTelemetry (ADOT) auto-instrumentation to capture telemetry and route it to Amazon Bedrock AgentCore Observability—a dashboard that displays agent reasoning chains, tool invocations, model outputs, and token usage.

  2. Why it matters

    Until now, Bedrock AgentCore Observability only worked natively for agents deployed on AWS. This extension lets organizations monitor agents anywhere without losing visibility into agent behavior, hallucinations, or token costs. For enterprises running multi-cloud or hybrid setups, this centralizes observability across environments.

  3. What to watch

    AWS provides a complete walkthrough using a Strands agent with Claude Haiku as the model. Telemetry appears in the CloudWatch console within two to three minutes; the setup requires IAM credentials, Python 3.10+, and outbound HTTPS access to AWS endpoints. AWS recommends using IAM Roles Anywhere for production to avoid long-lived access keys.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

AWS Bedrock AgentCore Observability has been limited to agents deployed natively on AWS infrastructure. This announcement removes that constraint by introducing a portable observability pipeline based on the AWS Distro for OpenTelemetry. The solution acknowledges that enterprises increasingly adopt multi-cloud strategies or maintain significant on-premises workloads; centralizing observability across these environments reduces operational friction.

The technical approach is straightforward: ADOT runs in-process with the agent application, automatically instrumenting boto3 calls to Amazon Bedrock and capturing spans from the agent framework itself. SigV4 authentication (AWS's signature mechanism) signed requests allow non-AWS environments to authenticate securely using IAM credentials. Telemetry flows to CloudWatch's native OpenTelemetry Protocol (OTLP) endpoint, where it is indexed and displayed in the AgentCore Observability dashboard. The architecture demonstrates AWS's effort to serve customers whose AI workloads span multiple cloud providers while funneling observability data back to AWS services.

FAQ
Which agent frameworks are supported?
The solution supports agents built with Strands Agents, LangGraph, and CrewAI. The ADOT auto-instrumentation patches the frameworks to emit OpenTelemetry traces following generative AI semantic conventions.
Where can agents run with this observability?
Agents can run on-premises, on Amazon EKS, Amazon ECS, AWS Lambda, Google Cloud Platform (GCP), Microsoft Azure, or any other environment with Python 3.10+ and outbound HTTPS access to AWS endpoints.
How long does it take for telemetry to appear in the dashboard?
Telemetry data appears in the AgentCore Observability dashboard within two to three minutes of agent execution.
Amazon AI BlogRead Original Article

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleApple researchers find some data points needn't be unlearned from AI models