AWS batch documentation change
Summary
Updated command input to require JSON format and adjusted step numbering in EC2 multi-node job definition documentation
Security assessment
The changes involve simplifying command input to JSON format and renumbering steps, but there's no explicit mention of addressing a security vulnerability or adding new security content. While JSON input might improve structure, no security justification is provided in the diff.
Diff
diff --git a/batch/latest/userguide/multi-node-job-def-ec2.md index d9a233f2d..f082b278b 100644 --- a/batch/latest/userguide/multi-node-job-def-ec2.md +++ b/batch/latest/userguide/multi-node-job-def-ec2.md @@ -85,3 +85 @@ Docker image architecture must match the processor architecture of the compute r - 4. For **Command syntax** , choose **Bash** or **JSON**. - - 5. For **Command** , specify the command to pass to the container. For simple commands, you can enter the command as you do at a command prompt in the **Space delimited** tab. Then, verify that the JSON result is correct. The JSON result is passed to the Docker daemon. For more complicated commands (for example, with special characters), you can switch to the **JSON** tab and enter the string array equivalent there. + 4. For **Command** , enter the commands into the field as their **JSON** string array equivalent. @@ -95 +93 @@ You can use default values for parameter substitution and placeholders in your c - 6. For **vCPUs** , specify the number of vCPUs to reserve for the container. This parameter maps to `CpuShares` in the [Create a container](https://docs.docker.com/engine/api/v1.38/#operation/ContainerCreate) section of the [Docker Remote API](https://docs.docker.com/engine/api/v1.38/) and the `--cpu-shares` option to [**docker run**](https://docs.docker.com/engine/reference/commandline/run/). Each vCPU is equivalent to 1,024 CPU shares. You must specify at least one vCPU. + 5. For **vCPUs** , specify the number of vCPUs to reserve for the container. This parameter maps to `CpuShares` in the [Create a container](https://docs.docker.com/engine/api/v1.38/#operation/ContainerCreate) section of the [Docker Remote API](https://docs.docker.com/engine/api/v1.38/) and the `--cpu-shares` option to [**docker run**](https://docs.docker.com/engine/reference/commandline/run/). Each vCPU is equivalent to 1,024 CPU shares. You must specify at least one vCPU. @@ -97 +95 @@ You can use default values for parameter substitution and placeholders in your c - 7. For **Memory** , specify the hard limit (in MiB) of memory to present to the job's container. If your container attempts to exceed the memory specified here, the container is stopped. This parameter maps to `Memory` in the [Create a container](https://docs.docker.com/engine/api/v1.38/#operation/ContainerCreate) section of the [Docker Remote API](https://docs.docker.com/engine/api/v1.38/) and the `--memory` option to [**docker run**](https://docs.docker.com/engine/reference/commandline/run/). You must specify at least 4 MiB of memory for a job. + 6. For **Memory** , specify the hard limit (in MiB) of memory to present to the job's container. If your container attempts to exceed the memory specified here, the container is stopped. This parameter maps to `Memory` in the [Create a container](https://docs.docker.com/engine/api/v1.38/#operation/ContainerCreate) section of the [Docker Remote API](https://docs.docker.com/engine/api/v1.38/) and the `--memory` option to [**docker run**](https://docs.docker.com/engine/reference/commandline/run/). You must specify at least 4 MiB of memory for a job. @@ -103 +101 @@ To maximize your resource utilization, you can provide your jobs as much memory - 8. (Optional) For **Number of GPUs** , specify the number of GPUs your job uses. The job runs on a container with the specified number of GPUs that are pinned to that container. + 7. (Optional) For **Number of GPUs** , specify the number of GPUs your job uses. The job runs on a container with the specified number of GPUs that are pinned to that container. @@ -105 +103 @@ To maximize your resource utilization, you can provide your jobs as much memory - 9. (Optional) For **Job role** , you can specify an IAM role that provides the container in your job with permissions to use the AWS APIs. This feature uses Amazon ECS IAM roles for task functionality. For more information including configuration prerequisites, see [IAM Roles for Tasks](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html) in the _Amazon Elastic Container Service Developer Guide_. + 8. (Optional) For **Job role** , you can specify an IAM role that provides the container in your job with permissions to use the AWS APIs. This feature uses Amazon ECS IAM roles for task functionality. For more information including configuration prerequisites, see [IAM Roles for Tasks](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html) in the _Amazon Elastic Container Service Developer Guide_. @@ -115 +113 @@ Only roles that have the **Amazon Elastic Container Service Task Role** trust re - 10. (Optional) For **Execution role** , specify an IAM role that grants the Amazon ECS container agents permission to make AWS API calls on your behalf. This feature uses Amazon ECS IAM roles for task functionality. For more information, see [Amazon ECS task execution IAM roles](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_execution_IAM_role.html) in the _Amazon Elastic Container Service Developer Guide_. + 9. (Optional) For **Execution role** , specify an IAM role that grants the Amazon ECS container agents permission to make AWS API calls on your behalf. This feature uses Amazon ECS IAM roles for task functionality. For more information, see [Amazon ECS task execution IAM roles](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_execution_IAM_role.html) in the _Amazon Elastic Container Service Developer Guide_.