AWS AmazonCloudWatch documentation change
Summary
Updated documentation to replace 'AWS CloudFormation' with 'CloudFormation' in multiple instances, maintaining terminology consistency
Security assessment
Changes are purely terminological (removing 'AWS' prefix from CloudFormation references) with no security implications. The mention of IAM policies remains unchanged and relates to existing security best practices rather than addressing new vulnerabilities.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-troubleshooting-ECS.md b/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-troubleshooting-ECS.md index abc5a0f16..c98388530 100644 --- a//AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-troubleshooting-ECS.md +++ b//AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-troubleshooting-ECS.md @@ -17 +17 @@ The Prometheus metrics should be ingested as log events in the log group **/aws/ -First, change the CloudWatch agent to debug mode by adding the following bold lines to your AWS CloudFormation template file, `cwagent-ecs-prometheus-metric-for-bridge-host.yaml` or `cwagent-ecs-prometheus-metric-for-awsvpc.yaml`. Then save the file. +First, change the CloudWatch agent to debug mode by adding the following bold lines to your CloudFormation template file, `cwagent-ecs-prometheus-metric-for-bridge-host.yaml` or `cwagent-ecs-prometheus-metric-for-awsvpc.yaml`. Then save the file. @@ -28 +28 @@ First, change the CloudWatch agent to debug mode by adding the following bold li -Create a new AWS CloudFormation changeset against the existing stack. Set other parameters in the changeset to the same values as in your existing AWS CloudFormation stack. The following example is for a CloudWatch agent installed in an Amazon ECS cluster using the EC2 launch type and the bridge network mode. +Create a new CloudFormation changeset against the existing stack. Set other parameters in the changeset to the same values as in your existing CloudFormation stack. The following example is for a CloudWatch agent installed in an Amazon ECS cluster using the EC2 launch type and the bridge network mode. @@ -48 +48 @@ Create a new AWS CloudFormation changeset against the existing stack. Set other -Go to the AWS CloudFormation console to review the new changeset, `$NEW_CHANGESET_NAME`. There should be one change applied to the **CWAgentConfigSSMParameter** resource. Execute the changeset and restart the CloudWatch agent task by entering the following commands. +Go to the CloudFormation console to review the new changeset, `$NEW_CHANGESET_NAME`. There should be one change applied to the **CWAgentConfigSSMParameter** resource. Execute the changeset and restart the CloudWatch agent task by entering the following commands. @@ -144 +144 @@ If there are still no log events sent to the target CloudWatch Logs log group ev - * The CloudWatch agent’s ECS task role might not have the **CloudWatchAgentServerPolicy** managed policy. The CloudWatch agent’s ECS task role needs to have this policy to be able to send the Prometheus metrics as log events. If you used the sample AWS CloudFormation template to create the IAM roles automatically, both the ECS task role and the ECS execution role are granted with the least privilege to perform the Prometheus monitoring. + * The CloudWatch agent’s ECS task role might not have the **CloudWatchAgentServerPolicy** managed policy. The CloudWatch agent’s ECS task role needs to have this policy to be able to send the Prometheus metrics as log events. If you used the sample CloudFormation template to create the IAM roles automatically, both the ECS task role and the ECS execution role are granted with the least privilege to perform the Prometheus monitoring.