AWS batch documentation change
Summary
Added 'Scale down delay' configuration option and updated step numbering in compute environment setup instructions
Security assessment
Changes are procedural updates related to resource management and user interface flow. The scale down delay affects cost optimization rather than security controls.
Diff
diff --git a/batch/latest/userguide/create-compute-environment-managed-ec2.md b/batch/latest/userguide/create-compute-environment-managed-ec2.md index 14c75877d..7f1ec2376 100644 --- a//batch/latest/userguide/create-compute-environment-managed-ec2.md +++ b//batch/latest/userguide/create-compute-environment-managed-ec2.md @@ -57 +57,3 @@ To tag your Spot Instances on creation, your Amazon EC2 Spot Fleet IAM role must - 7. For **Allowed instance types** , choose the Amazon EC2 instance types that can be launched. You can specify instance families to launch any instance type within those families (for example, `c5`, `c5n`, or `p3`). Or, you can specify specific sizes within a family (such as `c5.8xlarge`). Metal instance types aren't in the instance families. For example, `c5` doesn't include `c5.metal`. + 7. (Optional) For **Scale down delay (minutes)** , choose the minimum time (in minutes) that AWS Batch keeps instances running in the compute environment after their jobs complete. + + 8. For **Allowed instance types** , choose the Amazon EC2 instance types that can be launched. You can specify instance families to launch any instance type within those families (for example, `c5`, `c5n`, or `p3`). Or, you can specify specific sizes within a family (such as `c5.8xlarge`). Metal instance types aren't in the instance families. For example, `c5` doesn't include `c5.metal`. @@ -87 +89 @@ AWS Batch will scale GPUs based on the required amount in your job queues. To us - 8. For **Allocation strategy** , choose the allocation strategy to use when selecting instance types from the list of allowed instance types. **BEST_FIT_PROGRESSIVE** is usually the better choice for EC2 On-Demand compute environments, **SPOT_CAPACITY_OPTIMIZED** , and **SPOT_PRICE_CAPACITY_OPTIMIZED** for EC2 Spot compute environments. For more information, see [Instance type allocation strategies for AWS Batch](./allocation-strategies.html). + 9. For **Allocation strategy** , choose the allocation strategy to use when selecting instance types from the list of allowed instance types. **BEST_FIT_PROGRESSIVE** is usually the better choice for EC2 On-Demand compute environments, **SPOT_CAPACITY_OPTIMIZED** , and **SPOT_PRICE_CAPACITY_OPTIMIZED** for EC2 Spot compute environments. For more information, see [Instance type allocation strategies for AWS Batch](./allocation-strategies.html). @@ -89 +91 @@ AWS Batch will scale GPUs based on the required amount in your job queues. To us - 9. Expand **Additional configuration**. + 10. Expand **Additional configuration**. @@ -129 +131 @@ The AMI that you choose for a compute environment must match the architecture of - 10. (Optional) Expand **Launch templates** + 11. (Optional) Expand **Launch templates** @@ -167 +169 @@ If the instance type or family that you want to select doesn't appear in this li - 11. Choose **Next**. + 12. Choose **Next**.