The useful question is what changes for users, developers or buyers, and whether the announcement stays industry context or becomes something people can actually use.

Amazon CloudWatch has introduced managed Prometheus collectors, allowing users to collect Prometheus metrics from AWS infrastructure such as Amazon EKS, EC2, ECS, MSK, and OpenSearch Service without deploying or managing agents. Previously, this required operating a self-managed OpenTelemetry Collector, which added complexity and maintenance overhead. The new managed collectors automate provisioning, scaling, and data collection, streamlining the monitoring process for these services.

Users can configure scrape settings and establish resource connections, after which CloudWatch handles the rest, delivering metrics in OpenTelemetry format. These metrics can be queried alongside AWS vended metrics using PromQL, enabling unified alarming, dashboarding, and cross-service analysis in a single interface. The managed collectors support multiple discovery methods, including Kubernetes service discovery for EKS, DNS-based discovery via AWS Cloud Map for ECS, direct instance scraping for EC2, and open monitoring endpoints for MSK and OpenSearch Service.

Metrics collected for EKS, MSK, and OpenSearch Service can be visualized in automatic dashboards, queried using PromQL, and incorporated into CloudWatch alarms. The feature is available in all AWS Regions where the CloudWatch OTLP endpoint is accessible, with the exception of Asia Pacific (New Zealand). This expansion enhances monitoring capabilities for users relying on Prometheus metrics within their AWS environments.

Managed Prometheus collectors are billed hourly, with standard CloudWatch OpenTelemetry metric ingestion pricing applying. The service aims to reduce operational burden by eliminating the need for users to manage their own collection infrastructure. Documentation is provided to assist users in getting started with the new managed collectors.