AWS appstream2 documentation change
Summary
Renamed service references from 'AppStream 2.0' to 'WorkSpaces Applications', updated console/client terminology, and adjusted tutorial links. No functional changes to file association configuration process.
Security assessment
Changes are limited to branding updates and terminology alignment. Security-related content about smart card sign-in remains functionally identical, only referencing the renamed client. No new security features or vulnerability mitigations introduced.
Diff
diff --git a/appstream2/latest/developerguide/customize-fleets-set-default-file-associations.md b/appstream2/latest/developerguide/customize-fleets-set-default-file-associations.md index 90ec696eb..da62e0d7a 100644 --- a//appstream2/latest/developerguide/customize-fleets-set-default-file-associations.md +++ b//appstream2/latest/developerguide/customize-fleets-set-default-file-associations.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 @@ -# Set Default File Associations for Your Users in Amazon AppStream 2.0 +# Set Default File Associations for Your Users in Amazon WorkSpaces Applications @@ -7 +7 @@ -The associations for application file extensions are set on a per-user basis and so are not automatically applied to all users who launch AppStream 2.0 streaming sessions. For example, if you set Adobe Reader as the default application for .pdf files on your image builder, this change is not applied to your users. +The associations for application file extensions are set on a per-user basis and so are not automatically applied to all users who launch WorkSpaces Applications streaming sessions. For example, if you set Adobe Reader as the default application for .pdf files on your image builder, this change is not applied to your users. @@ -21 +21 @@ The following steps must be performed on an image builder that is joined to an A - * [Use the AppStream 2.0 console](./managing-image-builders-connect-console.html) (for web connections only) + * [Use the WorkSpaces Applications console](./managing-image-builders-connect-console.html) (for web connections only) @@ -23 +23 @@ The following steps must be performed on an image builder that is joined to an A - * [Create a streaming URL](./managing-image-builders-connect-streaming-URL.html) (for web or AppStream 2.0 client connections) + * [Create a streaming URL](./managing-image-builders-connect-streaming-URL.html) (for web or WorkSpaces Applications client connections) @@ -27 +27 @@ The following steps must be performed on an image builder that is joined to an A -If your organization requires smart card sign in, you must create a streaming URL and use the AppStream 2.0 client for the connection. For information about smart card sign in, see [Smart Cards](./feature-support-USB-devices-qualified.html#feature-support-USB-devices-qualified-smart-cards). +If your organization requires smart card sign in, you must create a streaming URL and use the WorkSpaces Applications client for the connection. For information about smart card sign in, see [Smart Cards](./feature-support-USB-devices-qualified.html#feature-support-USB-devices-qualified-smart-cards). @@ -75 +75 @@ Under **User Configuration** , expand **Policies** , **Administrative Templates* - 11. Follow the necessary steps in Image Assistant to finish creating your image. For more information, see [Tutorial: Create a Custom AppStream 2.0 Image by Using the AppStream 2.0 Console](./tutorial-image-builder.html). + 11. Follow the necessary steps in Image Assistant to finish creating your image. For more information, see [Tutorial: Create a Custom WorkSpaces Applications Image by Using the WorkSpaces Applications Console](./tutorial-image-builder.html).