AWS appstream2 documentation change
Summary
Updated service name references from 'Amazon AppStream 2.0' to 'Amazon WorkSpaces Applications' throughout the troubleshooting guide, including console/API references and resolution steps.
Security assessment
The changes are purely branding updates and documentation alignment with the new service name. No security vulnerabilities, mitigations, or new security features are introduced. The content about password expiration, network connectivity checks, and Active Directory configuration remains functionally identical but uses the updated service name.
Diff
diff --git a/appstream2/latest/developerguide/troubleshooting-notification-codes.md b/appstream2/latest/developerguide/troubleshooting-notification-codes.md index e1471ef01..3940f47f9 100644 --- a//appstream2/latest/developerguide/troubleshooting-notification-codes.md +++ b//appstream2/latest/developerguide/troubleshooting-notification-codes.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 @@ Active Directory Internal ServiceActive Directory Domain JoinImage Internal Serv -The following are notification codes and resolution steps for notifications that you might see when you set up and use Amazon AppStream 2.0. These notifications can be found in the **Notifications** tab in the AppStream 2.0 console, after selecting an image builder or fleet. You can also get fleet notifications by using the AppStream 2.0 API operation [DescribeFleets](https://docs.aws.amazon.com/appstream2/latest/APIReference/API_DescribeFleets.html) or the [describe-fleets](https://docs.aws.amazon.com/cli/latest/reference/appstream/describe-fleets.html) CLI command. +The following are notification codes and resolution steps for notifications that you might see when you set up and use Amazon WorkSpaces Applications. These notifications can be found in the **Notifications** tab in the WorkSpaces Applications console, after selecting an image builder or fleet. You can also get fleet notifications by using the WorkSpaces Applications API operation [DescribeFleets](https://docs.aws.amazon.com/appstream2/latest/APIReference/API_DescribeFleets.html) or the [describe-fleets](https://docs.aws.amazon.com/cli/latest/reference/appstream/describe-fleets.html) CLI command. @@ -13 +13 @@ The following are notification codes and resolution steps for notifications that -Follow these steps if you receive an internal service error when you set up and use Active Directory with Amazon AppStream 2.0. +Follow these steps if you receive an internal service error when you set up and use Active Directory with Amazon WorkSpaces Applications. @@ -24 +24 @@ Follow these steps if you receive an internal service error when you set up and -The following are notification codes and resolution steps for issues with domain join that you might encounter when you set up and use Active Directory with Amazon AppStream 2.0. +The following are notification codes and resolution steps for issues with domain join that you might encounter when you set up and use Active Directory with Amazon WorkSpaces Applications. @@ -45 +45 @@ The following are notification codes and resolution steps for issues with domain -**Resolution** : The password for the service account specified in the AppStream 2.0 directory configuration has expired. Change the password for the service account in your Active Directory domain, update the configuration, and then re-create the image builder or fleet that had the error. +**Resolution** : The password for the service account specified in the WorkSpaces Applications directory configuration has expired. Change the password for the service account in your Active Directory domain, update the configuration, and then re-create the image builder or fleet that had the error. @@ -73 +73 @@ The following are notification codes and resolution steps for issues with domain -**Resolution** : The streaming instance was unable to contact your Active Directory domain. To ensure network connectivity, confirm your VPC, subnet, and security group settings. For more information, see [My AppStream 2.0 streaming instances aren't joining the Active Directory domain.](./troubleshooting-active-directory.html#troubleshooting-active-directory-5) +**Resolution** : The streaming instance was unable to contact your Active Directory domain. To ensure network connectivity, confirm your VPC, subnet, and security group settings. For more information, see [My WorkSpaces Applications streaming instances aren't joining the Active Directory domain.](./troubleshooting-active-directory.html#troubleshooting-active-directory-5) @@ -107 +107 @@ The following are notification codes and resolution steps for issues with domain - * After AppStream 2.0 creates the computer object, it is moved from the OU in which it was created. In this case, the first image builder or fleet is created successfully, but any new image builder or fleet that uses the computer object fails. When Active Directory searches for the computer object in the specified OU and detects that an object with the same name exists elsewhere in the domain, the domain join is not successful. + * After WorkSpaces Applications creates the computer object, it is moved from the OU in which it was created. In this case, the first image builder or fleet is created successfully, but any new image builder or fleet that uses the computer object fails. When Active Directory searches for the computer object in the specified OU and detects that an object with the same name exists elsewhere in the domain, the domain join is not successful. @@ -109 +109 @@ The following are notification codes and resolution steps for issues with domain - * The name of the OU specified in the AppStream 2.0 Directory Config includes spaces before or after the commas in the directory configuration. In this case, 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. To resolve this issue for a fleet, do the following: + * The name of the OU specified in the WorkSpaces Applications Directory Config includes spaces before or after the commas in the directory configuration. In this case, 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. To resolve this issue for a fleet, do the following: @@ -115 +115 @@ The following are notification codes and resolution steps for issues with domain - 3. Update the AppStream 2.0 Directory Config to specify an OU that doesn't contain spaces. For more information, see [Step 1: Create a Directory Config Object](./active-directory-directory-setup.html#active-directory-setup-config). + 3. Update the WorkSpaces Applications Directory Config to specify an OU that doesn't contain spaces. For more information, see [Step 1: Create a Directory Config Object](./active-directory-directory-setup.html#active-directory-setup-config). @@ -123 +123 @@ To resolve this issue for an image builder, do the following: - 2. Update the AppStream 2.0 Directory Config to specify an OU that doesn't contain spaces. For more information, see [Step 1: Create a Directory Config Object](./active-directory-directory-setup.html#active-directory-setup-config). + 2. Update the WorkSpaces Applications Directory Config to specify an OU that doesn't contain spaces. For more information, see [Step 1: Create a Directory Config Object](./active-directory-directory-setup.html#active-directory-setup-config). @@ -132 +132 @@ To resolve this issue for an image builder, do the following: -If you receive an internal service error after you use managed AppStream 2.0 image updates to initiate an image update, follow these steps. +If you receive an internal service error after you use managed WorkSpaces Applications image updates to initiate an image update, follow these steps. @@ -137 +137 @@ If you receive an internal service error after you use managed AppStream 2.0 ima -**Message** : AppStream 2.0 could not update image `image-name`. Failed to update/install/configure/disable <software name>. Check your source image and try again. If this problem persists, contact AWS Support. +**Message** : WorkSpaces Applications could not update image `image-name`. Failed to update/install/configure/disable <software name>. Check your source image and try again. If this problem persists, contact AWS Support. @@ -141 +141 @@ If you receive an internal service error after you use managed AppStream 2.0 ima -If updating again doesn't work, make sure that you're using the latest version of SSM Agent. For version information, see [AppStream 2.0 Base Image and Managed Image Update Release Notes](./base-image-version-history.html). For installation information, see [Manually install SSM Agent on EC2 instances for Windows Server](https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-install-win.html). +If updating again doesn't work, make sure that you're using the latest version of SSM Agent. For version information, see [WorkSpaces Applications Base Image and Managed Image Update Release Notes](./base-image-version-history.html). For installation information, see [Manually install SSM Agent on EC2 instances for Windows Server](https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-install-win.html).