ssm worker processes accumulate over time on Windows due to long path failure

[adamkbmc]

We noticed that if we use SSM non interactive commands against Windows instances, then we see a a lot of worker processes hanging around. They don't die and eventually SSM commands fail and the machine needs a reboot. We've traced this to problems with the worker log file which has a very long path which exceeds the Windows default limit of 260 characters. For example:

2025-02-11 10:58:46.0176 WARN [ssm-session-worker] [4e77db8f999284a60eeaff5c9aecf64a142a4c1f44a74e3acb744f8f40e6e73c-znevu7gh3qqrdurq264gk2ft38] [DataBackend] [pluginName=Standard_Stream] Error opening file: open C:\ProgramData\Amazon\SSM\InstanceData\i-xxxxxxxxxxxxxxxxx\session\orchestration\4e77db8f999284a60eeaff5c9aecf64a142a4c1f44a74e3acb744f8f40e6e73c-znevu7gh3qqrdurq264gk2ft38\Standard_Stream\4e77db8f999284a60eeaff5c9aecf64a142a4c1f44a74e3acb744f8f40e6e73c-znevu7gh3qqrdurq264gk2ft38.log: The system cannot find the file specified.
The issue was resolved by setting the registry value HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem LongPathsEnabled (Type: REG_DWORD) to 1 and restarting the system.

Since this registry key isn't set by default on Windows, SSM should really try and avoid creating long paths

[Aperocky]

Thank you for this report, we are able to reproduce and root cause and is fixing this bug.

[73dsuk25]

I realise this is a new issue but please can you update with a target fix date as this is affecting one of my services.

[drmihalj]

Hello, the fix will be available with our next release. Thank you.

[73dsuk25]

Do you have a release date for the next release yet please?