AWS wellarchitected documentation change
Summary
Updated references from 'Amazon AppStream 2.0' to 'Amazon WorkSpaces Applications' throughout monitoring and logging documentation
Security assessment
The changes primarily update service names without introducing new security content. While monitoring/logging relates to security best practices, there is no evidence these changes address a specific security vulnerability or weakness. The log retention justification remains similar to previous guidance.
Diff
diff --git a/wellarchitected/latest/end-user-computing-lens/eucops05-bp01.md b/wellarchitected/latest/end-user-computing-lens/eucops05-bp01.md index d8ddba5d8..caaaf9267 100644 --- a//wellarchitected/latest/end-user-computing-lens/eucops05-bp01.md +++ b//wellarchitected/latest/end-user-computing-lens/eucops05-bp01.md @@ -17 +17 @@ Implement proactive monitoring of the health of all aspects of an AWS EUC deploy -For both Amazon WorkSpaces and Amazon AppStream 2.0, it is important to monitor both the service itself in addition to any external service dependencies. Consider the following monitoring tools: +For both Amazon WorkSpaces and Amazon WorkSpaces Applications, it is important to monitor both the service itself in addition to any external service dependencies. Consider the following monitoring tools: @@ -38 +38 @@ Additional metrics, such as instance specific CPU, memory, and disk performance -[**Amazon AppStream 2.0**](https://docs.aws.amazon.com/appstream2/latest/developerguide/logging-monitoring-alerting.html) +[**Amazon WorkSpaces Applications**](https://docs.aws.amazon.com/appstream2/latest/developerguide/logging-monitoring-alerting.html) @@ -44 +44 @@ CloudWatch alarms can be configured to send alerts when specific thresholds are -Each WorkSpaces and Amazon AppStream 2.0 instance exposes a network interface in the customers managed VPC which can be addressed by third party monitoring tools for traditional management. +Each WorkSpaces and Amazon WorkSpaces Applications instance exposes a network interface in the customers managed VPC which can be addressed by third party monitoring tools for traditional management. @@ -52 +52 @@ Monitoring should also be in place for: - * Internet connectivity (user to Amazon WorkSpaces or Amazon AppStream 2.0 service) + * Internet connectivity (user to Amazon WorkSpaces or Amazon WorkSpaces Applications service) @@ -87 +87 @@ For services still hosted on-premises, Amazon CloudWatch agents can be installed -For centralized gathering of log files for troubleshooting and retrospective analysis, Amazon Kinesis agents can be deployed on WorkSpaces or AppStream 2.0 to deliver real-time propagation of OS and application-level logs to a central location. +For centralized gathering of log files for troubleshooting and retrospective analysis, Amazon Kinesis agents can be deployed on WorkSpaces or WorkSpaces Applications to deliver real-time propagation of OS and application-level logs to a central location. @@ -89 +89 @@ For centralized gathering of log files for troubleshooting and retrospective ana -For Amazon AppStream 2.0, propagating instance log files in real time to a centralized location is essential if you need to store logs for compliance purposes, as AppStream instances are destroyed at the end of each session. For more detail, see [Using the Kinesis Agent to store AppStream 2.0 Windows event logs](https://aws.amazon.com/blogs/desktop-and-application-streaming/using-kinesis-agent-for-microsoft-windows-to-store-appstream-2-0-windows-event-logs/). +For Amazon WorkSpaces Applications, propagating instance log files in real time to a centralized location is essential if you need to store logs for compliance purposes, as AppStream instances are destroyed at the end of each session. For more detail, see [Using the Kinesis Agent to store WorkSpaces Applications Windows event logs](https://aws.amazon.com/blogs/desktop-and-application-streaming/using-kinesis-agent-for-microsoft-windows-to-store-appstream-2-0-windows-event-logs/).