AWS wellarchitected documentation change
Summary
Replaced 'AppStream 2.0' with 'WorkSpaces Applications' in operational documentation about deployment processes and system configurations
Security assessment
These are nomenclature updates rather than security-focused changes. While the documentation touches on security-adjacent topics like SAML and Active Directory integration, the changes themselves don't introduce new security guidance or address specific vulnerabilities.
Diff
diff --git a/wellarchitected/latest/end-user-computing-lens/eucops07-bp01.md b/wellarchitected/latest/end-user-computing-lens/eucops07-bp01.md index 45202b420..cbf66cb07 100644 --- a//wellarchitected/latest/end-user-computing-lens/eucops07-bp01.md +++ b//wellarchitected/latest/end-user-computing-lens/eucops07-bp01.md @@ -25 +25 @@ For each of the following topics, if a manual installation was performed, captur -How were the landing zone and your WorkSpaces or AppStream 2.0 environments created, which options were configured for each service, and why? CloudFormation templates can be used to reliably and repeatably build the baseline infrastructure and the rationale behind the CloudFormation template creation. Deployment and rollback processes can be captured and documented. +How were the landing zone and your WorkSpaces or WorkSpaces Applications environments created, which options were configured for each service, and why? CloudFormation templates can be used to reliably and repeatably build the baseline infrastructure and the rationale behind the CloudFormation template creation. Deployment and rollback processes can be captured and documented. @@ -29 +29 @@ How were the landing zone and your WorkSpaces or AppStream 2.0 environments crea -Your Active Directory and RADIUS deployment and maintenance should be part of a separate operations guide chapter. For WorkSpaces and AppStream 2.0, capture the specifics of how you integrated Active Directory and RADIUS for the respective service. For WorkSpaces, document which directory integration method was used, and capture the manual steps used to deploy or details of the CloudFormation templates used to automate this process. +Your Active Directory and RADIUS deployment and maintenance should be part of a separate operations guide chapter. For WorkSpaces and WorkSpaces Applications, capture the specifics of how you integrated Active Directory and RADIUS for the respective service. For WorkSpaces, document which directory integration method was used, and capture the manual steps used to deploy or details of the CloudFormation templates used to automate this process. @@ -33 +33 @@ Your Active Directory and RADIUS deployment and maintenance should be part of a -How was your SAML 2.0 IdP configured with respect to integration with Amazon WorkSpaces or AppStream 2.0? Which SAML attributes were used to drive AppStream application entitlements? +How was your SAML 2.0 IdP configured with respect to integration with Amazon WorkSpaces or WorkSpaces Applications? Which SAML attributes were used to drive AppStream application entitlements? @@ -47 +47 @@ How were your applications installed and deployed (for example, did you use loca -For AppStream 2.0, did you use session scripts? Document the scripts deployed and what each script does. +For WorkSpaces Applications, did you use session scripts? Document the scripts deployed and what each script does. @@ -55 +55 @@ How should image updates be managed, which version control and naming convention -Which clients are required to access Workspaces or AppStream 2.0 (for example, Windows, macOS, or web), which user groups require each client type, and how should it be installed? How will clients be updated? +Which clients are required to access Workspaces or WorkSpaces Applications (for example, Windows, macOS, or web), which user groups require each client type, and how should it be installed? How will clients be updated?