AWS announced on November 3 that Amazon CloudWatch now supports API keys for OpenTelemetry traces: bearer-token authentication as an additional option for sending traces to the AWS X-Ray OTLP traces endpoint. Any OTLP/HTTP client that can set an Authorization header, including the OpenTelemetry Collector and the SDK exporters, can now skip signing requests with Signature Version 4. The stated audience is everything that could not sign: workloads on premises or in other clouds, CI/CD pipelines, and “third-party tools that support only a static Authorization header.”
There are no vendor figures to discount here, and the announcement is careful about what it is not saying. “SigV4 remains the recommended authentication method,” the AWS Distro for OpenTelemetry SDKs keep using it by default, and traces sent either way get the same downstream features, Transaction Search and Application Signals among them. Availability is every commercial region where the X-Ray OTLP endpoint already runs. The trade is explicit: a static credential is easier to hand to a pipeline and easier to leak from one, which is why AWS frames it as the second option rather than the new path.
In the catalog this lands across two providers. The AWS X-Ray provider page lists ten API pages describing the native X-Ray service, with the AWS X-Ray Traces API the one this change feeds; the OTLP ingestion endpoint is not a separate page among them. The Amazon CloudWatch provider page lists 48, including the Amazon CloudWatch Cloudwatch O Tel Enrichment API, and its record already describes unified metrics, logs and traces. X-Ray’s own description notes it “is now part of Amazon CloudWatch Application Signals,” which is the same consolidation the announcement assumes.
On the Kin Score, CloudWatch is 77.3, exemplar, with access clarity at a full 100.0, and X-Ray is 65.2, strong, with developer ergonomics at 83.8. Both have auth clarity lit in Agent Readiness, 41.5 and 43.1 respectively. Both have protected resource metadata and dynamic client registration unlit, the machine-readable descriptions of how a client finds out which credential an endpoint accepts. Adding a second way in is a reason to publish that description, because a collector configured from documentation is exactly the kind of client this release was written for.