AWS Security ChangesHomeSearch

AWS AmazonCloudWatch: Rename CloudWatch agent config page to Classic configuration

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

File: AmazonCloudWatch/latest/monitoring/create-cloudwatch-agent-configuration-file.md

Summary

Retitles the page to "Create the Classic CloudWatch agent configuration file", rewrites the intro to describe the JSON metrics/logs/traces sections, changes restart guidance to re-run `fetch-config`, and adds a note about splitting an `opentelemetry` section across multiple configuration files.

Security assessment

Purely editorial restructuring and terminology change (Classic vs. OpenTelemetry configuration) plus a restart-procedure correction; no authentication, encryption, credential, or exposure content is introduced or removed.

Evidence

+# Create the Classic CloudWatch agent configuration file

Diff

diff --git a/AmazonCloudWatch/latest/monitoring/create-cloudwatch-agent-configuration-file.md b/AmazonCloudWatch/latest/monitoring/create-cloudwatch-agent-configuration-file.md
index 08b31ea..91b1ce6 100644
--- a//AmazonCloudWatch/latest/monitoring/create-cloudwatch-agent-configuration-file.md
+++ b//AmazonCloudWatch/latest/monitoring/create-cloudwatch-agent-configuration-file.md
@@ -9 +9 @@ Creating multiple CloudWatch agent configuration filesLog collection patterns an
-# Create the CloudWatch agent configuration file
+# Create the Classic CloudWatch agent configuration file
@@ -11 +11 @@ Creating multiple CloudWatch agent configuration filesLog collection patterns an
-Before running the CloudWatch agent on any servers, you must create one or more CloudWatch agent configuration files. 
+In the Classic configuration, the agent configuration file is a JSON file whose `metrics`, `logs`, and `traces` sections specify the metrics, logs, and traces that the agent collects. Metrics are published as CloudWatch metrics in a namespace.
@@ -13 +13 @@ Before running the CloudWatch agent on any servers, you must create one or more
-The agent configuration file is a JSON file that specifies the metrics, logs, and traces that the agent is to collect, including custom metrics. You can create it by using the wizard or by creating it yourself from scratch. You could also use the wizard to initially create the configuration file and then modify it manually. If you create or modify the file manually, the process is more complex, but you have more control over the metrics collected and can specify metrics not available through the wizard.
+You can create the configuration file with the wizard, or create it yourself. You can also use the wizard to create a starting file and then edit it. If you create or edit the file yourself, you have more control over the metrics collected and can specify metrics that the wizard doesn't offer.
@@ -15 +15 @@ The agent configuration file is a JSON file that specifies the metrics, logs, an
-Any time you change the agent configuration file, you must then restart the agent to have the changes take effect. To restart the agent, follow the instructions in [(Optional) Modify the common configuration and named profile for CloudWatch agent](./installing-cloudwatch-agent-ssm.html#CloudWatch-Agent-profile-instance-fleet).
+Any time you change the agent configuration file, you must then restart the agent to have the changes take effect. To restart the agent, run the `fetch-config` command again. For more information, see [Starting the CloudWatch agent](./start-CloudWatch-Agent-on-premise-SSM-onprem.html).
@@ -129,0 +130,2 @@ The preceding example shows the use of two configuration files, but there is no
+You can also split an `opentelemetry` section across multiple configuration files. For the merge rules, see [Split the configuration across files](./CloudWatch-Agent-OpenTelemetry-config.html#CloudWatch-Agent-OpenTelemetry-config-multiple).
+
@@ -229 +231 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-Set up the CloudWatch agent with security-enhanced Linux (SELinux)
+Classic configuration