AWS appstream2 documentation change
Summary
Updated product name references from 'AppStream 2.0' to 'WorkSpaces Applications' throughout the document
Security assessment
The changes are purely branding updates replacing 'AppStream 2.0' with 'WorkSpaces Applications'. No security-related content was added or modified beyond product naming.
Diff
diff --git a/appstream2/latest/developerguide/active-directory-overview.md b/appstream2/latest/developerguide/active-directory-overview.md index 8bca15c28..3df3effb1 100644 --- a//appstream2/latest/developerguide/active-directory-overview.md +++ b//appstream2/latest/developerguide/active-directory-overview.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) @@ -7 +7 @@ -Using Active Directory domains with AppStream 2.0 requires an understanding of how they work together and the configuration tasks that you'll need to complete. You'll need to complete the following tasks: +Using Active Directory domains with WorkSpaces Applications requires an understanding of how they work together and the configuration tasks that you'll need to complete. You'll need to complete the following tasks: @@ -11 +11 @@ Using Active Directory domains with AppStream 2.0 requires an understanding of h - 2. Create the domain-joined application stack in AppStream 2.0. + 2. Create the domain-joined application stack in WorkSpaces Applications. @@ -13 +13 @@ Using Active Directory domains with AppStream 2.0 requires an understanding of h - 3. Create the AppStream 2.0 application in the SAML 2.0 identity provider and assign it to end users either directly or through Active Directory groups. + 3. Create the WorkSpaces Applications application in the SAML 2.0 identity provider and assign it to end users either directly or through Active Directory groups. @@ -18 +18 @@ Using Active Directory domains with AppStream 2.0 requires an understanding of h -For your users to be authenticated to a domain, several steps must occur when these users initiate an AppStream 2.0 streaming session. The following diagram illustrates the end-to-end user authentication flow from the initial browser request through SAML and Active Directory authentication. +For your users to be authenticated to a domain, several steps must occur when these users initiate an WorkSpaces Applications streaming session. The following diagram illustrates the end-to-end user authentication flow from the initial browser request through SAML and Active Directory authentication. @@ -32 +32 @@ For your users to be authenticated to a domain, several steps must occur when th - 5. The user's browser posts the SAML assertion to the AWS Sign-In SAML endpoint (`https://signin.aws.amazon.com/saml`). AWS Sign-In receives the SAML request, processes the request, authenticates the user, and forwards the authentication token to the AppStream 2.0 service. + 5. The user's browser posts the SAML assertion to the AWS Sign-In SAML endpoint (`https://signin.aws.amazon.com/saml`). AWS Sign-In receives the SAML request, processes the request, authenticates the user, and forwards the authentication token to the WorkSpaces Applications service. @@ -34 +34 @@ For your users to be authenticated to a domain, several steps must occur when th - 6. Using the authentication token from AWS, AppStream 2.0 authorizes the user and presents applications to the browser. + 6. Using the authentication token from AWS, WorkSpaces Applications authorizes the user and presents applications to the browser. @@ -36 +36 @@ For your users to be authenticated to a domain, several steps must occur when th - 7. The user chooses an application and, depending on the Windows login authentication method that is enabled on the AppStream 2.0 stack, they're prompted to enter their Active Directory domain password or choose a smart card. If both authentication methods are enabled, the user can choose whether to enter their domain password or use their smart card. Certificate-based authentication can also be used to authenticate users, removing the prompt. + 7. The user chooses an application and, depending on the Windows login authentication method that is enabled on the WorkSpaces Applications stack, they're prompted to enter their Active Directory domain password or choose a smart card. If both authentication methods are enabled, the user can choose whether to enter their domain password or use their smart card. Certificate-based authentication can also be used to authenticate users, removing the prompt. @@ -45 +45 @@ For your users to be authenticated to a domain, several steps must occur when th -From the user's perspective, this process is transparent. The user starts by navigating to your organization's internal portal and is redirected to an AppStream 2.0 application portal, without having to enter AWS credentials. Only an Active Directory domain password or smart card credentials are required. +From the user's perspective, this process is transparent. The user starts by navigating to your organization's internal portal and is redirected to an WorkSpaces Applications application portal, without having to enter AWS credentials. Only an Active Directory domain password or smart card credentials are required.