AWS AmazonECS documentation change
Summary
Updated task creation steps with renumbered instructions, added cluster selection guidance, and clarified compute configuration options. Modified UI element labels (e.g., 'Run new task' to 'Run task') and reorganized content structure.
Security assessment
Changes focus on workflow clarification and UI updates without addressing security vulnerabilities. While IAM role override documentation exists, it maintains existing security guidance rather than introducing new security content or addressing a specific vulnerability.
Diff
diff --git a/AmazonECS/latest/developerguide/standalone-task-create.md b/AmazonECS/latest/developerguide/standalone-task-create.md index 7afb4780e..fb891dc96 100644 --- a/AmazonECS/latest/developerguide/standalone-task-create.md +++ b/AmazonECS/latest/developerguide/standalone-task-create.md @@ -17 +17 @@ To start a service from | Steps -a cluster detail page... | +The cluster detail page | @@ -19,2 +19,2 @@ a cluster detail page... | - 2. From the **Tasks** tab, choose **Run new task**. -a task definition revision page... | + 2. From the **Tasks** tab, choose **Run task**. +The task definition revision page | @@ -25 +25,7 @@ a task definition revision page... | - 3. (Optional) The **Compute configuration (advanced)** section is where you choose how your tasks will be distributed. You can use either a **Capacity provider strategy** or a **Launch type**. To use a capacity provider strategy, you must configure your capacity providers at the cluster level. If you haven't configured your cluster to use a capacity provider, use a launch type instead. + 3. For **Existing cluster** , choose the cluster. + +Choose **Create cluster** to run the task on a new cluster + + 4. Choose how your tasks are distributed across your cluster infrastructure. Under **Compute configuration** , choose your option.To use a capacity provider strategy, you must configure your capacity providers at the cluster level. + +If you haven't configured your cluster to use a capacity provider, use a launch type instead. @@ -43 +49 @@ Launch type | - 4. For **Application type** , choose **Task**. + 5. Under **Deployment configuration** , do the following: @@ -45 +51 @@ Launch type | - 5. For **Task definition** , choose the task definition family and revision. + 1. For **Task definition** , enter the task definition. @@ -51 +57,3 @@ The console validates the selection to ensure that the selected task definition - 6. For **Desired tasks** , enter the number of tasks to launch. + 2. For **Desired tasks** , enter the number of tasks to launch. + + 3. For **Task group** , enter the task group name. @@ -53 +61 @@ The console validates the selection to ensure that the selected task definition - 7. If your task definition uses the `awsvpc` network mode, expand **Networking**. Use the following steps to specify a custom configuration. + 6. If your task definition uses the `awsvpc` network mode, expand **Networking**. Use the following steps to specify a custom configuration. @@ -69 +77 @@ AWS Fargate tasks can be assigned a public IP address when run in a public subne - 8. If your task uses a data volume that's compatible with configuration at deployment, you can configure the volume by expanding **Volume**. + 7. If your task uses a data volume that's compatible with configuration at deployment, you can configure the volume by expanding **Volume**. @@ -88 +96 @@ Amazon EBS | - 9. (Optional) To use a task placement strategy other than the default, expand **Task Placement** , and then choose from the following options. + 8. (Optional) To use a task placement strategy other than the default, expand **Task Placement** , and then choose from the following options. @@ -114 +122 @@ You can enter a maximum of 10 constraints. - 10. (Optional) To override the task IAM role, or task execution role that is defined in your task definition, expand **Task overrides** , and then complete the following steps: + 9. (Optional) To override the task IAM role, or task execution role that is defined in your task definition, expand **Task overrides** , and then complete the following steps: @@ -122 +130 @@ Only roles with the `ecs-tasks.amazonaws.com` trust relationship are displayed. - 11. (Optional) To override the container commands and environment variables, expand **Container Overrides** , and then expand the container. + 10. (Optional) To override the container commands and environment variables, expand **Container Overrides** , and then expand the container. @@ -132 +140 @@ AWS surrounds the strings with double quotation marks (" ") and passes the strin - 12. (Optional) To help identify your task, expand the **Tags** section, and then configure your tags. + 11. (Optional) To help identify your task, expand the **Tags** section, and then configure your tags. @@ -146 +154 @@ Add or remove a tag. - 13. Choose **Create**. + 12. Choose **Create**.