AWS appstream2 documentation change
Summary
Updated product name references from 'AppStream 2.0' to 'WorkSpaces Applications' throughout the document. No technical changes to authentication methods or security practices were made.
Security assessment
The changes are purely branding/product name updates (AppStream 2.0 → WorkSpaces Applications). The security-related content about using custom domains to handle third-party cookie blocking remains unchanged in substance. No vulnerabilities or new security features are introduced.
Diff
diff --git a/appstream2/latest/developerguide/create-streaming-url-user-authentication.md b/appstream2/latest/developerguide/create-streaming-url-user-authentication.md index e882ae188..e610397d1 100644 --- a//appstream2/latest/developerguide/create-streaming-url-user-authentication.md +++ b//appstream2/latest/developerguide/create-streaming-url-user-authentication.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 @@ Configuration Requirements for Using Custom Domains -You must create a streaming URL to authenticate users for embedded AppStream 2.0 streaming sessions. SAML 2.0 and user pools are currently not supported for embedded streaming sessions. To create a streaming URL, use one of the following methods: +You must create a streaming URL to authenticate users for embedded WorkSpaces Applications streaming sessions. SAML 2.0 and user pools are currently not supported for embedded streaming sessions. To create a streaming URL, use one of the following methods: @@ -11 +11 @@ You must create a streaming URL to authenticate users for embedded AppStream 2.0 - * AppStream 2.0 console + * WorkSpaces Applications console @@ -22 +22 @@ You must create a streaming URL to authenticate users for embedded AppStream 2.0 -Whether you use custom domains to apply your company branding or to ensure that embedded AppStream 2.0 streaming sessions work with browsers that block third-party cookies, the configuration requirements are the same. +Whether you use custom domains to apply your company branding or to ensure that embedded WorkSpaces Applications streaming sessions work with browsers that block third-party cookies, the configuration requirements are the same. @@ -24 +24 @@ Whether you use custom domains to apply your company branding or to ensure that -For web browsers that block third-party cookies, custom domains are required. AppStream 2.0 uses browser cookies to authenticate streaming sessions and lets users reconnect to an active session without being prompted to provide their sign-in credentials every time. By default, AppStream 2.0 streaming URLs include `appstream.com` as the domain. When you embed a streaming session within your website, `appstream.com` is treated as a third-party domain. As a result, streaming sessions may be blocked when modern browsers are used that block third-party cookies by default. +For web browsers that block third-party cookies, custom domains are required. WorkSpaces Applications uses browser cookies to authenticate streaming sessions and lets users reconnect to an active session without being prompted to provide their sign-in credentials every time. By default, WorkSpaces Applications streaming URLs include `appstream.com` as the domain. When you embed a streaming session within your website, `appstream.com` is treated as a third-party domain. As a result, streaming sessions may be blocked when modern browsers are used that block third-party cookies by default. @@ -26 +26 @@ For web browsers that block third-party cookies, custom domains are required. Ap -To avoid embedded AppStream 2.0 streaming sessions from being blocked in this scenario, follow these steps: +To avoid embedded WorkSpaces Applications streaming sessions from being blocked in this scenario, follow these steps: @@ -28 +28 @@ To avoid embedded AppStream 2.0 streaming sessions from being blocked in this sc - 1. Specify a custom domain to host your embedded AppStream 2.0 streaming sessions. + 1. Specify a custom domain to host your embedded WorkSpaces Applications streaming sessions. @@ -30 +30 @@ To avoid embedded AppStream 2.0 streaming sessions from being blocked in this sc -When you configure your custom domain, make sure that the domain is a subdomain of the webpage in which you plan to embed AppStream 2.0. For example, if you update your stack to specify `training.example.com` as the host domain, you can create a subdomain called `content.training.example.com` for your embedded streaming sessions. +When you configure your custom domain, make sure that the domain is a subdomain of the webpage in which you plan to embed WorkSpaces Applications. For example, if you update your stack to specify `training.example.com` as the host domain, you can create a subdomain called `content.training.example.com` for your embedded streaming sessions. @@ -32 +32 @@ When you configure your custom domain, make sure that the domain is a subdomain - 2. Create a streaming URL for embedded AppStream 2.0 streaming sessions that uses the same custom subdomain. To create the streaming URL, use the [CreateStreamingURL](https://docs.aws.amazon.com/appstream2/latest/APIReference/API_CreateStreamingURL.html) API action or the [create-streaming-url](https://docs.aws.amazon.com/cli/latest/reference/appstream/create-streaming-url.html) AWS CLI command. You cannot use the AppStream 2.0 console to create a streaming URL in this scenario. + 2. Create a streaming URL for embedded WorkSpaces Applications streaming sessions that uses the same custom subdomain. To create the streaming URL, use the [CreateStreamingURL](https://docs.aws.amazon.com/appstream2/latest/APIReference/API_CreateStreamingURL.html) API action or the [create-streaming-url](https://docs.aws.amazon.com/cli/latest/reference/appstream/create-streaming-url.html) AWS CLI command. You cannot use the WorkSpaces Applications console to create a streaming URL in this scenario. @@ -34 +34 @@ When you configure your custom domain, make sure that the domain is a subdomain -To create a streaming URL for embedded AppStream 2.0 streaming sessions, in the URL, replace `appstream2.``region``.aws.amazon.com` with your own domain. +To create a streaming URL for embedded WorkSpaces Applications streaming sessions, in the URL, replace `appstream2.``region``.aws.amazon.com` with your own domain. @@ -36 +36 @@ To create a streaming URL for embedded AppStream 2.0 streaming sessions, in the -By default, AppStream 2.0 streaming URLs are formatted as follows: +By default, WorkSpaces Applications streaming URLs are formatted as follows: @@ -46 +46 @@ If your subdomain is `content.training.example.com`, your new streaming URL foll -When you create a custom domain, you can use the domain for embedded AppStream 2.0 streaming sessions only in the AWS Region for which it was configured. If you plan to support custom domains in multiple Regions, create a custom domain for each applicable Region. Also, embedded streaming sessions are only supported over HTTPS [TCP port 443]. +When you create a custom domain, you can use the domain for embedded WorkSpaces Applications streaming sessions only in the AWS Region for which it was configured. If you plan to support custom domains in multiple Regions, create a custom domain for each applicable Region. Also, embedded streaming sessions are only supported over HTTPS [TCP port 443]. @@ -53 +53 @@ When you create a custom domain, you can use the domain for embedded AppStream 2 -Setting a custom domain and creating a streaming URL that specifies the same domain lets the cookies be saved as first-party cookies. For information about how to configure custom domains by using Amazon CloudFront, see [Using Custom Domains with AppStream 2.0](https://aws.amazon.com/blogs/desktop-and-application-streaming/using-custom-domains-with-amazon-appstream-2-0/). +Setting a custom domain and creating a streaming URL that specifies the same domain lets the cookies be saved as first-party cookies. For information about how to configure custom domains by using Amazon CloudFront, see [Using Custom Domains with WorkSpaces Applications](https://aws.amazon.com/blogs/desktop-and-application-streaming/using-custom-domains-with-amazon-appstream-2-0/). @@ -58 +58 @@ Setting a custom domain and creating a streaming URL that specifies the same dom -After you set up a custom domain for your embedded AppStream 2.0 streaming sessions, if your streaming URLs don't redirect to your custom domain, or if your custom domain doesn't display correctly for your users, see the following troubleshooting topics: +After you set up a custom domain for your embedded WorkSpaces Applications streaming sessions, if your streaming URLs don't redirect to your custom domain, or if your custom domain doesn't display correctly for your users, see the following troubleshooting topics: @@ -60 +60 @@ After you set up a custom domain for your embedded AppStream 2.0 streaming sessi - * [I set up a custom domain for my embedded AppStream 2.0 streaming sessions, but my AppStream 2.0 streaming URLs aren't redirecting to my custom domain.](./troubleshooting-general.html#embedded-streaming-sessions-streaming-urls-not-redirected-to-custom-domain) + * [I set up a custom domain for my embedded WorkSpaces Applications streaming sessions, but my WorkSpaces Applications streaming URLs aren't redirecting to my custom domain.](./troubleshooting-general.html#embedded-streaming-sessions-streaming-urls-not-redirected-to-custom-domain)