AWS prescriptive-guidance documentation change
Summary
Updated documentation links and fixed URL formatting for CloudWatch references. Corrected punctuation in SolarWinds link. Changed navigation link from welcome.html to introduction.html.
Security assessment
The changes primarily involve URL formatting corrections and navigation structure updates. While the SolarWinds reference might raise security awareness due to historical incidents, the change itself only adds a comma and does not address security aspects. The CloudWatch monitoring recommendations remain unchanged in substance.
Diff
diff --git a/prescriptive-guidance/latest/migration-replatforming-cots-applications/updating-logging-monitoring.md b/prescriptive-guidance/latest/migration-replatforming-cots-applications/updating-logging-monitoring.md index 5250c51fb..12fc57d56 100644 --- a//prescriptive-guidance/latest/migration-replatforming-cots-applications/updating-logging-monitoring.md +++ b//prescriptive-guidance/latest/migration-replatforming-cots-applications/updating-logging-monitoring.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Replatforming COTS and in-house applications during a migration to the AWS Cloud](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Replatforming COTS and in-house applications during a migration to the AWS Cloud](introduction.html) @@ -9 +9 @@ -Some legacy environments use centralized logging and monitoring tools (for example, [Splunk](https://www.splunk.com/), [SolarWinds](https://www.solarwinds.com/), or [Zabbix](https://www.zabbix.com/)) for infrastructure and application monitoring. Application support teams might also use Secure Shell (SSH) protocol or remote desktop protocol (RDP) to monitor and debug. To avoid this manual and repetitive process, you can use [CloudWatch](https://docs.aws.amazon.com//AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html) to automate monitoring on the AWS Cloud. +Some legacy environments use centralized logging and monitoring tools (for example, [Splunk](https://www.splunk.com/), [SolarWinds,](https://www.solarwinds.com/) or [Zabbix](https://www.zabbix.com/)) for infrastructure and application monitoring. Application support teams might also use Secure Shell (SSH) protocol or remote desktop protocol (RDP) to monitor and debug. To avoid this manual and repetitive process, you can use [CloudWatch](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html) to automate monitoring on the AWS Cloud. @@ -11 +11 @@ Some legacy environments use centralized logging and monitoring tools (for examp -We recommend using CloudWatch metrics to monitor your infrastructure and CloudWatch agents to send application logs to CloudWatch. After application logs are received by CloudWatch, you can create [CloudWatch metric filters](https://docs.aws.amazon.com//AmazonCloudWatch/latest/logs/MonitoringPolicyExamples.html) and use [CloudWatch alarms](https://docs.aws.amazon.com//AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html) to monitor application errors and automatically notify support teams. +We recommend using CloudWatch metrics to monitor your infrastructure and CloudWatch agents to send application logs to CloudWatch. After application logs are received by CloudWatch, you can create [CloudWatch metric filters](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/MonitoringPolicyExamples.html) and use [CloudWatch alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html) to monitor application errors and automatically notify support teams.