Monitor on-premises and multi-cloud AI agents with AgentCore Observability
Amazon Web Services
Anthropic
Amazon Bedrock AgentCore Observability now supports agents running outside AWS, such as on-premises or on other clouds. This post shows how to use AWS Distro for OpenTelemetry (ADOT) auto-instrumentation to route telemetry to CloudWatch, enabling centralized monitoring for agents deployed in non-AWS environments.
The post explains how to set up observability for AI agents running outside AWS using ADOT auto-instrumentation. The solution routes telemetry to the Amazon CloudWatch OTLP endpoint with SigV4 authentication, using IAM credentials. The setup requires three components: ADOT auto-instrumentation, IAM credentials, and environment variables. The walkthrough uses a Strands agent, but the pattern applies to other OpenTelemetry-compatible frameworks like LangGraph and CrewAI. The solution was validated in an on-premises simulated environment and on Google Cloud Shell. The console displays sessions, traces, span metrics, token usage, and latency in the AgentCore Observability dashboard. The post also compares telemetry collection and credential management between non-AWS runtimes and AgentCore runtime, and provides best practices such as consistent naming and verifying credentials with get-caller-identity.
- Abbreviations
- EKS = Elastic Kubernetes Service — Эластичный сервис Kubernetes
- ECS = Elastic Container Service — Эластичный сервис контейнеров
- GCP = Google Cloud Platform — Облачная платформа Google
- ADOT = AWS Distro for OpenTelemetry — Дистрибутив AWS для OpenTelemetry
- OTLP = OpenTelemetry Protocol — Протокол OpenTelemetry
- SigV4 = Signature Version 4 — Версия подписи 4
- IAM = Identity and Access Management — Управление доступом и идентификацией
Source: AWS ML blog —
original
