AWS AmazonCloudWatch documentation change
Summary
Updated scenario titles: replaced 'CloudWatch dashboard' with 'monitoring dashboard' and updated section header text similarly.
Security assessment
Consistency updates in terminology without security context. No security implications identified.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/service_code_examples_scenarios.md b/AmazonCloudWatch/latest/monitoring/service_code_examples_scenarios.md index c602ca32a..088c78dae 100644 --- a//AmazonCloudWatch/latest/monitoring/service_code_examples_scenarios.md +++ b//AmazonCloudWatch/latest/monitoring/service_code_examples_scenarios.md @@ -15 +15 @@ Scenarios target an intermediate level of experience to help you understand serv - * [Creating a CloudWatch dashboard with function name as a variable](./example_cloudwatch_GettingStarted_031_section.html) + * [Creating a monitoring dashboard with function name as a variable](./example_cloudwatch_GettingStarted_031_section.html) @@ -23 +23 @@ Scenarios target an intermediate level of experience to help you understand serv - * [Run CPU stress tests on EC2 instances using FIS](./example_iam_GettingStarted_069_section.html) + * [Run CPU stress tests on virtual machine instances using fault injection](./example_iam_GettingStarted_069_section.html) @@ -25 +25 @@ Scenarios target an intermediate level of experience to help you understand serv - * [Using property variables in CloudWatch dashboards to monitor multiple Lambda functions](./example_iam_GettingStarted_032_section.html) + * [Using property variables in monitoring dashboards to monitor multiple serverless functions](./example_iam_GettingStarted_032_section.html) @@ -38 +38 @@ PutMetricData -Creating a CloudWatch dashboard with function name as a variable +Creating a monitoring dashboard with function name as a variable