AWS AmazonECS documentation change
Summary
Expanded deployment configuration options with new deployment strategies (Rolling/Blue-Green), lifecycle hooks for Lambda functions, and renumbered steps. Added details about role requirements for Lambda functions in blue/green deployments.
Security assessment
The change introduces documentation about assigning IAM roles with blue/green permissions to Lambda functions used in deployment lifecycle hooks. While this improves security guidance, there is no evidence of addressing a specific vulnerability. The security relevance stems from enforcing least-privilege permissions, but this is a standard security practice rather than a response to a disclosed issue.
Diff
diff --git a/AmazonECS/latest/developerguide/update-service-console-v2.md b/AmazonECS/latest/developerguide/update-service-console-v2.md index 4d1e0a0a4..1cb30b0a6 100644 --- a//AmazonECS/latest/developerguide/update-service-console-v2.md +++ b//AmazonECS/latest/developerguide/update-service-console-v2.md @@ -44 +44,32 @@ The console validates that the selected task definition family and revision are - 10. To configure how Amazon ECS detects and handles deployment failures, expand **Deployment failure detection** , and then choose your options. + 10. To configure how tasks are deployed for your service, expand **Deployment options** and then configure your options. + + 1. For **Deployment controller type** , specify the service deployment controller. The Amazon ECS console supports the following controller types: `ECS`. + + 2. For **Deployment strategy** , choose the strategy used by Amazon ECS to deploy new versions of the service. + + 3. Depending on the choice of **Deployment strategy** , do the following: + +Deployment strategy | Steps +---|--- +**Rolling update** | + 1. For **Min running tasks %** , specify a minimum percentage value of tasks that must run during a service deployment. For more information, see [Deploy Amazon ECS services by replacing tasks](./deployment-type-ecs.html). + 2. For **Max running tasks %** , specify a maximum percentage value of tasks that can run during a service deployment. For more information, see [Deploy Amazon ECS services by replacing tasks](./deployment-type-ecs.html). +**Blue/green** | For **Bake time** , specify a time duration, in minutes, that blue and green service revisions should run simultaenously. For more information, see [Amazon ECS blue/green deployments](./deployment-type-blue-green.html). + + 4. To run Lambda functions for a lifecycle stage, under **Deployment lifecyce hooks** do the following for each unique Lambda function: + + 1. Choose **Add**. + +Repeat for every unique function you want to run. + + 2. For **Lambda function** , enter the function name. + + 3. For **Role** , choose the role that you created in the prerequisites with the blue/green permissions. + +For more information, see [Permissions required for Lambda functions in Amazon ECS blue/green deployments](./blue-green-permissions.html). + + 4. For **Lifecycle stages** , select the stages the Lambda function runs. + + 5. (Optional) For **Hook details** , enter a key value pair that provides information about the hook. + + 11. To configure how Amazon ECS detects and handles deployment failures, expand **Deployment failure detection** , and then choose your options. @@ -54 +85 @@ To have the software automatically roll back the deployment to the last complete - 11. To change the compute options, expand **Compute configuration** , and then do the following: + 12. To change the compute options, expand **Compute configuration** , and then do the following: @@ -66 +97 @@ A service that's using an Auto Scaling group capacity provider can't be updated - 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). + 13. (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). @@ -106 +137 @@ Step scaling | - 13. (Optional) To use Service Connect, select **Turn on Service Connect** , and then specify the following: + 14. (Optional) To use Service Connect, select **Turn on Service Connect** , and then specify the following: @@ -116 +147 @@ Step scaling | - 14. If your task uses a data volume that's compatible with configuration at deployment, you can configure the volume by expanding **Volume**. + 15. If your task uses a data volume that's compatible with configuration at deployment, you can configure the volume by expanding **Volume**. @@ -135 +166 @@ Amazon EBS | - 15. (Optional) To help identify your service, expand the **Tags** section, and then configure your tags. + 16. (Optional) To help identify your service, expand the **Tags** section, and then configure your tags. @@ -145 +176 @@ Amazon EBS | - 16. Choose **Update**. + 17. Choose **Update**. @@ -179 +210 @@ Update Amazon ECS service parameters -Updating a blue/green deployment +Deleting a service