AWS Security ChangesHomeSearch

AWS AmazonCloudWatch: CloudWatch agent page reorganized around three configuration models

Service: AmazonCloudWatch · 2026-11-21 · Documentation low

File: AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.md

Summary

The CloudWatch agent install overview was rewritten to describe three configuration models (Classic, Curated OpenTelemetry, Native OpenTelemetry YAML) built on the OpenTelemetry Collector, consolidates log-collection and pricing notes into single sentences, replaces the old install flow with a 4-step getting-started list, and updates the in-page links (adding configuration-model, OpenTelemetry, Classic, and EKS Container Insights pages; dropping the package-signature verification, SELinux, metrics-collected, and create-configuration-file links).

Security assessment

This is a navigational/content restructuring of the agent overview, not a fix for a specific vulnerability or incident. The only security-relevant delta is the removal of the in-page link to the package-signature verification topic (and to the SELinux hardening topic) from this page's list; there is no indication the referenced guidance was changed or deprecated, so this reads as link relocation rather than removal of security documentation. Other added lines (e.g., a step to complete IAM and network prerequisites) are routine setup pointers.

Evidence

-  * [Verifying the signature of the CloudWatch agent package](./verify-CloudWatch-Agent-Package-Signature.html)

Diff

diff --git a/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.md b/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.md
index 263ab4a..4cce99d 100644
--- a//AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.md
+++ b//AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.md
@@ -9 +9 @@
-The CloudWatch agent is a software component that collects metrics, logs, and traces from your Amazon EC2 instances, on-premises servers, and containerized applications. It enables you to monitor your infrastructure and applications more comprehensively than the basic monitoring provided by default.
+The CloudWatch agent is a software component that collects metrics, logs, and traces from your Amazon EC2 instances, on-premises servers, and containerized applications. It enables you to monitor your infrastructure and applications more comprehensively than the basic monitoring provided by default. The CloudWatch agent is built on the OpenTelemetry Collector, so it can receive OpenTelemetry data and send it to the CloudWatch OTLP endpoints.
@@ -11 +11 @@ The CloudWatch agent is a software component that collects metrics, logs, and tr
-The CloudWatch agent enables you to do the following:
+The agent supports three configuration models:
@@ -13 +13 @@ The CloudWatch agent enables you to do the following:
-  * Collect internal system-level metrics from Amazon EC2 instances across operating systems. The metrics can include in-guest metrics, in addition to the metrics for Amazon EC2 instances. For a list of additional metrics that you can collect, see [Metrics collected by the CloudWatch agent](./metrics-collected-by-CloudWatch-agent.html).
+  * **Classic** – The agent publishes metrics as CloudWatch metrics in a namespace, `CWAgent` by default, which are billed as custom metrics. The Classic configuration also provides StatsD, collectd, procstat, JMX, NVIDIA GPU, EFA, NVMe, and network performance metrics, and CloudWatch Application Signals. For more information, see [Configure the CloudWatch agent with the Classic configuration](./CloudWatch-Agent-Classic-configuration.html).
@@ -15 +15 @@ The CloudWatch agent enables you to do the following:
-  * Collect system-level metrics from on-premises servers. These can include servers in a hybrid environment as well as servers not managed by AWS.
+  * **Curated OpenTelemetry (recommended)** – You configure the `opentelemetry` section of the agent JSON configuration file. The agent collects metrics, logs, and traces and sends them to the CloudWatch OpenTelemetry Protocol (OTLP) endpoints. Metrics use OpenTelemetry semantic conventions, keep their labels, and are queried with PromQL. They're billed per GB ingested. For more information, see [Configure the CloudWatch agent with OpenTelemetry (recommended)](./CloudWatch-Agent-OpenTelemetry-configuration.html).
@@ -17 +17 @@ The CloudWatch agent enables you to do the following:
-  * Retrieve custom metrics from your applications or services using the `StatsD` and `collectd` protocols. `StatsD` is supported on both Linux servers and servers running Windows Server. `collectd` is supported only on Linux servers.
+  * **Native OpenTelemetry (YAML)** – You provide a standard OpenTelemetry Collector configuration in YAML, appended to the agent configuration file (the agent requires at least one JSON configuration file). This exposes the full OpenTelemetry Collector receiver set, including receivers that the `opentelemetry` section doesn't expose, such as `collectd` and `statsd`, and sends the data to the CloudWatch OTLP endpoints. For more information, see [Appending OpenTelemetry collector configuration files](./CloudWatch-Agent-appending-OpenTelemetry-config-files.html).
@@ -19 +18,0 @@ The CloudWatch agent enables you to do the following:
-  * Collect logs from Amazon EC2 instances and on-premises servers, running either Linux or Windows Server.
@@ -21 +19,0 @@ The CloudWatch agent enables you to do the following:
-Note
@@ -23 +20,0 @@ Note
-The CloudWatch agent does not support collecting logs from FIFO pipes.
@@ -25 +22 @@ The CloudWatch agent does not support collecting logs from FIFO pipes.
-  * Send the metrics to either CloudWatch or Amazon Managed Service for Prometheus, or to both. The CloudWatch agent configuration file contains a `metrics_destinations` parameter in the `metrics` section. You can specify `cloudwatch`, `amp`, or both in this parameter.
+In all three models, the agent collects logs from Amazon EC2 instances and on-premises servers into Amazon CloudWatch Logs. The agent doesn't support collecting logs from FIFO pipes. For pricing, see [Amazon CloudWatch Pricing](http://aws.amazon.com/cloudwatch/pricing).
@@ -27 +24 @@ The CloudWatch agent does not support collecting logs from FIFO pipes.
-  * Version 1.300031.0 and later can be used to enable CloudWatch Application Signals. For more information, see [Application Signals](./CloudWatch-Application-Monitoring-Sections.html).
+To get started:
@@ -29 +26 @@ The CloudWatch agent does not support collecting logs from FIFO pipes.
-  * Version 1.300025.0 and later can collect traces from [OpenTelemetry](https://docs.aws.amazon.com/xray/latest/devguide/xray-instrumenting-your-app.html#xray-instrumenting-opentel) or [X-Ray](https://docs.aws.amazon.com/xray/latest/devguide/xray-instrumenting-your-app.html#xray-instrumenting-xray-sdk) client SDKs, and send them to X-Ray.
+  1. Choose a configuration model. For more information, see [Choose a configuration model for the CloudWatch agent](./CloudWatch-Agent-config-model.html).
@@ -31 +28 @@ The CloudWatch agent does not support collecting logs from FIFO pipes.
-Using the CloudWatch agent allows you to collect traces without needing to run a separate trace collection daemon, helping to reduce the number of agents that you run and manage.
+  2. Complete the IAM and network prerequisites. For more information, see [Prerequisites](./prerequisites.html).
@@ -32,0 +30 @@ Using the CloudWatch agent allows you to collect traces without needing to run a
+  3. Install the agent. For more information, see [Installing the CloudWatch agent](./install-CloudWatch-Agent-on-EC2-Instance.html).
@@ -33,0 +32 @@ Using the CloudWatch agent allows you to collect traces without needing to run a
+  4. Create the agent configuration file for the model that you chose, and start the agent.
@@ -36 +34,0 @@ Using the CloudWatch agent allows you to collect traces without needing to run a
-Metrics that the CloudWatch agent publishes as CloudWatch metrics can be viewed in CloudWatch just as any other CloudWatch metrics. The default CloudWatch namespace for these metrics is `CWAgent`, although you can specify a different namespace when you configure the agent.
@@ -38,5 +35,0 @@ Metrics that the CloudWatch agent publishes as CloudWatch metrics can be viewed
-Metrics that the CloudWatch agent forwards to the CloudWatch OTLP endpoints are stored as OpenTelemetry metrics. These metrics don't use a CloudWatch namespace. Instead, you identify them by metric name and labels, and you query them with PromQL. For more information about OpenTelemetry metrics, see [OpenTelemetry Metrics (Recommended)](./metrics-otel-recommended.html). For information about querying these metrics, see [Query metrics with PromQL](./CloudWatch-PromQL.html).
-
-The logs collected by the CloudWatch agent are processed and stored in Amazon CloudWatch Logs, just like logs collected by the older CloudWatch Logs agent. For information about CloudWatch Logs pricing, see [Amazon CloudWatch Pricing](http://aws.amazon.com/cloudwatch/pricing).
-
-Metrics collected by the CloudWatch agent are billed as custom metrics. For more information about CloudWatch metrics pricing, see [Amazon CloudWatch Pricing](http://aws.amazon.com/cloudwatch/pricing).
@@ -46,15 +38,0 @@ The CloudWatch agent is open-source under the MIT license, and is [ hosted on Gi
-For information about forwarding application metrics, traces, and logs through the CloudWatch agent using the OpenTelemetry Protocol (OTLP), see [Example: send application metrics through the CloudWatch agent](./CloudWatch-OTLPCloudWatchAgent.html#CloudWatch-OTLPCloudWatchAgent-Example).
-
-You can download and install the CloudWatch agent manually using the command line, or you can integrate it with AWS Systems Manager. The general flow of installing the CloudWatch agent is as follows:
-
-  1. Create IAM roles or users that enable the agent to collect metrics from the server and optionally to integrate with AWS Systems Manager.
-
-  2. Download the agent package.
-
-  3. Modify the CloudWatch agent configuration file and specify the metrics that you want to collect.
-
-  4. Install and start the agent on your servers.
-
-
-
-
@@ -62,0 +41,2 @@ You can download and install the CloudWatch agent manually using the command lin
+  * [Choose a configuration model for the CloudWatch agent](./CloudWatch-Agent-config-model.html)
+
@@ -69,2 +48,0 @@ You can download and install the CloudWatch agent manually using the command lin
-  * [Verifying the signature of the CloudWatch agent package](./verify-CloudWatch-Agent-Package-Signature.html)
-
@@ -73 +51 @@ You can download and install the CloudWatch agent manually using the command lin
-  * [Set up the CloudWatch agent with security-enhanced Linux (SELinux)](./CloudWatch-Agent-SELinux.html)
+  * [Configure the CloudWatch agent with OpenTelemetry (recommended)](./CloudWatch-Agent-OpenTelemetry-configuration.html)
@@ -75 +53 @@ You can download and install the CloudWatch agent manually using the command lin
-  * [Create the CloudWatch agent configuration file](./create-cloudwatch-agent-configuration-file.html)
+  * [Configure the CloudWatch agent with the Classic configuration](./CloudWatch-Agent-Classic-configuration.html)
@@ -79,2 +56,0 @@ You can download and install the CloudWatch agent manually using the command lin
-  * [Metrics collected by the CloudWatch agent](./metrics-collected-by-CloudWatch-agent.html)
-
@@ -82,0 +59,2 @@ You can download and install the CloudWatch agent manually using the command lin
+  * [Using the CloudWatch agent for Amazon EKS Container Insights](./CloudWatch-Agent-container-insights-eks.html)
+
@@ -100 +78 @@ Troubleshooting
-Supported operating systems
+Choose a configuration model