AWS appstream2 documentation change
Summary
Updated product name references from 'Amazon AppStream 2.0' to 'Amazon WorkSpaces Applications' throughout the documentation
Security assessment
The changes are purely branding updates with no mention of security vulnerabilities, mitigations, or new security features. All technical content about setup script execution context (SYSTEM/root privileges) and logging remains unchanged.
Diff
diff --git a/appstream2/latest/developerguide/create-setup-script.md b/appstream2/latest/developerguide/create-setup-script.md index 0817d6950..9b917f536 100644 --- a//appstream2/latest/developerguide/create-setup-script.md +++ b//appstream2/latest/developerguide/create-setup-script.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) @@ -5 +5 @@ -# Create the Setup Script for the VHD in Amazon AppStream 2.0 +# Create the Setup Script for the VHD in Amazon WorkSpaces Applications @@ -7 +7 @@ -AppStream 2.0 uses a setup script that you provide to mount the VHD before the application launches. You can also use the setup script to complete other tasks required to make your application work. For example, you can configure registry keys, register DLLs, manage pre-requisites, or modify the user profile from the setup script. AppStream 2.0 provides script examples that you can use to mount your VHD. You will need to modify these scripts for your VHD and application needs. +WorkSpaces Applications uses a setup script that you provide to mount the VHD before the application launches. You can also use the setup script to complete other tasks required to make your application work. For example, you can configure registry keys, register DLLs, manage pre-requisites, or modify the user profile from the setup script. WorkSpaces Applications provides script examples that you can use to mount your VHD. You will need to modify these scripts for your VHD and application needs. @@ -11 +11 @@ AppStream 2.0 uses a setup script that you provide to mount the VHD before the a -Setup scripts aren't required for app blocks with AppStream 2.0 packaging. However, you can provide optional post-setup scripts to customize application installation. +Setup scripts aren't required for app blocks with WorkSpaces Applications packaging. However, you can provide optional post-setup scripts to customize application installation. @@ -21 +21 @@ Use the following links to download the example scripts: -AppStream 2.0 and the Microsoft Windows operating system reserve drive letters A through E. Don't mount VHDs or network shares to these drive letters. +WorkSpaces Applications and the Microsoft Windows operating system reserve drive letters A through E. Don't mount VHDs or network shares to these drive letters. @@ -26 +26 @@ AppStream 2.0 and the Microsoft Windows operating system reserve drive letters A -AppStream 2.0 downloads the setup script and VHD to a directory on the fleet streaming instance, then runs the setup script. The setup script runs on the operating system with full administrator rights. The setup script runs in the `SYSTEM` context on Microsoft Windows, and as the `root` user on Amazon Linux 2. +WorkSpaces Applications downloads the setup script and VHD to a directory on the fleet streaming instance, then runs the setup script. The setup script runs on the operating system with full administrator rights. The setup script runs in the `SYSTEM` context on Microsoft Windows, and as the `root` user on Amazon Linux 2. @@ -51 +51 @@ The name of the app block that the VHD and setup script correspond to. -AppStream 2.0 maintains the file name as they are on the object. For example, if your app block is named `MyApps`, with a VHD named `apps.vhd` and setup script named `mount-apps.ps1`, then the full path on a Windows streaming instance is: +WorkSpaces Applications maintains the file name as they are on the object. For example, if your app block is named `MyApps`, with a VHD named `apps.vhd` and setup script named `mount-apps.ps1`, then the full path on a Windows streaming instance is: @@ -64 +64 @@ AppStream 2.0 maintains the file name as they are on the object. For example, if -AppStream 2.0 captures the standard error and standard output from your setup script when it runs on a fleet streaming instance and uploads the output to an Amazon S3 bucket within your account. You can use these logs to identify and resolve issues you may have with your setup script. The buckets are named in a specific format as follows: +WorkSpaces Applications captures the standard error and standard output from your setup script when it runs on a fleet streaming instance and uploads the output to an Amazon S3 bucket within your account. You can use these logs to identify and resolve issues you may have with your setup script. The buckets are named in a specific format as follows: @@ -79 +79 @@ Your AWS account identifier. The random ID ensures that there is no conflict wit -For example, if you create an elastic fleet in the US West (Oregon) Region (us-west-2) on account number 123456789012, AppStream 2.0 creates an Amazon S3 bucket within your account in that Region with the name shown. Only an administrator with sufficient permissions can delete this bucket. +For example, if you create an elastic fleet in the US West (Oregon) Region (us-west-2) on account number 123456789012, WorkSpaces Applications creates an Amazon S3 bucket within your account in that Region with the name shown. Only an administrator with sufficient permissions can delete this bucket. @@ -112 +112 @@ This example folder structure contains one log file for the standard output, and - * [App block setup script execution in Amazon AppStream 2.0](./script-execution.html) + * [App block setup script execution in Amazon WorkSpaces Applications](./script-execution.html)