AWS AmazonECS documentation change
Summary
Restructured step numbering and added details under 'Service details' section. Fixed a typo in VPC Lattice step ('xxpand' to 'expand'). Reordered and renumbered multiple steps in the service creation process.
Security assessment
The changes primarily involve documentation structure, step renumbering, and typo fixes. No explicit references to security vulnerabilities, access controls, encryption, or authentication mechanisms were added or modified. The health check grace period mention remains unchanged in content and does not indicate a security fix.
Diff
diff --git a/AmazonECS/latest/developerguide/create-service-console-v2.md b/AmazonECS/latest/developerguide/create-service-console-v2.md index df87b31a8..e70aa35e9 100644 --- a//AmazonECS/latest/developerguide/create-service-console-v2.md +++ b//AmazonECS/latest/developerguide/create-service-console-v2.md @@ -147 +147,7 @@ The **Create service** page appears. - 3. For **Existing cluster** , choose the cluster. + 3. Under Service details, do the following: + + 1. For **Task definition** , enter the task definition to use. Then, for **Revision** , choose the revision to use. + + 2. For **Service name** , enter a name for your service. + + 4. For **Existing cluster** , choose the cluster. @@ -151 +157 @@ 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. + 5. Choose how your tasks are distributed across your cluster infrastructure. Under **Compute configuration** , choose your option. @@ -169,5 +175 @@ Launch type | - 5. Under **Deployment configuration** , do the following: - - 1. For **Task definition** , enter the task definition to use. Then, for **Revision** , choose the revision to use. - - 2. For **Service name** , enter a name for your service. + 6. Under **Deployment configuration** , do the following: @@ -175 +177 @@ Launch type | - 3. For **Service type** , choose the service scheduling strategy. + 1. For **Service type** , choose the service scheduling strategy. @@ -181 +183 @@ Launch type | - 4. If you chose **Replica** , for **Desired tasks** , enter the number of tasks to launch and maintain in the service. + 2. If you chose **Replica** , for **Desired tasks** , enter the number of tasks to launch and maintain in the service. @@ -183 +185 @@ Launch type | - 5. If you chose **Replica** , to have Amazon ECS monitor the distribution of tasks across Availability Zones, and redistribute them when there is an imbalance, under **Availability Zone service rebalancing** , select **Availability Zone service rebalancing**. + 3. If you chose **Replica** , to have Amazon ECS monitor the distribution of tasks across Availability Zones, and redistribute them when there is an imbalance, under **Availability Zone service rebalancing** , select **Availability Zone service rebalancing**. @@ -185 +187 @@ Launch type | - 6. For **Health check grace period** , enter the amount of time (in seconds) that the enter the amount of time (in seconds) that the service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started. If you do not specify a health check grace period value, the default value of 0 is used. + 4. For **Health check grace period** , enter the amount of time (in seconds) that the enter the amount of time (in seconds) that the service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started. If you do not specify a health check grace period value, the default value of 0 is used. @@ -187 +189 @@ Launch type | - 7. Determine the deployment type for your service. Expand **Deployment options** , and then specify the following parameters. + 5. Determine the deployment type for your service. Expand **Deployment options** , and then specify the following parameters. @@ -198 +200 @@ Blue/green deployment | - 8. To configure how Amazon ECS detects and handles deployment failures, expand **Deployment failure detection** , and then choose your options. + 6. To configure how Amazon ECS detects and handles deployment failures, expand **Deployment failure detection** , and then choose your options. @@ -208 +210 @@ To have the software automatically roll back the deployment to the last complete - 6. If your task definition uses the `awsvpc` network mode, you can specify a custom network configuration expand **Networking** , and then do the following to. + 7. If your task definition uses the `awsvpc` network mode, you can specify a custom network configuration expand **Networking** , and then do the following to. @@ -224 +226 @@ AWS Fargate tasks can be assigned a public IP address when run in a public subne - 7. (Optional) To interconnect you service using Service Connect, expand **Service Connect** , and then specify the following: + 8. (Optional) To interconnect you service using Service Connect, expand **Service Connect** , and then specify the following: @@ -250 +252 @@ The following describes each container log destination in more detail. - 8. (Optional) To interconnect you service using Service Discovery, expand **Service discovery** , and then do the following. + 9. (Optional) To interconnect you service using Service Discovery, expand **Service discovery** , and then do the following. @@ -268 +270 @@ For **TTL** , enter the time in seconds how long a record set is cached by DNS r - 9. (Optional) To interconnect you service using VPC Lattice, xxpand **VPC Lattice** , and then do the following: + 10. (Optional) To interconnect you service using VPC Lattice, xxpand **VPC Lattice** , and then do the following: @@ -288 +290 @@ To delete a target group, choose **Remove**. - 10. (Optional) To configure a load balancer for your service, expand **Load balancing**. + 11. (Optional) To configure a load balancer for your service, expand **Load balancing**. @@ -311 +313 @@ Network Load Balancer | - 11. (Optional) To configure service Auto Scaling, expand **Service auto scaling** , and then specify the following parameters.To use predicte auto scaling, which looks at past load data from traffic flows, configure it after you create the service. For more information, see [Use historical patterns to scale Amazon ECS services with predictive scaling](./predictive-auto-scaling.html). + 12. (Optional) To configure service Auto Scaling, expand **Service auto scaling** , and then specify the following parameters.To use predicte auto scaling, which looks at past load data from traffic flows, configure it after you create the service. For more information, see [Use historical patterns to scale Amazon ECS services with predictive scaling](./predictive-auto-scaling.html). @@ -351 +353 @@ Step scaling | - 12. (Optional) To use a task placement strategy other than the default, expand **Task Placement** , and then choose from the following options. + 13. (Optional) To use a task placement strategy other than the default, expand **Task Placement** , and then choose from the following options. @@ -377 +379 @@ You can enter a maximum of 10 constraints. - 13. If your task uses a data volume that's compatible with configuration at deployment, you can configure the volume by expanding **Volume**. + 14. If your task uses a data volume that's compatible with configuration at deployment, you can configure the volume by expanding **Volume**. @@ -395 +397 @@ Amazon EBS | - 14. (Optional) To help identify your service and tasks, expand the **Tags** section, and then configure your tags. + 15. (Optional) To help identify your service and tasks, expand the **Tags** section, and then configure your tags. @@ -411 +413 @@ Add or remove a tag. - 15. Choose **Create**. + 16. Choose **Create**.