AWS wellarchitected documentation change
Summary
Updated service references from AppStream 2.0 to WorkSpaces Applications throughout the document, including examples and best practice links
Security assessment
Changes appear to reflect a rebranding or service name update rather than addressing security issues. The content about timeout configurations and scaling strategies remains conceptually identical, just referencing the new service name.
Diff
diff --git a/wellarchitected/latest/end-user-computing-lens/alignment-to-demand.md b/wellarchitected/latest/end-user-computing-lens/alignment-to-demand.md index b6d539759..e2add6326 100644 --- a//wellarchitected/latest/end-user-computing-lens/alignment-to-demand.md +++ b//wellarchitected/latest/end-user-computing-lens/alignment-to-demand.md @@ -10 +10 @@ EUCSUS01: How do you select the type of fleet and running mode for your end user -With Amazon AppStream 2.0, you can select between Always-On or On-Demand fleet types. Similarly, Amazon WorkSpaces offers two running modes with AlwaysOn and AutoStop. +With Amazon WorkSpaces Applications, you can select between Always-On or On-Demand fleet types. Similarly, Amazon WorkSpaces offers two running modes with AlwaysOn and AutoStop. @@ -22 +22 @@ Timeouts are crucial for an AWS EUC deployment, as timeouts enable efficient res -For example, consider two scenarios where disconnect timeouts have been configured for an AppStream 2.0 fleet at six hours and 15 minutes respectively. In the case of the 15 minute timeout, a session will be timed out and the instance terminated within 15 minutes. +For example, consider two scenarios where disconnect timeouts have been configured for an WorkSpaces Applications fleet at six hours and 15 minutes respectively. In the case of the 15 minute timeout, a session will be timed out and the instance terminated within 15 minutes. @@ -26 +26 @@ In comparison, the six hour timeout will result in an instance running for six h -Timeouts optimize costs and the carbon footprint for AppStream 2.0and WorkSpaces instances by helping to prevent unnecessary resource consumption and associated charges. +Timeouts optimize costs and the carbon footprint for WorkSpaces Applicationsand WorkSpaces instances by helping to prevent unnecessary resource consumption and associated charges. @@ -31 +31 @@ EUCSUS04: How do you align your scaling strategy with efficient use of resources -Scaling in Amazon AppStream 2.0 helps create a seamless user experience by providing the necessary resources to handle fluctuating user demands, while also optimizing costs and sustainability by avoiding over-provisioning when demand is low. +Scaling in Amazon WorkSpaces Applications helps create a seamless user experience by providing the necessary resources to handle fluctuating user demands, while also optimizing costs and sustainability by avoiding over-provisioning when demand is low. @@ -41 +41 @@ Scaling in Amazon AppStream 2.0 helps create a seamless user experience by provi - * [EUCSUS03-BP01 Adapt your AppStream 2.0 fleet timeout](./eucsus03-bp01.html) + * [EUCSUS03-BP01 Adapt your WorkSpaces Applications fleet timeout](./eucsus03-bp01.html) @@ -45 +45 @@ Scaling in Amazon AppStream 2.0 helps create a seamless user experience by provi - * [EUCSUS04-BP01 Implement a scaling methodology in AppStream 2.0](./eucsus04-bp01.html) + * [EUCSUS04-BP01 Implement a scaling methodology in WorkSpaces Applications](./eucsus04-bp01.html)