AWS batch documentation change
Summary
Updated navigation steps, renumbered configuration options, added details about allocation strategies, restructured launch template configuration, and updated Amazon Linux AMI references to Amazon Linux 2023 with compatibility notes.
Security assessment
Changes primarily involve UI navigation updates, documentation restructuring, and AMI version updates. While EC2 key pair configuration (security credentials) was moved in the structure, this is a documentation reorganization rather than a new security feature or vulnerability fix. The Amazon Linux 2023 update addresses modern platform support but doesn't explicitly mention security patches or vulnerabilities.
Diff
diff --git a/batch/latest/userguide/create-compute-environment-managed-ec2.md b/batch/latest/userguide/create-compute-environment-managed-ec2.md index c88b71bb8..1bd9aee44 100644 --- a//batch/latest/userguide/create-compute-environment-managed-ec2.md +++ b//batch/latest/userguide/create-compute-environment-managed-ec2.md @@ -13 +13 @@ Complete the following steps to create a managed compute environment using Amazo - 3. In the navigation pane, choose **Compute environments**. + 3. In the navigation pane, choose **Environments**. @@ -15 +15 @@ Complete the following steps to create a managed compute environment using Amazo - 4. Choose **Create**. + 4. Choose **Create environment** and then **Compute environment**. @@ -31 +31 @@ Complete the following steps to create a managed compute environment using Amazo - 7. (Optional) For **EC2 tags** , choose **Add tag** to add a tag to resources that are launched in the compute environment. Then, enter a **Key** name and optional **Value**. Choose **Add tag**. + 1. (Optional) For **EC2 tags** , choose **Add tag** to add a tag to resources that are launched in the compute environment. Then, enter a **Key** name and optional **Value**. Choose **Add tag**. @@ -33 +33 @@ Complete the following steps to create a managed compute environment using Amazo - 8. (Optional) For **Tags** , choose **Add tag**. Then, enter a **Key** name and optional **Value**. Choose **Add tag**. + 2. (Optional) For **Tags** , choose **Add tag**. Then, enter a **Key** name and optional **Value**. Choose **Add tag**. @@ -37 +37 @@ For more information, see [Tag your AWS Batch resources](./using-tags.html). - 9. Choose **Next page**. + 7. Choose **Next**. @@ -87 +87 @@ AWS Batch will scale GPUs based on the required amount in your job queues. To us - 8. Expand **Additional configuration**. + 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). @@ -89 +89 @@ AWS Batch will scale GPUs based on the required amount in your job queues. To us - 9. (Optional) For **Placement group** , enter a placement group name to group resources in the compute environment. + 9. Expand **Additional configuration**. @@ -91 +91 @@ AWS Batch will scale GPUs based on the required amount in your job queues. To us - 10. (Optional) For **EC2 key pair** , choose a public and private key pair as security credentials when you connect to the instance. For more information about Amazon EC2 key pairs, see [Amazon EC2 key pairs and Linux instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html). + 1. (Optional) For **Placement group** , enter a placement group name to group resources in the compute environment. @@ -93 +93 @@ AWS Batch will scale GPUs based on the required amount in your job queues. To us - 11. 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). + 2. (Optional) For **EC2 key pair** , choose a public and private key pair as security credentials when you connect to the instance. For more information about Amazon EC2 key pairs, see [Amazon EC2 key pairs and Linux instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html). @@ -95 +95 @@ AWS Batch will scale GPUs based on the required amount in your job queues. To us - 12. (Optional) For **EC2 configuration** choose **Image type** and **Image ID override** values to provide information for AWS Batch to select Amazon Machine Images (AMIs) for instances in the compute environment. If the **Image ID override** isn't specified for each **Image type** , AWS Batch selects a recent [Amazon ECS optimized AMI](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html). If no **Image type** is specified, the default is a **Amazon Linux 2** for non-GPU, non AWS Graviton instance. + 3. (Optional) For **EC2 configuration** choose **Image type** and **Image ID override** values to provide information for AWS Batch to select Amazon Machine Images (AMIs) for instances in the compute environment. If the **Image ID override** isn't specified for each **Image type** , AWS Batch selects a recent [Amazon ECS optimized AMI](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html). If no **Image type** is specified, the default is a **Amazon Linux 2** for non-GPU, non AWS Graviton instance. @@ -111 +111 @@ Default for all GPU instance families (for example `P4` and `G4`) and can be use -Amazon Linux +[Amazon Linux 2023](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html) @@ -114 +114,10 @@ Amazon Linux -Can be used for non-GPU, non AWS Graviton instance families. The standard support for Amazon Linux AMI has ended. For more information, see [Amazon Linux AMI](https://aws.amazon.com/amazon-linux-ami/). +AWS Batch supports Amazon Linux 2023. + +###### Note + +Amazon Linux 2023 does not support `A1` instances. + +[Amazon Linux 2023 (GPU)](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html#gpuami) + + +Default for all GPU instance families (for example `P4` and `G4`) and can be used for all non AWS Graviton-based instance types. @@ -120 +129,3 @@ The AMI that you choose for a compute environment must match the architecture of - 13. (Optional) For **Launch template** , select an existing Amazon EC2 launch template to configure your compute resources. The default version of the template is automatically populated. For more information, see [Use Amazon EC2 launch templates with AWS Batch](./launch-templates.html). + 10. (Optional) Expand **Launch templates** + + 1. For **Default launch template** , select an existing Amazon EC2 launch template to configure your compute resources. The default version of the template is automatically populated. For more information, see [Use Amazon EC2 launch templates with AWS Batch](./launch-templates.html). @@ -126 +137 @@ In a launch template, you can specify a custom AMI that you created. - 14. (Optional) For **Launch template version** , enter `$Default`, `$Latest`, or a specific version number to use. + 2. (Optional) For **Default version** , enter `$Default`, `$Latest`, or a specific version number to use. @@ -136 +147,3 @@ If the version parameter of the launch template is `$Default` or `$Latest`, the - 15. (Optional) For **Override launch templates** , select an existing Amazon EC2 launch template to use for specific instance types and families. + 3. (Optional) For **Override launch template** choose **Add override launch template** + + 1. (Optional) For **Launch template** , select an existing Amazon EC2 launch template to use for specific instance types and families. @@ -138 +151 @@ If the version parameter of the launch template is `$Default` or `$Latest`, the - 16. (Optional) For **Override launch template version** , enter a specific version number to use, `$Default`, or `$Latest`. + 2. (Optional) For **Default version** , enter a specific version number to use, `$Default`, or `$Latest`. @@ -144 +157 @@ If you use either the `$Default` or `$Latest` variable, AWS Batch will apply the - 17. (Optional) For **Target instance types** , select the instance type or family that you want to apply the override launch template. + 3. (Optional) For **Target instance types** , select the instance type or family that you want to apply the override launch template. @@ -154 +167 @@ If the instance type or family that you want to select doesn't appear in this li - 18. Choose **Next page**. + 11. Choose **Next**.