We are investigating the issue.

Hi @andrewme2,

I am also experiencing this issue. As a workaround, I am using this cron job in root's crontab:

0 0 * * * find /var/lib/amazon/ssm/i-*/document/orchestration -mindepth 2 -maxdepth 2 -type d -mtime +3 -print0 | xargs -0 rm -rf

This will be executed every day at midnight and delete all orchestration documents older than 3 days.

Thanks @vjt ! That's a good workaround until this bug is fixed.

has this been resolved in a release?

@wael-amz Is there a workaround or updates on this issue?

The issue has been addressed in the latest release 2.2.800.0

Hi @wael-amz , I'm trying to verify that this bug is fixed. I upgraded to 2.2.800.0. How long do I need to wait before the SSM agent will clean up old files? I do not know how often the agent runs its clean-up routine (every hour, once-per-day, etc?). After running for ~2 hours, I still have directories in the orchestration directory from May:

root@ip-X-X-X-X:~# ls -ltr /var/lib/amazon/ssm//document/orchestration | head
total 774160
drwx------ 3 root root 4096 May 1 17:59 9b1a8ca8-REDACTED
drw------- 3 root root 4096 May 1 17:59 8c7ca5d1-REDACTED
drw------- 3 root root 4096 May 1 18:02 a7a2756a-REDACTED
drwx------ 3 root root 4096 May 1 18:03 6dd8855e-REDACTED
drwx------ 3 root root 4096 May 1 18:07 28445cc3-REDACTED
drwx------ 3 root root 4096 May 1 18:07 dca845eb-REDACTED
drw------- 3 root root 4096 May 1 18:10 e2bd2589-REDACTED
drwx------ 3 root root 4096 May 1 18:10 a4e4b5e3-REDACTED
drw------- 3 root root 4096 May 1 18:11 cd02fb83-REDACTED

The cleanup logic will be triggered every time you run a command and it is not time based.