AWS appstream2 documentation change
Summary
Updated product name from 'Amazon AppStream 2.0' to 'Amazon WorkSpaces Applications' throughout the document. Content recommendations about short-lived URLs and concurrent sessions remain similar but with updated product references.
Security assessment
The changes appear to be product rebranding updates rather than addressing security vulnerabilities. The security recommendation about short-lived URLs (5-second validity) remains unchanged in content - this is existing security guidance rather than new documentation. No new security features or vulnerabilities are introduced.
Diff
diff --git a/appstream2/latest/developerguide/embed-streaming-sessions-recommendations-considerations.md b/appstream2/latest/developerguide/embed-streaming-sessions-recommendations-considerations.md index ade4e0c48..5f7d0fffa 100644 --- a//appstream2/latest/developerguide/embed-streaming-sessions-recommendations-considerations.md +++ b//appstream2/latest/developerguide/embed-streaming-sessions-recommendations-considerations.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 @@ -# Recommendations and Usage Considerations for Embedding Amazon AppStream 2.0 Streaming Sessions +# Recommendations and Usage Considerations for Embedding Amazon WorkSpaces Applications Streaming Sessions @@ -7 +7 @@ -Consider the following recommendations and usage notes for embedded AppStream 2.0 streaming sessions. +Consider the following recommendations and usage notes for embedded WorkSpaces Applications streaming sessions. @@ -9 +9 @@ Consider the following recommendations and usage notes for embedded AppStream 2. - * To maintain maximum control over the embedded AppStream 2.0 streaming experience for your users, we recommend that you configure short-lived streaming URLs that last approximately 5 seconds. Any user can inspect the contents of a webpage and view its source. This includes the document object model (DOM) and the src (source) URL of the iframe. If the URL is still valid when a user copies it, that user can paste the URL in a separate browser tab and stream the session with the standard AppStream 2.0 portal user interface, without the embed options. + * To maintain maximum control over the embedded WorkSpaces Applications streaming experience for your users, we recommend that you configure short-lived streaming URLs that last approximately 5 seconds. Any user can inspect the contents of a webpage and view its source. This includes the document object model (DOM) and the src (source) URL of the iframe. If the URL is still valid when a user copies it, that user can paste the URL in a separate browser tab and stream the session with the standard WorkSpaces Applications portal user interface, without the embed options. @@ -11 +11 @@ Consider the following recommendations and usage notes for embedded AppStream 2. - * Concurrent sessions are not supported when custom domains are used for embedded AppStream 2.0 streaming sessions. Concurrent sessions occur when users start two embedded AppStream 2.0 streaming sessions either on the same webpage or across two different browser tabs. You can't have a single user with concurrent sessions, but you can have multiple users. For example, a user logs into your app, your app generates a streaming URL to give to the customer (which counts as a unique user for billing), a customer loads the streaming URL, and the customer is assigned to an appstream instance within your specified pool. + * Concurrent sessions are not supported when custom domains are used for embedded WorkSpaces Applications streaming sessions. Concurrent sessions occur when users start two embedded WorkSpaces Applications streaming sessions either on the same webpage or across two different browser tabs. You can't have a single user with concurrent sessions, but you can have multiple users. For example, a user logs into your app, your app generates a streaming URL to give to the customer (which counts as a unique user for billing), a customer loads the streaming URL, and the customer is assigned to an appstream instance within your specified pool.