AWS appstream2 documentation change
Summary
Updated service name references from 'Amazon AppStream 2.0' to 'Amazon WorkSpaces Applications' throughout the document, including console names, feature references, and documentation links.
Security assessment
The changes are purely branding updates (service name change) with no evidence of addressing security vulnerabilities or weaknesses. Security-related sections (IAM roles, security groups, VPC configuration) only reflect the service name change without altering security guidance or introducing new security features.
Diff
diff --git a/appstream2/latest/developerguide/set-up-stacks-fleets-create.md b/appstream2/latest/developerguide/set-up-stacks-fleets-create.md index 62d3aff0a..2c563118c 100644 --- a//appstream2/latest/developerguide/set-up-stacks-fleets-create.md +++ b//appstream2/latest/developerguide/set-up-stacks-fleets-create.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 a Fleet in Amazon AppStream 2.0 +# Create a Fleet in Amazon WorkSpaces Applications @@ -11 +11 @@ Set up and create a fleet from which user applications are launched and streamed -To create an Always-On or On-Demand fleet, you must have an image that has applications installed to create an Always-On or On-Demand fleet that your users can stream from. To create an image, see [Tutorial: Create a Custom AppStream 2.0 Image by Using the AppStream 2.0 Console](./tutorial-image-builder.html). To create an Elastic fleet, you must have applications associated to app blocks. To create applications and app blocks for an Elastic fleet, see [Applications Manager](./app-blocks-applications.html). +To create an Always-On or On-Demand fleet, you must have an image that has applications installed to create an Always-On or On-Demand fleet that your users can stream from. To create an image, see [Tutorial: Create a Custom WorkSpaces Applications Image by Using the WorkSpaces Applications Console](./tutorial-image-builder.html). To create an Elastic fleet, you must have applications associated to app blocks. To create applications and app blocks for an Elastic fleet, see [Applications Manager](./app-blocks-applications.html). @@ -15 +15 @@ To create an Always-On or On-Demand fleet, you must have an image that has appli - 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). @@ -23 +23 @@ To create an Always-On or On-Demand fleet, you must have an image that has appli -The fleet type determines its immediate availability and how you pay for it. For more information, see [AppStream 2.0 Fleet Types](./fleet-type.html). +The fleet type determines its immediate availability and how you pay for it. For more information, see [WorkSpaces Applications Fleet Types](./fleet-type.html). @@ -33 +33 @@ The fleet type determines its immediate availability and how you pay for it. For - * For **Choose instance type** , choose the instance type that meets the performance requirements of your applications. All streaming instances in your fleet launch with the instance type that you select. For more information, see [AppStream 2.0 Instance Families](./instance-types.html). + * For **Choose instance type** , choose the instance type that meets the performance requirements of your applications. All streaming instances in your fleet launch with the instance type that you select. For more information, see [WorkSpaces Applications Instance Families](./instance-types.html). @@ -37 +37 @@ The fleet type determines its immediate availability and how you pay for it. For - * For **Maximum session duration in minutes** , choose the maximum amount of time that a streaming session can remain active. If users are still connected to a streaming instance five minutes before this limit is reached, they are prompted to save any open documents before being disconnected. After this time elapses, the instance is terminated and replaced by a new instance. The maximum session duration that you can set in the AppStream 2.0 console is 5760 minutes (96 hours). The maximum session duration that you can set using the AppStream 2.0 API and CLI is 432000 seconds (120 hours). + * For **Maximum session duration in minutes** , choose the maximum amount of time that a streaming session can remain active. If users are still connected to a streaming instance five minutes before this limit is reached, they are prompted to save any open documents before being disconnected. After this time elapses, the instance is terminated and replaced by a new instance. The maximum session duration that you can set in the WorkSpaces Applications console is 5760 minutes (96 hours). The maximum session duration that you can set using the WorkSpaces Applications API and CLI is 432000 seconds (120 hours). @@ -41 +41 @@ The fleet type determines its immediate availability and how you pay for it. For -If a user ends the session by choosing **End Session** or **Logout** on the AppStream 2.0 toolbar, the disconnect timeout does not apply. Instead, the user is prompted to save any open documents, and then immediately disconnected from the streaming instance. The instance the user was using is then terminated. +If a user ends the session by choosing **End Session** or **Logout** on the WorkSpaces Applications toolbar, the disconnect timeout does not apply. Instead, the user is prompted to save any open documents, and then immediately disconnected from the streaming instance. The instance the user was using is then terminated. @@ -61 +61 @@ Multi-session is available only on Always-on and On-demand fleets powered by a W -Only base images and managed image updates released on or after May 15, 2023 support multi-session fleets. For more details, see [AppStream 2.0 Base Image and Managed Image Update Release Notes](./base-image-version-history.html). +Only base images and managed image updates released on or after May 15, 2023 support multi-session fleets. For more details, see [WorkSpaces Applications Base Image and Managed Image Update Release Notes](./base-image-version-history.html). @@ -73 +73 @@ For multi-session, you must specify the capacity based on the number of user ses - * For **Stream view** , choose the AppStream 2.0 view that is displayed to your users during their streaming sessions. Choose **Application** to display only the windows of applications opened by users. Choose **Desktop** to display the standard desktop that is provided by the operating system. + * For **Stream view** , choose the WorkSpaces Applications view that is displayed to your users during their streaming sessions. Choose **Application** to display only the windows of applications opened by users. Choose **Desktop** to display the standard desktop that is provided by the operating system. @@ -77 +77 @@ For multi-session, you must specify the capacity based on the number of user ses -By default, AppStream 2.0 displays only the windows of applications opened by users during their streaming sessions. To enable **Desktop** view for your users, configure your fleet to use an AppStream 2.0 image that uses a version of the AppStream 2.0 agent released on or after February 19, 2020. +By default, WorkSpaces Applications displays only the windows of applications opened by users during their streaming sessions. To enable **Desktop** view for your users, configure your fleet to use an WorkSpaces Applications image that uses a version of the WorkSpaces Applications agent released on or after February 19, 2020. @@ -79 +79 @@ By default, AppStream 2.0 displays only the windows of applications opened by us - * For **Scaling details (Advanced)** , specify the scaling policies that AppStream 2.0 uses to increase and decrease the capacity of your fleet. Note that the size of your fleet is limited by the minimum and maximum capacity that you specified. For more information, see [Fleet Auto Scaling for Amazon AppStream 2.0](./autoscaling.html). + * For **Scaling details (Advanced)** , specify the scaling policies that WorkSpaces Applications uses to increase and decrease the capacity of your fleet. Note that the size of your fleet is limited by the minimum and maximum capacity that you specified. For more information, see [Fleet Auto Scaling for Amazon WorkSpaces Applications](./autoscaling.html). @@ -81 +81 @@ By default, AppStream 2.0 displays only the windows of applications opened by us - * For **IAM role (Advanced)** , when you apply an IAM role from your account to an AppStream 2.0 fleet instance, you can make AWS API requests from the fleet instance without manually managing AWS credentials. To apply an IAM role, do either of the following: + * For **IAM role (Advanced)** , when you apply an IAM role from your account to an WorkSpaces Applications fleet instance, you can make AWS API requests from the fleet instance without manually managing AWS credentials. To apply an IAM role, do either of the following: @@ -83 +83 @@ By default, AppStream 2.0 displays only the windows of applications opened by us - * To use an existing IAM role in your AWS account, choose the role that you want to use from the **IAM role** list. The role must be accessible from the fleet instance. For more information, see [Configuring an Existing IAM Role to Use With AppStream 2.0 Streaming Instances](./configuring-existing-iam-role-to-use-with-streaming-instances.html). + * To use an existing IAM role in your AWS account, choose the role that you want to use from the **IAM role** list. The role must be accessible from the fleet instance. For more information, see [Configuring an Existing IAM Role to Use With WorkSpaces Applications Streaming Instances](./configuring-existing-iam-role-to-use-with-streaming-instances.html). @@ -85 +85 @@ By default, AppStream 2.0 displays only the windows of applications opened by us - * To create a new IAM role, choose **Create new IAM role** and follow the steps in [How to Create an IAM Role to Use With AppStream 2.0 Streaming Instances](./how-to-create-iam-role-to-use-with-streaming-instances.html). + * To create a new IAM role, choose **Create new IAM role** and follow the steps in [How to Create an IAM Role to Use With WorkSpaces Applications Streaming Instances](./how-to-create-iam-role-to-use-with-streaming-instances.html). @@ -101 +101 @@ By default, AppStream 2.0 displays only the windows of applications opened by us -Your VPC must provide access to Amazon Simple Storage Service (S3) if you enable features that rely on saving to an S3 bucket. For more information, see [Using Amazon S3 VPC Endpoints for AppStream 2.0 Features](./managing-network-vpce-iam-policy.html). +Your VPC must provide access to Amazon Simple Storage Service (S3) if you enable features that rely on saving to an S3 bucket. For more information, see [Using Amazon S3 VPC Endpoints for WorkSpaces Applications Features](./managing-network-vpce-iam-policy.html). @@ -109 +109 @@ Elastic fleets require that you specify at least two subnets that are in differe -If you don't have your own VPC and subnet, you can use the [default VPC](./default-vpc-with-public-subnet.html) or create your own. To create your own, choose the **Create a new VPC** and **Create new subnet** links to create them. Choosing these links opens the Amazon VPC console. After you create your VPC and subnets, return to the AppStream 2.0 console and choose the refresh icon to the left of the **Create a new VPC** and **Create new subnet** links to display them in the list. For more information, see [Configure a VPC for AppStream 2.0](./appstream-vpc.html). +If you don't have your own VPC and subnet, you can use the [default VPC](./default-vpc-with-public-subnet.html) or create your own. To create your own, choose the **Create a new VPC** and **Create new subnet** links to create them. Choosing these links opens the Amazon VPC console. After you create your VPC and subnets, return to the WorkSpaces Applications console and choose the refresh icon to the left of the **Create a new VPC** and **Create new subnet** links to display them in the list. For more information, see [Configure a VPC for WorkSpaces Applications](./appstream-vpc.html). @@ -111 +111 @@ If you don't have your own VPC and subnet, you can use the [default VPC](./defau - * For **Security group(s)** , choose up to five security groups to associate with this fleet. If you don't have your own security group and you don't want to use the default security group, choose the **Create new security group** link to create one. After you create your subnets in the Amazon VPC console, return to the AppStream 2.0 console and choose the refresh icon to the left of the **Create new security group** link to display them in the list. For more information, see [Security Groups in Amazon AppStream 2.0](./managing-network-security-groups.html). + * For **Security group(s)** , choose up to five security groups to associate with this fleet. If you don't have your own security group and you don't want to use the default security group, choose the **Create new security group** link to create one. After you create your subnets in the Amazon VPC console, return to the WorkSpaces Applications console and choose the refresh icon to the left of the **Create new security group** link to display them in the list. For more information, see [Security Groups in Amazon WorkSpaces Applications](./managing-network-security-groups.html). @@ -113 +113 @@ If you don't have your own VPC and subnet, you can use the [default VPC](./defau - * For Always-On and On-Demand fleets, for **Active Directory Domain (Optional)** , choose the Active Directory and organizational unit (OU) for your streaming instance computer objects. Ensure that the network access settings you selected enable DNS resolvability and communication with your directory. For more information, see [Using Active Directory with AppStream 2.0](./active-directory.html). + * For Always-On and On-Demand fleets, for **Active Directory Domain (Optional)** , choose the Active Directory and organizational unit (OU) for your streaming instance computer objects. Ensure that the network access settings you selected enable DNS resolvability and communication with your directory. For more information, see [Using Active Directory with WorkSpaces Applications](./active-directory.html).