AWS AmazonCloudWatch documentation change
Summary
Corrected apostrophe usage and capitalization ('docker' to 'Docker'). Maintained existing security note about production security group best practices without modification.
Security assessment
Changes are grammatical improvements. The pre-existing security note about using dedicated security groups in production was untouched and merely carried forward without alteration or enhancement.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-redis-ecs.md b/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-redis-ecs.md index 239e7ce1d..e8eaace2e 100644 --- a//AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-redis-ecs.md +++ b//AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-redis-ecs.md @@ -11 +11 @@ Set the Amazon ECS Fargate cluster environment variableSet the network environme -This tutorial provides a hands-on introduction to scrape the Prometheus metrics of a sample Redis OSS application in an Amazon ECS Fargate cluster. The Redis OSS Prometheus exporter target will be auto-discovered by the CloudWatch agent with Prometheus metric support based on the container’s docker labels. +This tutorial provides a hands-on introduction to scrape the Prometheus metrics of a sample Redis OSS application in an Amazon ECS Fargate cluster. The Redis OSS Prometheus exporter target will be auto-discovered by the CloudWatch agent with Prometheus metric support based on the container's Docker labels. @@ -86 +86 @@ The expected result of this command is as follows: - 2. In this tutorial, we are going to install the Redis OSS application and the CloudWatch agent in the default security group of the Amazon ECS cluster’s VPC. The default security group allows all network connection within the same security group so the CloudWatch agent can scrape the Prometheus metrics exposed on the Redis OSS containers. In a real production environment, you might want to create dedicated security groups for the Redis OSS application and CloudWatch agent and set customized permissions for them. + 2. In this tutorial, we are going to install the Redis OSS application and the CloudWatch agent in the default security group of the Amazon ECS cluster's VPC. The default security group allows all network connection within the same security group so the CloudWatch agent can scrape the Prometheus metrics exposed on the Redis OSS containers. In a real production environment, you might want to create dedicated security groups for the Redis OSS application and CloudWatch agent and set customized permissions for them. @@ -147 +147 @@ In the Redis OSS task definition, two containers are defined: - * The other container runs the Redis OSS exporter process to expose the Prometheus metrics on port 9121. This is the container to be discovered and scraped by the CloudWatch agent. The following docker label is defined so that the CloudWatch agent can discover this container based on it. + * The other container runs the Redis OSS exporter process to expose the Prometheus metrics on port 9121. This is the container to be discovered and scraped by the CloudWatch agent. The following Docker label is defined so that the CloudWatch agent can discover this container based on it. @@ -164 +164 @@ In the Redis OSS task definition, two containers are defined: -Then, in the `ecs_service_discovery` section shown here, the `docker_label`-based service discovery is enabled with the default settings which are based on `ECS_PROMETHEUS_EXPORTER_PORT`, which matches the docker label we defined in the Redis OSS ECS task definition. So we do not need to make any changes in this section: +Then, in the `ecs_service_discovery` section shown here, the `docker_label`-based service discovery is enabled with the default settings which are based on `ECS_PROMETHEUS_EXPORTER_PORT`, which matches the Docker label we defined in the Redis OSS ECS task definition. So we do not need to make any changes in this section: