https://aws.amazon.com/cloudwatch/ now supports bearer token authentication, using API keys (bearer tokens), as an additional option for sending OpenTelemetry traces to the AWS X-Ray OpenTelemetry Protocol (OTLP) traces endpoint. Any OTLP/HTTP client that can set an Authorization header, including the OpenTelemetry Collector and OpenTelemetry SDK exporters, can now authenticate with a bearer token instead of signing requests with AWS Signature Version 4 (SigV4). This helps teams send traces from workloads that can't use the AWS SDK or short-term credentials, such as applications running on premises or in other clouds, CI/CD pipelines, and third-party tools that support only a static Authorization header. SigV4 remains the recommended authentication method for sending traces to CloudWatch, and the AWS Distro for OpenTelemetry (ADOT) SDKs continue to use SigV4 by default with no changes required. Traces sent with either method get the same CloudWatch capabilities, including Transaction Search, Amazon CloudWatch Application Signals, and Amazon CloudWatch Omni. Bearer token authentication for traces is available in all commercial AWS Regions where the AWS X-Ray OTLP traces endpoint is available. To learn more, see https://docs.aws.amazon.com/xray/latest/devguide/xray-opentelemetry-bearer-token.html in the AWS X-Ray Developer Guide.

Amazon CloudWatch now supports bearer token authentication, using API keys (bearer tokens), as an additional option for sending OpenTelemetry traces to the AWS X-Ray OpenTelemetry Protocol (OTLP) traces endpoint. Any OTLP/HTTP client that can set an Authorization header, including the OpenTelemetry Collector and OpenTelemetry SDK exporters, can now authenticate with a bearer token instead of signing requests with AWS Signature Version 4 (SigV4). This helps teams send traces from workloads that can't use the AWS SDK or short-term credentials, such as applications running on premises or in other clouds, CI/CD pipelines, and third-party tools that support only a static Authorization header. SigV4 remains the recommended authentication method for sending traces to CloudWatch, and the AWS Distro for OpenTelemetry (ADOT) SDKs continue to use SigV4 by default with no changes required. Traces sent with either method get the same CloudWatch capabilities, including Transaction Search, Amazon CloudWatch Application Signals, and Amazon CloudWatch Omni. Bearer token authentication for traces is available in all commercial AWS Regions where the AWS X-Ray OTLP traces endpoint is available. To learn more, see Setting up bearer token authentication for traces in the AWS X-Ray Developer Guide.

Learn how to build and deploy serverless applications using AWS SAM with best practices, local testing, and streamlined CI/CD workflows.

CloudWatch Application Signals, an application performance monitoring (APM) solution, enables developers and operators to easily monitor the health and performance of their applications hosted across different compute platforms such as EKS, ECS and more. Customers can now use OpenTelemetry Protocol (OTLP), an open-source protocol, to send traces to the X-Ray OTLP endpoint, and unlock application performance monitoring capabilities with Application Signals. OpenTelemetry Protocol (OTLP) is a standardized protocol for transmitting telemetry data from your applications to monitoring solutions like CloudWatch. Developers who use OpenTelemetry to instrument their applications can now send traces to the X-Ray OTLP endpoint, unlocking, via Application Signals, pre-built, standardized dashboards for critical application metrics (throughput/latency/errors), correlated trace spans, and interactions between applications and its dependencies (such as other AWS services). This provides operators with a complete picture of the application's health, allowing them to pinpoint the source of performance issues. By creating Service Level Objectives (SLOs) within Application Signals, customers can track performance indicators of crucial application functions. This makes it simple to spot and address any operations falling short of their business goals. Finally, customers can also analyze application issues in business context such as troubleshoot customer support tickets or find top customers impacted due to application disruptions by searching and analyzing transaction (or trace) spans. OTLP endpoint for traces is available in all https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Monitoring-Sections.html is generally available. For pricing, see https://aws.amazon.com/cloudwatch/pricing/. See https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-OpenTelemetry-Sections.html to learn more.

CloudWatch Application Signals, an application performance monitoring (APM) solution, enables developers and operators to easily monitor the health and performance of their applications hosted across different compute platforms such as EKS, ECS and more. Customers can now use OpenTelemetry Protocol (OTLP), an open-source protocol, to send traces to the X-Ray OTLP endpoint, and unlock application performance monitoring capabilities with Application Signals. OpenTelemetry Protocol (OTLP) is a standardized protocol for transmitting telemetry data from your applications to monitoring solutions like CloudWatch. Developers who use OpenTelemetry to instrument their applications can now send traces to the X-Ray OTLP endpoint, unlocking, via Application Signals, pre-built, standardized dashboards for critical application metrics (throughput/latency/errors), correlated trace spans, and interactions between applications and its dependencies (such as other AWS services). This provides operators with a complete picture of the application's health, allowing them to pinpoint the source of performance issues. By creating Service Level Objectives (SLOs) within Application Signals, customers can track performance indicators of crucial application functions. This makes it simple to spot and address any operations falling short of their business goals. Finally, customers can also analyze application issues in business context such as troubleshoot customer support tickets or find top customers impacted due to application disruptions by searching and analyzing transaction (or trace) spans. OTLP endpoint for traces is available in all regions where Application Signals is generally available. For pricing, see Amazon CloudWatch pricing. See documentation to learn more.