Workspaces Applications Printer time out

Based on the available information, there are a few timeout-related configurations that could potentially affect printer redirection in WorkSpaces Applications. Session timeouts can be configured in the fleet console, including idle disconnect timeout (which defaults to 15 minutes but can be adjusted) and session duration (which defaults to 16 hours). If your idle disconnect timeout is set too low, it could potentially impact printer redirection functionality.

However, the specific issue you're describing—where redirected printers stop printing after approximately 20 minutes—isn't directly addressed in the current documentation. Local printer redirection is a supported feature for WorkSpaces Applications, and there have been updates to improve this functionality, including enhancements to the agent and client for local printer redirection.

I'd recommend checking your fleet's timeout configurations in the console to ensure they're set appropriately for your use case. If the issue persists after verifying your timeout settings, you may want to reach out through the AWS Support Center at https://console.aws.amazon.com/support/ to report this specific behavior, as it could be related to a configuration issue or potentially a bug that needs investigation with your specific setup and the latest agent and client versions you're using.
Sources
EUCSUS03-BP01 Adapt your WorkSpaces Applications fleet timeout - End User Computing (EUC) Lens
Document History for Amazon WorkSpaces Applications - Amazon WorkSpaces Applications

1. Distinguish between "20 minutes" of active session time and "20 minutes" of idle time

Check whether the disconnection occurs even when you are actively using the system for the full 20 minutes, or only after a period of inactivity. If it is the latter, the issue is likely related to an idle timeout; if it is the former, the cause lies elsewhere.

2. Check if the issue occurs with network printers

AWS recommends configuring printers directly within the WorkSpace environment rather than redirecting them from the client machine when using network printers. If you are currently using network printers, simply switching to this recommended configuration might resolve the issue.

3. Check if "Advanced Printer Redirection" is in use

AWS has introduced an "Advanced Printer Redirection" feature for WorkSpaces. Since its implementation differs from the traditional generic driver method, the troubleshooting approach depends on which method is being used. If you are not currently using this feature, it is worth trying.

4. Reinstall the agent

The AWS troubleshooting guide outlines the following procedure for printing issues: connect to the WorkSpace via RDP, uninstall "WSP" (if using the DCV protocol), restart the instance from the WorkSpaces console, wait 15 minutes, and then perform a test print. Reinstalling the agent has been known to resolve the issue in some cases.

Hello.

I haven't found any documented timeout of around 20 minutes for WorkSpaces Applications printer redirection.
One thing worth checking is the exact WorkSpaces Applications client version you are using.
The latest Windows client, version 1.3.1954 released on August 18, 2026, includes a change related to printer handling ("Added support for honoring printer preferences when printing from a session").
https://docs.aws.amazon.com/appstream2/latest/developerguide/client-release-versions.html

If no issues occur with a client older than this version, the problem might lie with a feature added in this version.