AWS appstream2 documentation change
Summary
Updated service name references from 'AppStream 2.0' to 'Amazon WorkSpaces Applications' throughout the document. Technical content about management ports (8000/8443), IPv6 requirements, and DNS configuration remains unchanged but uses new branding.
Security assessment
The changes are purely branding updates with no modifications to security configurations or vulnerability disclosures. The existing security guidance about port requirements and IPv6 remains unchanged.
Diff
diff --git a/appstream2/latest/developerguide/management_ports.md b/appstream2/latest/developerguide/management_ports.md index 7aecb337c..d8b5d0808 100644 --- a//appstream2/latest/developerguide/management_ports.md +++ b//appstream2/latest/developerguide/management_ports.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 @@ -# Management Network Interface IP Address Range and Ports in Amazon AppStream 2.0 +# Management Network Interface IP Address Range and Ports in Amazon WorkSpaces Applications @@ -11 +11 @@ The management network interface IP address range is 198.19.0.0/16. The followin - * Inbound TCP on ports 8000 and 8443. These are used for management of the streaming instance by AppStream 2.0. + * Inbound TCP on ports 8000 and 8443. These are used for management of the streaming instance by WorkSpaces Applications. @@ -22 +22 @@ Limit the inbound range on the management network interface to 198.19.0.0/16. -Under normal circumstances, AppStream 2.0 correctly configures these ports for your streaming instances. If any security or firewall software is installed on a streaming instance that blocks any of these ports, the streaming instance may not function correctly or may be unreachable. +Under normal circumstances, WorkSpaces Applications correctly configures these ports for your streaming instances. If any security or firewall software is installed on a streaming instance that blocks any of these ports, the streaming instance may not function correctly or may be unreachable. @@ -24 +24 @@ Under normal circumstances, AppStream 2.0 correctly configures these ports for y -Do not disable IPv6. If you disable IPv6, AppStream 2.0 will not function correctly. For information about configuring IPv6 for Windows, see [Guidance for configuring IPv6 in Windows for advanced users](https://support.microsoft.com/en-us/help/929852/guidance-for-configuring-ipv6-in-windows-for-advanced-users). +Do not disable IPv6. If you disable IPv6, WorkSpaces Applications will not function correctly. For information about configuring IPv6 for Windows, see [Guidance for configuring IPv6 in Windows for advanced users](https://support.microsoft.com/en-us/help/929852/guidance-for-configuring-ipv6-in-windows-for-advanced-users). @@ -28 +28 @@ Do not disable IPv6. If you disable IPv6, AppStream 2.0 will not function correc -AppStream 2.0 relies on the DNS servers within your VPC to return a non-existent domain (NXDOMAIN) response for local domain names that don’t exist. This enables the AppStream 2.0-managed network interface to communicate with the management servers. +WorkSpaces Applications relies on the DNS servers within your VPC to return a non-existent domain (NXDOMAIN) response for local domain names that don’t exist. This enables the WorkSpaces Applications-managed network interface to communicate with the management servers. @@ -30 +30 @@ AppStream 2.0 relies on the DNS servers within your VPC to return a non-existent -When you create a directory with Simple AD, AWS Directory Service creates two domain controllers that also function as DNS servers on your behalf. Because the domain controllers don't provide the NXDOMAIN response, they can't be used with AppStream 2.0. +When you create a directory with Simple AD, AWS Directory Service creates two domain controllers that also function as DNS servers on your behalf. Because the domain controllers don't provide the NXDOMAIN response, they can't be used with WorkSpaces Applications.