There are a few situations where it would be useful to write data to the file system, but my experience is that the data will not persist for more than a few days. I've tried writing data within the integration folder, above the integration, to /var/lib/*, and so on...all without any luck. The data soon disappears.
A specific example is the use of AWS Secret Manager. A credential file cannot be used because it will not persist. For now, using a parameter will suffice, but there are other uses for writing local data to support custom jobs/actions that need to track information between runs.
Any ideas are appreciated. Thank you!
Solved! Go to Solution.
Hi @GonFreecss , you may use Remote Agent (an on-prem component of Chronicle SOAR) to persistently store data (/opt/SiemplifyAgent/).
Also, with docker Remote Agent you are able to store data persistently since it is using Docker Volume mechanism.
https://cloud.google.com/chronicle/docs/soar/working-with-remote-agents/remote-agents-for-cloud-over...
https://docs.docker.com/storage/volumes/
Hi @GonFreecss , you may use Remote Agent (an on-prem component of Chronicle SOAR) to persistently store data (/opt/SiemplifyAgent/).
Also, with docker Remote Agent you are able to store data persistently since it is using Docker Volume mechanism.
https://cloud.google.com/chronicle/docs/soar/working-with-remote-agents/remote-agents-for-cloud-over...
https://docs.docker.com/storage/volumes/
I will check this out. Many thanks.