- Newest
- Most votes
- Most comments
Amazon WorkSpaces Applications (also known as AppStream 2.0) handles USB redirection differently between the Image Builder environment and the actual fleet deployment.
When you're using the Image Builder, USB redirection settings are available because the Image Builder is designed for administrators to test and configure applications, including qualifying USB devices that will be used during streaming sessions. This allows you to verify that your USB devices work properly with your applications.
However, when you create an image and attach it to a fleet, the USB redirection settings may not appear in the client for several possible reasons:
-
The USB devices may not have been properly qualified during the image building process. USB devices must be qualified before users can use them during WorkSpaces Applications streaming sessions.
-
There might be configuration differences between your Image Builder and fleet instances. The fleet might have different policies or settings applied.
-
The client application version might be handling USB redirection differently in the production environment compared to the Image Builder environment.
To resolve this issue, verify that:
- All necessary USB devices were properly qualified in the Image Builder
- The fleet has the appropriate permissions and configurations to support USB redirection
- The client application is the correct version and properly installed with USB redirection drivers
For USB redirection to work in production, both qualification of the device and proper sharing of the device with WorkSpaces Applications are required.
Sources
USB Devices - Amazon WorkSpaces Applications
Further context:
- When creating a single session fleet, the "USB Devices" option does show up and device redirection works fine. I was under the impression USB redirection works in either single or multi-session fleets. If it only works on single session then this makes this product close to useless.
Relevant content
- asked 2 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago

AI answer did not help