AWS deadline-cloud medium security documentation change
Summary
Restructured fleet configuration steps, updated instance market terminology, moved service role and tag settings to optional sections, and adjusted section headers.
Security assessment
The change emphasizes creating a new service role for each fleet to write to CloudWatch, which enforces the principle of least privilege. This is a security best practice to minimize over-permissive roles, directly addressing access control.
Diff
diff --git a/deadline-cloud/latest/userguide/define-fleet.md b/deadline-cloud/latest/userguide/define-fleet.md index 0e1ae0f36..faf53bec6 100644 --- a//deadline-cloud/latest/userguide/define-fleet.md +++ b//deadline-cloud/latest/userguide/define-fleet.md @@ -13 +13 @@ A fleet allocates workers to execute your rendering tasks. If you need a fleet f - 2. Select the way your compute resources should scale. The **Service-managed** option allows Deadline Cloud to auto scale your compute resources. The **Customer-managed** option leaves you in control of your own compute scaling. + 2. Review the fleet type and operating system for awareness. @@ -15 +15 @@ A fleet allocates workers to execute your rendering tasks. If you need a fleet f - 2. In the **Instance option** section, choose either **Spot** or **On-demand**. Amazon EC2 On-demand instances provide faster availability and Amazon EC2 Spot instances are better for cost saving efforts. + 2. In the **Instance market type** section, choose either **Spot Instance** or **On-demand Instance**. Amazon EC2 On-demand instances provide faster availability and Amazon EC2 Spot instances are better for cost saving efforts. @@ -21 +21,5 @@ We strongly recommend to always set the minimum number of instances to `0` to av - 4. Your fleet requires permission to write to CloudWatch on your behalf. We recommend you create a new service role for every fleet. + 4. Review the worker capabilities for awareness. + + 5. (optional) Choose **Additional fleet settings** + + 1. Your fleet requires permission to write to CloudWatch on your behalf. We recommend you create a new service role for every fleet. @@ -35 +39 @@ We strongly recommend to always set the minimum number of instances to `0` to av - 5. (Optional) Add tags for the fleet using key and value pairs. + 2. (Optional) Add tags for the fleet using key and value pairs. @@ -50 +54 @@ Define queue details -Configure worker capabilities +Review and create