AWS appstream2 documentation change
Summary
Updated references from 'Amazon AppStream 2.0' to 'Amazon WorkSpaces Applications' throughout the document. Adjusted configuration guidance to use WorkSpaces Applications terminology.
Security assessment
The changes are primarily branding updates (AppStream 2.0 to WorkSpaces Applications) and do not introduce new security content or address specific vulnerabilities. The existing security recommendation to use NAT gateways instead of Elastic IPs remains unchanged but is now associated with the new service name.
Diff
diff --git a/appstream2/latest/developerguide/managing-network-default-internet-access.md b/appstream2/latest/developerguide/managing-network-default-internet-access.md index 47875f925..856eab133 100644 --- a//appstream2/latest/developerguide/managing-network-default-internet-access.md +++ b//appstream2/latest/developerguide/managing-network-default-internet-access.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: Configure a VPC with a Public SubnetStep 2: Enable Default Internet Acce -If you created your Amazon Web Services account after 2013-12-04, you have a [default VPC](./default-vpc-with-public-subnet.html) in each AWS Region that includes default public subnets. However, you may want to create your own nondefault VPC or configure an existing VPC to use with AppStream 2.0. This topic describes how to configure a nondefault VPC and public subnet to use with AppStream 2.0. +If you created your Amazon Web Services account after 2013-12-04, you have a [default VPC](./default-vpc-with-public-subnet.html) in each AWS Region that includes default public subnets. However, you may want to create your own nondefault VPC or configure an existing VPC to use with WorkSpaces Applications. This topic describes how to configure a nondefault VPC and public subnet to use with WorkSpaces Applications. @@ -11 +11 @@ If you created your Amazon Web Services account after 2013-12-04, you have a [de -After you configure your VPC and public subnet, you can provide your streaming instances (fleet instances and image builders) with access to the internet by enabling the **Default Internet Access** option. When you enable this option, AppStream 2.0 enables internet connectivity by associating an [Elastic IP address](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/elastic-ip-addresses-eip.html) to the network interface that is attached from the streaming instance to your public subnet. An Elastic IP address is a public IPv4 address that is reachable from the internet. For this reason, we recommend that you instead use a NAT gateway to provide internet access to your AppStream 2.0 instances. In addition, when **Default Internet Access** is enabled, a maximum of 100 fleet instances is supported. If your deployment must support more than 100 concurrent users, use the [NAT gateway configuration](./managing-network-internet-NAT-gateway.html) instead. +After you configure your VPC and public subnet, you can provide your streaming instances (fleet instances and image builders) with access to the internet by enabling the **Default Internet Access** option. When you enable this option, WorkSpaces Applications enables internet connectivity by associating an [Elastic IP address](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/elastic-ip-addresses-eip.html) to the network interface that is attached from the streaming instance to your public subnet. An Elastic IP address is a public IPv4 address that is reachable from the internet. For this reason, we recommend that you instead use a NAT gateway to provide internet access to your WorkSpaces Applications instances. In addition, when **Default Internet Access** is enabled, a maximum of 100 fleet instances is supported. If your deployment must support more than 100 concurrent users, use the [NAT gateway configuration](./managing-network-internet-NAT-gateway.html) instead. @@ -50 +50 @@ If you want to use an existing VPC that does not have a public subnet, you can a - 1. To add a public subnet, complete the steps in [Creating a Subnet in Your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/working-with-vpcs.html#AddaSubnet). Use the existing VPC that you plan to use with AppStream 2.0. + 1. To add a public subnet, complete the steps in [Creating a Subnet in Your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/working-with-vpcs.html#AddaSubnet). Use the existing VPC that you plan to use with WorkSpaces Applications. @@ -77 +77 @@ For fleet instances that have the **Default Internet Access** option enabled, th - 1. Complete the steps in [Create a Fleet in Amazon AppStream 2.0](./set-up-stacks-fleets-create.html) up to **Step 4: Configure Network**. + 1. Complete the steps in [Create a Fleet in Amazon WorkSpaces Applications](./set-up-stacks-fleets-create.html) up to **Step 4: Configure Network**. @@ -83 +83 @@ For fleet instances that have the **Default Internet Access** option enabled, th - 4. Continue with the steps in [Create a Fleet in Amazon AppStream 2.0](./set-up-stacks-fleets-create.html). + 4. Continue with the steps in [Create a Fleet in Amazon WorkSpaces Applications](./set-up-stacks-fleets-create.html). @@ -101 +101 @@ For fleet instances that have the **Default Internet Access** option enabled, th -You can test internet connectivity by starting your fleet, creating a stack, associating the fleet with a stack, and browsing the internet within a streaming session for stack. For more information, see [Create an Amazon AppStream 2.0 Fleet and Stack](./set-up-stacks-fleets.html). +You can test internet connectivity by starting your fleet, creating a stack, associating the fleet with a stack, and browsing the internet within a streaming session for stack. For more information, see [Create an Amazon WorkSpaces Applications Fleet and Stack](./set-up-stacks-fleets.html).