AWS deadline-cloud documentation change
Summary
Minor wording change clarifying caching behavior on service-managed fleets.
Security assessment
Clarifies technical behavior without security implications. No evidence of security vulnerability being addressed.
Diff
diff --git a/deadline-cloud/latest/developerguide/build-jobs-scheduling.md b/deadline-cloud/latest/developerguide/build-jobs-scheduling.md index b0b3cba03..ba30941b1 100644 --- a//deadline-cloud/latest/developerguide/build-jobs-scheduling.md +++ b//deadline-cloud/latest/developerguide/build-jobs-scheduling.md @@ -97 +97 @@ 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. +On service-managed fleet workers, session directories are deleted after the session ends, but other directories are retained between sessions. This behavior 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.