Why does the WorkspacesClientDiagnosticUploader.exe open so many processes and use so much bandwidth to s3-1-w.amazonmaws.com

Hi, Why does the WorkspacesClientDiagnosticUploader.exe open so many processes and use so much bandwidth to s3-1-w.amazonmaws.com.

Have some users where we had to uncheck the option of Automatic Diagnostic Logging in the Workspaces Settings section or just reboot their PCs to kill the amount of processes that was created by the log uploader

On some PCs I saw more than 20 Processes running and the amount of connections being made to s3-1-w.amazonmaws.com.

Want to know what triggers it happening ? Why does it start so many different processes? Why does it have to use so much bandwidth to upload the logs?

![![