AWS appstream2 documentation change
Summary
Updated product name references from 'Amazon AppStream 2.0' to 'Amazon WorkSpaces Applications' throughout the document, including links to pricing, instance types, and monitoring documentation.
Security assessment
The changes are purely branding/product name updates without any security-related content modifications. No vulnerabilities, security controls, or security features were added or modified.
Diff
diff --git a/appstream2/latest/developerguide/multi-session-recs.md b/appstream2/latest/developerguide/multi-session-recs.md index a9c35ce77..6c742fd81 100644 --- a//appstream2/latest/developerguide/multi-session-recs.md +++ b//appstream2/latest/developerguide/multi-session-recs.md @@ -3 +3 @@ -[Documentation](/index.html)[Amazon AppStream 2.0](/appstream2/index.html)[Administration Guide](what-is-appstream.html) +[Documentation](/index.html)[Amazon WorkSpaces Applications](/appstream2/index.html)[Administration Guide](what-is-appstream.html) @@ -11 +11 @@ When deciding the maximum number of user sessions on an instance in a multi-sess - * _Consider instance specifications_ : Take into account the specifications of the instance, including the number of CPUs, available memory, and GPU specifications. Instances with higher specifications can handle a larger number of user sessions. For more information on different instance types supported by AppStream 2.0 and pricing, see [Amazon AppStream 2.0 pricing](https://aws.amazon.com/appstream2/pricing/). + * _Consider instance specifications_ : Take into account the specifications of the instance, including the number of CPUs, available memory, and GPU specifications. Instances with higher specifications can handle a larger number of user sessions. For more information on different instance types supported by WorkSpaces Applications and pricing, see [WorkSpaces Applications pricing](https://aws.amazon.com/appstream2/pricing/). @@ -13 +13 @@ When deciding the maximum number of user sessions on an instance in a multi-sess - * _Performance testing_ : Conduct performance testing on the applications and workload expected to run within the user sessions. Measure resource utilization, response times, and overall system performance. Use this data to assess the impact of concurrent user sessions on performance, and determine the optimal session-to-instance ratio. You can run these assessments across different instance types offered by AppStream 2.0 to find the optimal instance type or size for your end users. For more information on different instance types offered by AppStream 2.0, see [AppStream 2.0 Instance Families](./instance-types.html). + * _Performance testing_ : Conduct performance testing on the applications and workload expected to run within the user sessions. Measure resource utilization, response times, and overall system performance. Use this data to assess the impact of concurrent user sessions on performance, and determine the optimal session-to-instance ratio. You can run these assessments across different instance types offered by WorkSpaces Applications to find the optimal instance type or size for your end users. For more information on different instance types offered by WorkSpaces Applications, see [WorkSpaces Applications Instance Families](./instance-types.html). @@ -15 +15 @@ When deciding the maximum number of user sessions on an instance in a multi-sess - * _Monitor resource utilization_ : Continuously monitor the resource utilization of the instance during normal usage. Observe CPU, memory, and disk utilization. Ensure that the resource utilization remains within acceptable limits to avoid performance degradation. For a multi-session environment, you can view these metrics on AppStream 2.0 and the CloudWatch console. For more information, see [Monitoring Amazon AppStream 2.0 Resources](./monitoring.html). + * _Monitor resource utilization_ : Continuously monitor the resource utilization of the instance during normal usage. Observe CPU, memory, and disk utilization. Ensure that the resource utilization remains within acceptable limits to avoid performance degradation. For a multi-session environment, you can view these metrics on WorkSpaces Applications and the CloudWatch console. For more information, see [Monitoring Amazon WorkSpaces Applications Resources](./monitoring.html). @@ -19 +19 @@ When deciding the maximum number of user sessions on an instance in a multi-sess -AppStream 2.0 enables you to configure a maximum of 50 user sessions per instance, regardless of the instance type or size that you choose. However, this is just an upper limit, and not a recommended limit. The following is an example table to help you determine the maximum number of user sessions on an instance in a multi-session fleet. The recommended maximum number of users listed in the table is based on general guidelines and assumptions. Testing with the real-life workload is crucial, since actual performance can vary, depending on the workload's individual characteristics, the application's resource requirements, and user behavior. +WorkSpaces Applications enables you to configure a maximum of 50 user sessions per instance, regardless of the instance type or size that you choose. However, this is just an upper limit, and not a recommended limit. The following is an example table to help you determine the maximum number of user sessions on an instance in a multi-session fleet. The recommended maximum number of users listed in the table is based on general guidelines and assumptions. Testing with the real-life workload is crucial, since actual performance can vary, depending on the workload's individual characteristics, the application's resource requirements, and user behavior.