// the find
aws-observability/aws-otel-collector
AWS Distro for OpenTelemetry Collector (see ADOT Roadmap at https://github.com/orgs/aws-observability/projects/4)
ADOT Collector is AWS's blessed distribution of the OpenTelemetry Collector, pre-wired for CloudWatch, X-Ray, and AMP with IAM/SigV4 auth baked in. If you're running workloads on AWS and want OTel without the integration glue work, this is the path of least resistance. It's not for you if you're running on-prem or want to stay on vanilla upstream.
SigV4 authentication via the sigv4authextension is handled properly, which saves a non-trivial amount of credential plumbing compared to the vanilla collector. The config examples are actually comprehensive — separate YAML files for ECS, EKS, EC2, App Runner, covering the common topologies rather than a single generic example. The benchmark tooling (perf.yml + GitHub Pages trend reports) is genuinely useful for catching regressions before they ship. AWS-specific receivers like awsecscontainermetricsreceiver and awscontainerinsightreceiver pull ECS task and EKS infrastructure metrics that the upstream collector doesn't have.
It still uses a vendor directory in 2026, which means Go module updates require manual vendoring and makes the dependency surface harder to audit at a glance. The support policy is 'best effort' unless you pay for Enterprise Support — so open issues can sit. Several components (datadog, logzio, sapm, signalfx exporters) are being dropped with minimal migration guidance in the issue tracker. It tracks upstream OpenTelemetry Collector closely but with a lag, so you'll sometimes be waiting on AWS to ship a component version that upstream already has.