AWS appstream2 documentation change
Summary
Updated product name references from 'AppStream 2.0' to 'WorkSpaces Applications' throughout the document. Adjusted console names, SDK references, and links to align with the rebranding. No functional changes to procedures or security requirements.
Security assessment
The changes are purely branding updates (renaming 'AppStream 2.0' to 'WorkSpaces Applications') without modifying security protocols, addressing vulnerabilities, or introducing new security features. The existing security guidance about OU name restrictions and domain join requirements remains unchanged except for service name substitutions.
Diff
diff --git a/appstream2/latest/developerguide/active-directory-directory-setup.md b/appstream2/latest/developerguide/active-directory-directory-setup.md index 65f4c22e6..aaca16c66 100644 --- a//appstream2/latest/developerguide/active-directory-directory-setup.md +++ b//appstream2/latest/developerguide/active-directory-directory-setup.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) @@ -9 +9 @@ Step 1: Create a Directory Config ObjectStep 2: Create an Image by Using a Domai -To use Active Directory with AppStream 2.0, you must first register your directory configuration by creating a Directory Config object in AppStream 2.0. This object includes the information required to join streaming instances to an Active Directory domain. You create a Directory Config object by using the AppStream 2.0 management console, AWS SDK, or AWS CLI. You can then use your directory configuration to launch domain-joined Always-On and On-Demand fleets and image builders. +To use Active Directory with WorkSpaces Applications, you must first register your directory configuration by creating a Directory Config object in WorkSpaces Applications. This object includes the information required to join streaming instances to an Active Directory domain. You create a Directory Config object by using the WorkSpaces Applications management console, AWS SDK, or AWS CLI. You can then use your directory configuration to launch domain-joined Always-On and On-Demand fleets and image builders. @@ -30 +30 @@ You can only join Always-On and On-Demand fleet streaming instances to an Active -The Directory Config object that you create in AppStream 2.0 will be used in later steps. +The Directory Config object that you create in WorkSpaces Applications will be used in later steps. @@ -34 +34 @@ If you are using the AWS SDK, you can use the [CreateDirectoryConfig](https://do -###### To create a Directory Config object by using the AppStream 2.0 console +###### To create a Directory Config object by using the WorkSpaces Applications console @@ -36 +36 @@ If you are using the AWS SDK, you can use the [CreateDirectoryConfig](https://do - 1. Open the AppStream 2.0 console at [https://console.aws.amazon.com/appstream2](https://console.aws.amazon.com/appstream2). + 1. Open the WorkSpaces Applications console at [https://console.aws.amazon.com/appstream2](https://console.aws.amazon.com/appstream2). @@ -50 +50 @@ If you are using the AWS SDK, you can use the [CreateDirectoryConfig](https://do -The OU name can't contain spaces. If you specify an OU name that contains spaces, when a fleet or image builder attempts to rejoin the Active Directory domain, AppStream 2.0 cannot cycle the computer objects correctly and the domain rejoin does not succeed. For information about how to troubleshoot this issue, see the _DOMAIN_JOIN_INTERNAL_SERVICE_ERROR_ topic for "The account already exists" message in [Active Directory Domain Join](./troubleshooting-notification-codes.html#troubleshooting-notification-codes-ad). +The OU name can't contain spaces. If you specify an OU name that contains spaces, when a fleet or image builder attempts to rejoin the Active Directory domain, WorkSpaces Applications cannot cycle the computer objects correctly and the domain rejoin does not succeed. For information about how to troubleshoot this issue, see the _DOMAIN_JOIN_INTERNAL_SERVICE_ERROR_ topic for "The account already exists" message in [Active Directory Domain Join](./troubleshooting-notification-codes.html#troubleshooting-notification-codes-ad). @@ -52 +52 @@ The OU name can't contain spaces. If you specify an OU name that contains spaces -In addition, the default Computers container is not an OU and cannot be used by AppStream 2.0. For more information, see [Finding the Organizational Unit Distinguished Name](./active-directory-oudn.html). +In addition, the default Computers container is not an OU and cannot be used by WorkSpaces Applications. For more information, see [Finding the Organizational Unit Distinguished Name](./active-directory-oudn.html). @@ -65 +65 @@ In addition, the default Computers container is not an OU and cannot be used by -Next, using the AppStream 2.0 image builder, create a new image with Active Directory domain-join capabilities. Note that the fleet and image can be members of different domains. You join the image builder to a domain to enable domain join and to install applications. Fleet domain join is discussed in the next section. +Next, using the WorkSpaces Applications image builder, create a new image with Active Directory domain-join capabilities. Note that the fleet and image can be members of different domains. You join the image builder to a domain to enable domain join and to install applications. Fleet domain join is discussed in the next section. @@ -69 +69 @@ Next, using the AppStream 2.0 image builder, create a new image with Active Dire - 1. Follow the procedures in [Tutorial: Create a Custom AppStream 2.0 Image by Using the AppStream 2.0 Console](./tutorial-image-builder.html). + 1. Follow the procedures in [Tutorial: Create a Custom WorkSpaces Applications Image by Using the WorkSpaces Applications Console](./tutorial-image-builder.html). @@ -71 +71 @@ Next, using the AppStream 2.0 image builder, create a new image with Active Dire - 2. For the base image selection step, use an AWS base image released on or after July 24, 2017. For a current list of released AWS images, see [AppStream 2.0 Base Image and Managed Image Update Release Notes](./base-image-version-history.html). + 2. For the base image selection step, use an AWS base image released on or after July 24, 2017. For a current list of released AWS images, see [WorkSpaces Applications Base Image and Managed Image Update Release Notes](./base-image-version-history.html). @@ -83 +83 @@ Next, using the AppStream 2.0 image builder, create a new image with Active Dire - 8. Complete the steps in [Tutorial: Create a Custom AppStream 2.0 Image by Using the AppStream 2.0 Console](./tutorial-image-builder.html) to install applications and create a new image. + 8. Complete the steps in [Tutorial: Create a Custom WorkSpaces Applications Image by Using the WorkSpaces Applications Console](./tutorial-image-builder.html) to install applications and create a new image. @@ -94 +94 @@ Using the private image created in the previous step, create an Active Directory - 1. Follow the procedures in [Create a Fleet in Amazon AppStream 2.0](./set-up-stacks-fleets-create.html). + 1. Follow the procedures in [Create a Fleet in Amazon WorkSpaces Applications](./set-up-stacks-fleets-create.html). @@ -104 +104 @@ Using the private image created in the previous step, create an Active Directory - 6. Complete the remaining steps in [Create an Amazon AppStream 2.0 Fleet and Stack](./set-up-stacks-fleets.html) so that your fleet is associated with a stack and running. + 6. Complete the remaining steps in [Create an Amazon WorkSpaces Applications Fleet and Stack](./set-up-stacks-fleets.html) so that your fleet is associated with a stack and running. @@ -117 +117 @@ Your users must use your SAML 2.0-based identity federation environment to launc - 2. AppStream 2.0 requires that the SAML_Subject `NameID` value for the user who is logging in be provided in either of the following formats: + 2. WorkSpaces Applications requires that the SAML_Subject `NameID` value for the user who is logging in be provided in either of the following formats: @@ -125 +125 @@ If you are using the sAMAccountName format, you can specify the ``domain`` by us - 3. Provide access to your Active Directory users or groups to enable access to the AppStream 2.0 stack from your identity provider application portal. + 3. Provide access to your Active Directory users or groups to enable access to the WorkSpaces Applications stack from your identity provider application portal. @@ -134 +134 @@ If you are using the sAMAccountName format, you can specify the ``domain`` by us - 1. Log in to your SAML 2.0 provider's application catalog and open the AppStream 2.0 SAML application that you created in the previous procedure. + 1. Log in to your SAML 2.0 provider's application catalog and open the WorkSpaces Applications SAML application that you created in the previous procedure. @@ -136 +136 @@ If you are using the sAMAccountName format, you can specify the ``domain`` by us - 2. When the AppStream 2.0 application catalog is displayed, select an application to launch. + 2. When the WorkSpaces Applications application catalog is displayed, select an application to launch.