AWS appstream2 documentation change
Summary
Updated service name references from 'AppStream 2.0' to 'WorkSpaces Applications' throughout the document
Security assessment
The changes are purely branding updates renaming the service from AppStream 2.0 to WorkSpaces Applications. No security vulnerabilities, mitigations, or new security features are introduced. The security-related content (security groups, VPC endpoints, IAM roles) remains functionally identical with only service name changes.
Diff
diff --git a/appstream2/latest/developerguide/control-network-traffic.md b/appstream2/latest/developerguide/control-network-traffic.md index b2b03955d..dc9b13008 100644 --- a//appstream2/latest/developerguide/control-network-traffic.md +++ b//appstream2/latest/developerguide/control-network-traffic.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) @@ -7 +7 @@ -To help control network traffic to your AppStream 2.0 streaming instances, consider these options: +To help control network traffic to your WorkSpaces Applications streaming instances, consider these options: @@ -13 +13 @@ To help control network traffic to your AppStream 2.0 streaming instances, consi - * Security groups that belong to your VPC let you control the network traffic between AppStream 2.0 streaming instances and VPC resources such as license servers, file servers, and database servers. Security groups also isolate traffic between your streaming instances and AppStream 2.0 management services. + * Security groups that belong to your VPC let you control the network traffic between WorkSpaces Applications streaming instances and VPC resources such as license servers, file servers, and database servers. Security groups also isolate traffic between your streaming instances and WorkSpaces Applications management services. @@ -15 +15 @@ To help control network traffic to your AppStream 2.0 streaming instances, consi -Use security groups to restrict access to your streaming instances. For example, you can allow traffic only from the address ranges for your corporate network. For more information, see [Security Groups in Amazon AppStream 2.0](./managing-network-security-groups.html). +Use security groups to restrict access to your streaming instances. For example, you can allow traffic only from the address ranges for your corporate network. For more information, see [Security Groups in Amazon WorkSpaces Applications](./managing-network-security-groups.html). @@ -17 +17 @@ Use security groups to restrict access to your streaming instances. For example, - * You can stream from AppStream 2.0 streaming instances in your VPC without going through the public internet. To do so, use an interface VPC endpoint (interface endpoint). For more information, see [Tutorial: Creating and Streaming from Interface VPC Endpoints](./creating-streaming-from-interface-vpc-endpoints.html). + * You can stream from WorkSpaces Applications streaming instances in your VPC without going through the public internet. To do so, use an interface VPC endpoint (interface endpoint). For more information, see [Tutorial: Creating and Streaming from Interface VPC Endpoints](./creating-streaming-from-interface-vpc-endpoints.html). @@ -19 +19 @@ Use security groups to restrict access to your streaming instances. For example, -You can also call AppStream 2.0 API operations from your VPC without sending traffic over the public internet by using an interface endpoint. For more information, see [Access AppStream 2.0 API Operations and CLI Commands Through an Interface VPC Endpoint](./access-api-cli-through-interface-vpc-endpoint.html). +You can also call WorkSpaces Applications API operations from your VPC without sending traffic over the public internet by using an interface endpoint. For more information, see [Access WorkSpaces Applications API Operations and CLI Commands Through an Interface VPC Endpoint](./access-api-cli-through-interface-vpc-endpoint.html). @@ -21 +21 @@ You can also call AppStream 2.0 API operations from your VPC without sending tra - * Use IAM roles and policies to manage administrator access to AppStream 2.0, Application Auto Scaling, and Amazon S3 buckets. For more information, see the following topics: + * Use IAM roles and policies to manage administrator access to WorkSpaces Applications, Application Auto Scaling, and Amazon S3 buckets. For more information, see the following topics: @@ -23 +23 @@ You can also call AppStream 2.0 API operations from your VPC without sending tra - * [Using AWS Managed Policies and Linked Roles to Manage Administrator Access to AppStream 2.0 Resources](./controlling-administrator-access-with-policies-roles.html) + * [Using AWS Managed Policies and Linked Roles to Manage Administrator Access to WorkSpaces Applications Resources](./controlling-administrator-access-with-policies-roles.html) @@ -29 +29 @@ You can also call AppStream 2.0 API operations from your VPC without sending tra - * You can use SAML 2.0 to federate authentication to AppStream 2.0. For more information, see [Amazon AppStream 2.0 Service Quotas](./limits.html). + * You can use SAML 2.0 to federate authentication to WorkSpaces Applications. For more information, see [Amazon WorkSpaces Applications Service Quotas](./limits.html). @@ -33 +33 @@ You can also call AppStream 2.0 API operations from your VPC without sending tra -For smaller AppStream 2.0 deployments, you can use AppStream 2.0 user pools. By default, user pools support a maximum of 50 users. For more information about AppStream 2.0 quotas (also referred to as limits), see [Amazon AppStream 2.0 Service Quotas](./limits.html). For deployments that must support 100 or more AppStream 2.0 users, we recommend using SAML 2.0. +For smaller WorkSpaces Applications deployments, you can use WorkSpaces Applications user pools. By default, user pools support a maximum of 50 users. For more information about WorkSpaces Applications quotas (also referred to as limits), see [Amazon WorkSpaces Applications Service Quotas](./limits.html). For deployments that must support 100 or more WorkSpaces Applications users, we recommend using SAML 2.0.