AWS Distro for OpenTelemetry

AWS Distro for OpenTelemetry (ADOT) collects logs, metrics, and traces from applications and connects them with infrastructure information. Applications can be instrumented once to send correlated telemetry to one or more observability backends, while auto-instrumentation can generate traces without changes to application code. ADOT collects metadata from AWS resources and managed services. Documented destinations include Amazon Managed Service for Prometheus, Amazon CloudWatch, AWS X-Ray, Amazon OpenSearch, OTLP-compliant backends, and Amazon MSK. It supports applications on AWS App Runner, Lambda, EC2, ECS, EKS on EC2, Fargate, and on-premises datacenters. Getting-started guides cover Go, Java, JavaScript, Python, Ruby, .NET, PHP, and Android. The project describes ADOT as secure and production-ready, with AWS Support, testing, and certification. It contributes changes and fixes to the OpenTelemetry community. ADOT is free under the Apache-2.0 license; the download page lists Collector version 0.50.0, released August 25, 2026.

ADOT brings application telemetry and AWS resource metadata together, with deployment options spanning AWS and on-premises datacenters. Its free Apache-2.0 distribution is worth considering when its documented backends and supported environments fit your setup.

ADOT suits developers and operations teams collecting application telemetry across AWS and on-premises environments. It may also suit teams working with any of its documented backends or SDK languages.

Overview

AWS Distro for OpenTelemetry (ADOT) is an AWS-supported distribution for collecting application logs, metrics, and traces. It is best suited to teams running services across AWS and on-premises environments that want shared instrumentation and AWS resource context. Its strongest case is the combination of AWS deployment coverage and OpenTelemetry-based routing, though its documented Collector release should fit your version requirements.

Key features

ADOT handles logs, metrics, and traces, with support for transform rules, data enrichment, and multi-destination routing. That gives teams room to shape telemetry and send it to more than one destination instead of treating collection as a one-way handoff. Applications can be instrumented once and send correlated telemetry to one or multiple observability backends, a useful way to avoid binding instrumentation to a single vendor.

Auto-instrumentation can generate traces without changes to application code, which helps when modifying individual services is difficult. ADOT also gathers metadata from AWS resources and managed services to connect application performance with infrastructure context. That extra context is valuable in AWS-heavy environments, but less compelling for teams whose infrastructure is mostly elsewhere.

Documented backends include Amazon Managed Service for Prometheus, Amazon CloudWatch, AWS X-Ray, Amazon OpenSearch, Amazon MSK, and OTLP-compliant destinations. AWS teams have several native landing points, while OTLP support leaves a path to compatible backends. The SDK getting-started guides cover Go, Java, JavaScript, Python, Ruby, .NET, and PHP; Android also has a getting-started guide.

Deployment support spans AWS App Runner, Lambda, EC2, ECS, EKS on EC2, and Fargate, as well as on-premises datacenters. The project describes ADOT as secure and production-ready, backed by AWS Support, testing, and certification. It follows an upstream-first approach, contributing enhancements, changes, and fixes to the OpenTelemetry community. The download page lists Collector version 0.50.0, released August 25, 2026, under the Apache-2.0 license; teams standardizing on a different release should treat version fit as a practical checkpoint.

Pricing

ADOT is free: the AWS Distro for OpenTelemetry plan costs nothing and is an Apache-2.0 licensed distribution. There are no paid tiers to trade off against the free offering. For teams seeking an open-source collector distribution, that removes a software license charge, though the choice still depends on supported environments, backends, and release fit.

Platforms

ADOT lists Android, API, Linux, self-hosted, and Windows platforms, with deployment options across AWS services and on-premises datacenters. That range suits mixed estates better than a tool tied to a single cloud runtime; the value is clearest when the named AWS environments or Android guide match your workload.

Who it's for

Choose ADOT if you need OpenTelemetry collection across AWS and on-premises systems, want AWS resource metadata correlated with application telemetry, or need to route to several documented AWS and OTLP-compatible backends. It is a weaker fit when your required runtime or destination falls outside its documented coverage, or when the listed Collector version does not align with your release policy.

Pros and cons

• Pro: Free Apache-2.0 distribution avoids a product license charge while keeping logs, metrics, and traces in scope.
• Pro: AWS metadata enrichment and deployment choices across managed services and on-premises datacenters suit mixed AWS estates.
• Pro: One-time instrumentation, auto-generated traces, and multi-destination routing support flexible telemetry pipelines.
• Con: The named backends and environments define the practical boundaries; teams should confirm their destinations and runtimes are covered.
• Con: Collector version 0.50.0 may not suit teams with a different release standard.

Alternatives

For a broader comparison, see Telemetry Pipeline Software.

• Honeycomb is worth considering when its free plan's monthly allowances of 20M events and 100M metrics data points, plus two triggers, match your needs, or when you want a freemium observability product with a free trial.
• Bindplane may fit teams prioritizing collector and project allowances: its free tier includes unlimited collectors, one user, 10 projects, and 100 GB/day of combined telemetry.
• Cribl Stream is an alternative for teams wanting up to 1TB/day, unlimited pipelines and routes, and community support on its free plan.
• Grafana k6 is a different option for Linux users focused on load testing, with a free plan capped at 500 virtual user hours per month.
• rsyslog is another Linux, self-hosted, and Windows option; its core programs are released under GPLv3, with some runtime files under LGPL.
• Amazon OpenSearch Ingestion suits teams seeking a paid ingestion service billed hourly with per-minute granularity for allocated ingestion OCUs.
• Cribl Edge may suit teams that want edge-node coverage, with its free plan allowing up to 1TB/day, 100 Edge Nodes, and one Fleet.
• Edge Delta is another telemetry-oriented alternative.

Verdict

ADOT is a strong choice for teams that want a free, open-source OpenTelemetry distribution spanning AWS services and on-premises systems, especially when AWS metadata and multiple destinations matter. Its principal reason to choose it is that AWS context and broad deployment support sit alongside standard telemetry collection; look elsewhere if your required backend, runtime, or Collector release does not fit.