AWS prescriptive-guidance documentation change
Summary
Fixed URL formatting by adding double slashes in documentation links
Security assessment
The changes only correct URL path formatting by adding consistent double slashes after the domain. There is no mention of security vulnerabilities, mitigations, or new security features. The content focuses on monitoring architecture and service integration without security implications.
Diff
diff --git a/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/prometheus-monitoring-eks.md b/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/prometheus-monitoring-eks.md index cd237c1c6..fd89446ac 100644 --- a//prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/prometheus-monitoring-eks.md +++ b//prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/prometheus-monitoring-eks.md @@ -7 +7 @@ -[Amazon Managed Service for Prometheus](https://docs.aws.amazon.com/prometheus/latest/userguide/what-is-Amazon-Managed-Service-Prometheus.html) provides a scalable, secure, AWS managed service for open-source Prometheus. You can use Prometheus query language (PromQL) to monitor the performance of containerized workloads without managing the underlying infrastructure for ingesting, storing, and querying operational metrics. You can collect Prometheus metrics from Amazon EKS and Amazon ECS by using [AWS Distro for OpenTelemetry (ADOT)](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics-OpenTelemetry.html) or Prometheus servers as collection agents. +[Amazon Managed Service for Prometheus](https://docs.aws.amazon.com//prometheus/latest/userguide/what-is-Amazon-Managed-Service-Prometheus.html) provides a scalable, secure, AWS managed service for open-source Prometheus. You can use Prometheus query language (PromQL) to monitor the performance of containerized workloads without managing the underlying infrastructure for ingesting, storing, and querying operational metrics. You can collect Prometheus metrics from Amazon EKS and Amazon ECS by using [AWS Distro for OpenTelemetry (ADOT)](https://docs.aws.amazon.com//prometheus/latest/userguide/AMP-onboard-ingest-metrics-OpenTelemetry.html) or Prometheus servers as collection agents. @@ -9 +9 @@ -[CloudWatch Container Insights monitoring for Prometheus](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus.html) enables you to configure and use the CloudWatch agent to discover Prometheus metrics from Amazon ECS, Amazon EKS, and Kubernetes workloads, and ingest them as CloudWatch metrics. This solution is appropriate if CloudWatch is your primary observability and monitoring solution. However, the following list outlines use cases where Amazon Managed Service for Prometheus provides more flexibility for ingesting, storing, and querying Prometheus metrics: +[CloudWatch Container Insights monitoring for Prometheus](https://docs.aws.amazon.com//AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus.html) enables you to configure and use the CloudWatch agent to discover Prometheus metrics from Amazon ECS, Amazon EKS, and Kubernetes workloads, and ingest them as CloudWatch metrics. This solution is appropriate if CloudWatch is your primary observability and monitoring solution. However, the following list outlines use cases where Amazon Managed Service for Prometheus provides more flexibility for ingesting, storing, and querying Prometheus metrics: @@ -15 +15 @@ - * Prometheus enables you to perform analysis on your operational metrics by using PromQL queries. In contrast, [the CloudWatch agent ingests Prometheus metrics in embedded metric format](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-configure-ECS.html#ContainerInsights-Prometheus-Setup-cw-agent-config) into CloudWatch Logs which result in CloudWatch metrics. You can query the embedded metric format logs by using CloudWatch Logs Insights. + * Prometheus enables you to perform analysis on your operational metrics by using PromQL queries. In contrast, [the CloudWatch agent ingests Prometheus metrics in embedded metric format](https://docs.aws.amazon.com//AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-configure-ECS.html#ContainerInsights-Prometheus-Setup-cw-agent-config) into CloudWatch Logs which result in CloudWatch metrics. You can query the embedded metric format logs by using CloudWatch Logs Insights. @@ -17 +17 @@ - * If you don’t plan to use CloudWatch for monitoring and metrics capture, then you should use Amazon Managed Service for Prometheus with your Prometheus server and a visualization solution such as Grafana. You need to configure your Prometheus server to scrape metrics from your Prometheus targets and configure the server to [remote write to your Amazon Managed Service for Prometheus workspace](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-ingest-metrics-existing-Prometheus.html). If you use Amazon Managed Grafana, then you can [directly integrate Amazon Managed Grafana with your Amazon Managed Service for Prometheus data source by using the included plugin](https://docs.aws.amazon.com/grafana/latest/userguide/prometheus-data-source.html). Because metric data is stored in Amazon Managed Service for Prometheus, there is no dependency to deploy the CloudWatch agent or requirement to ingest data into CloudWatch. The CloudWatch agent is required for Container Insights monitoring for Prometheus. + * If you don’t plan to use CloudWatch for monitoring and metrics capture, then you should use Amazon Managed Service for Prometheus with your Prometheus server and a visualization solution such as Grafana. You need to configure your Prometheus server to scrape metrics from your Prometheus targets and configure the server to [remote write to your Amazon Managed Service for Prometheus workspace](https://docs.aws.amazon.com//prometheus/latest/userguide/AMP-onboard-ingest-metrics-existing-Prometheus.html). If you use Amazon Managed Grafana, then you can [directly integrate Amazon Managed Grafana with your Amazon Managed Service for Prometheus data source by using the included plugin](https://docs.aws.amazon.com//grafana/latest/userguide/prometheus-data-source.html). Because metric data is stored in Amazon Managed Service for Prometheus, there is no dependency to deploy the CloudWatch agent or requirement to ingest data into CloudWatch. The CloudWatch agent is required for Container Insights monitoring for Prometheus.