AWS deadline-cloud documentation change
Summary
Added link to documentation about managing access to Windows job user secrets in AWS Secrets Manager.
Security assessment
The addition of a reference to 'Manage access to Windows job user secrets' provides guidance on securing credentials, which is a security best practice. However, there is no evidence this addresses a specific security vulnerability; it enhances existing security documentation.
Diff
diff --git a/deadline-cloud/latest/userguide/queues.md b/deadline-cloud/latest/userguide/queues.md index e446c52a2..e5ca7b62b 100644 --- a//deadline-cloud/latest/userguide/queues.md +++ b//deadline-cloud/latest/userguide/queues.md @@ -68 +68 @@ Or, to opt out of setting your own credentials and run jobs as the worker agent -If you are using a Windows fleet, you must create an AWS Secrets Manager secret that contains the password for the Run as user. If you don't have an existing secret with the password, choose **Create secret** to open the Secrets Manager console to create a secret. +If you are using a Windows fleet, you must create an AWS Secrets Manager secret that contains the password for the Run as user. If you don't have an existing secret with the password, choose **Create secret** to open the Secrets Manager console to create a secret. For more information, see [Manage access to Windows job user secrets](https://docs.aws.amazon.com/deadline-cloud/latest/developerguide/manage-access-windows-secrets.html) in the _Deadline Cloud Developer Guide_.