Running Configurations on Remote Targets Accumulates Disk Space Consumption

Our team leans heavily on the use of Remote Targets when running Test and Application configs. Every team member is given an EC2 machine with 60 gigs of disk space to setup the remote target. Recently some members ran into an issue where preparing the remote target failed because the EC2 instance had run out of disk space. Turns out they had hundreds of folders created over the last several months in the target path that looked like, “j6WLpsaOs1”. All together the temp folders were consuming 40 gigs of space. Deleting them unblocked the users.

I've tried to learn more about how IntelliJ prepares and runs targets but I can't find much. I see that each time a config is run a new temp folder is created in the target path. It contains a copy of the project along with information about the IntelliJ version used and other caches.

My questions are:

1. Is there a way to configure the use of these temp folders? Are we missing something that would clean them up periodically or are we potentially misusing the Remote Target feature?

2. Are there more detailed technical documentation on this topic? We maintain our own plugin for IntelliJ and are considering adding the ability to clean up remote target paths automatically if no such configuration exists.