AWS appstream2 documentation change
Summary
Updated service name references from 'Amazon AppStream 2.0' to 'Amazon WorkSpaces Applications' throughout the troubleshooting guide
Security assessment
The changes appear to be a rebranding update rather than addressing security issues. All modifications are service name replacements without any mention of vulnerabilities, security patches, or new security controls. The content about scaling policies, quotas, and IE settings remains functionally identical from a security perspective.
Diff
diff --git a/appstream2/latest/developerguide/troubleshooting-fleets.md b/appstream2/latest/developerguide/troubleshooting-fleets.md index 44b311ae8..6ea5d90ef 100644 --- a//appstream2/latest/developerguide/troubleshooting-fleets.md +++ b//appstream2/latest/developerguide/troubleshooting-fleets.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 @@ I tried to increase my fleet capacity, but the update isn't taking effect.My app -The following are issues that might occur when users connect to Amazon AppStream 2.0 streaming sessions launched from fleet instances. +The following are issues that might occur when users connect to Amazon WorkSpaces Applications streaming sessions launched from fleet instances. @@ -30 +30 @@ You can increase your fleet capacity in either of the two following ways: - * Manually, by increasing the **Minimum capacity** value on the **Scaling Policies** tab for the fleet in the AppStream 2.0 console. + * Manually, by increasing the **Minimum capacity** value on the **Scaling Policies** tab for the fleet in the WorkSpaces Applications console. @@ -37 +37 @@ You can increase your fleet capacity in either of the two following ways: -If your manual modification or scaling policy exceeds your current AppStream 2.0 quota for your fleet instance type and size, the new values will not take effect. If you experience this issue, you can use the AWS Command Line Interface (CLI) [describe-scaling-activities](https://docs.aws.amazon.com/cli/latest/reference/application-autoscaling/describe-scaling-activities.html) command to verify whether your capacity request exceeds your quota for the applicable fleet instance type and size. This command uses the following format: +If your manual modification or scaling policy exceeds your current WorkSpaces Applications quota for your fleet instance type and size, the new values will not take effect. If you experience this issue, you can use the AWS Command Line Interface (CLI) [describe-scaling-activities](https://docs.aws.amazon.com/cli/latest/reference/application-autoscaling/describe-scaling-activities.html) command to verify whether your capacity request exceeds your quota for the applicable fleet instance type and size. This command uses the following format: @@ -55 +55 @@ The following JSON output shows that a scaling policy for `TestFleet` with a **M -AppStream 2.0 instance type and size quotas are per Amazon Web Services account, per AWS Region. If you have multiple fleets in the same Region that use the same instance type and size, the total number of instances in all fleets in that Region must be less than or equal to the applicable quota. +WorkSpaces Applications instance type and size quotas are per Amazon Web Services account, per AWS Region. If you have multiple fleets in the same Region that use the same instance type and size, the total number of instances in all fleets in that Region must be less than or equal to the applicable quota. @@ -76 +76 @@ If you run the `describe-scaling-activities` command and the output indicates th - * Requesting a quota increase. To request a quota increase, use the [AppStream 2.0 Limits form](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase&limitType=service-code-appstream2). + * Requesting a quota increase. To request a quota increase, use the [WorkSpaces Applications Limits form](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase&limitType=service-code-appstream2). @@ -83 +83 @@ If you run the `describe-scaling-activities` command and the output indicates th -If your AppStream 2.0 environment includes applications that render elements, you might need to restore the Internet Explorer default settings to enable full enable access to the internet. +If your WorkSpaces Applications environment includes applications that render elements, you might need to restore the Internet Explorer default settings to enable full enable access to the internet. @@ -87 +87 @@ If your AppStream 2.0 environment includes applications that render elements, yo - 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). @@ -121 +121 @@ If your AppStream 2.0 environment includes applications that render elements, yo - 9. Follow the required steps in Image Assistant to finish creating your image. For more information, see [Tutorial: Create a Custom AppStream 2.0 Image by Using the AppStream 2.0 Console](./tutorial-image-builder.html). + 9. Follow the required steps in Image Assistant to finish creating your image. For more information, see [Tutorial: Create a Custom WorkSpaces Applications Image by Using the WorkSpaces Applications Console](./tutorial-image-builder.html). @@ -128 +128 @@ If your AppStream 2.0 environment includes applications that render elements, yo -Environment variables enable you to dynamically pass settings across applications. You can make user environment variables and system environment variables available across your fleet instances. You can also create environment variables with limited scope, which is useful when you need to use the same environment variable with different values across different applications. For more information, see [Persist Environment Variables in Amazon AppStream 2.0](./customize-fleets-persist-environment-variables.html). +Environment variables enable you to dynamically pass settings across applications. You can make user environment variables and system environment variables available across your fleet instances. You can also create environment variables with limited scope, which is useful when you need to use the same environment variable with different values across different applications. For more information, see [Persist Environment Variables in Amazon WorkSpaces Applications](./customize-fleets-persist-environment-variables.html). @@ -132 +132 @@ Environment variables enable you to dynamically pass settings across application -You can use Group Policy to set the default home page in Internet Explorer for your users. You can also enable users to change the default page that you set. For more information, see [Change the Default Internet Explorer Home Page for Users' Streaming Sessions in Amazon AppStream 2.0](./customize-fleets-change-ie-homepage.html). +You can use Group Policy to set the default home page in Internet Explorer for your users. You can also enable users to change the default page that you set. For more information, see [Change the Default Internet Explorer Home Page for Users' Streaming Sessions in Amazon WorkSpaces Applications](./customize-fleets-change-ie-homepage.html). @@ -136 +136 @@ You can use Group Policy to set the default home page in Internet Explorer for y -When a user ends a session, AppStream 2.0 terminates the underlying instance and creates a new instance if needed to meet the desired capacity of the fleet. If a user tries to start a new session before AppStream 2.0 creates the new instance and all other instances are in use, the user will receive an error stating that no streaming resources are available. If your users start and stop sessions frequently, consider increasing your fleet capacity. For more information, see [Fleet Auto Scaling for Amazon AppStream 2.0](./autoscaling.html). Or, consider increasing the maximum session duration for your fleet and instructing your users to close their browser during periods of inactivity rather than ending their session. +When a user ends a session, WorkSpaces Applications terminates the underlying instance and creates a new instance if needed to meet the desired capacity of the fleet. If a user tries to start a new session before WorkSpaces Applications creates the new instance and all other instances are in use, the user will receive an error stating that no streaming resources are available. If your users start and stop sessions frequently, consider increasing your fleet capacity. For more information, see [Fleet Auto Scaling for Amazon WorkSpaces Applications](./autoscaling.html). Or, consider increasing the maximum session duration for your fleet and instructing your users to close their browser during periods of inactivity rather than ending their session.