AWS deadline-cloud documentation change
Summary
Added documentation about session directory cleanup and persistent caching in job user's home directory on service-managed fleets.
Security assessment
Documents security-relevant behavior: automatic deletion of session directories reduces attack surface, while noting persistent storage locations helps implement secure caching. This adds security documentation but doesn't fix a specific vulnerability.
Diff
diff --git a/deadline-cloud/latest/developerguide/build-jobs-scheduling.md b/deadline-cloud/latest/developerguide/build-jobs-scheduling.md index f2d3fc646..b0b3cba03 100644 --- a//deadline-cloud/latest/developerguide/build-jobs-scheduling.md +++ b//deadline-cloud/latest/developerguide/build-jobs-scheduling.md @@ -96,0 +97,2 @@ As a worker completes section actions, additional session actions can be sent to +On service-managed fleet workers, session directories are deleted after the session ends, but other directories are retained between sessions. This allows you to implement caching strategies for data that can be reused across multiple sessions. To cache data between sessions, store it under the home directory of the user running the job. For example, conda packages are cached under the job user's home directory at `C:\Users\job-user\.conda-pkgs` on Windows workers and `/home/job-user/.conda-pkgs` on Linux workers. This data remains available until the worker shuts down. +