AWS cli documentation change
Summary
Updated CLI version reference from 2.27.51 to 2.27.54 and expanded documentation for deployment lifecycle stages. Added detailed descriptions of deployment phases, clarified bake time terminology, and enhanced lifecycle hook documentation with developer guide references.
Security assessment
The changes add documentation about deployment lifecycle hooks and reference security permissions for Lambda functions in blue/green deployments. While this improves security documentation clarity, there's no evidence of addressing a specific vulnerability. The added link to lifecycle hooks documentation helps implement secure deployment practices.
Diff
diff --git a/cli/latest/reference/ecs/describe-service-deployments.md b/cli/latest/reference/ecs/describe-service-deployments.md index 724c94485..eb759405e 100644 --- a//cli/latest/reference/ecs/describe-service-deployments.md +++ b//cli/latest/reference/ecs/describe-service-deployments.md @@ -15 +15 @@ - * [AWS CLI 2.27.51 Command Reference](../../index.html) » + * [AWS CLI 2.27.54 Command Reference](../../index.html) » @@ -66,2 +65,0 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/ecs-20 -`describe-service-deployments` uses document type values. Document types follow the JSON data model where valid values are: strings, numbers, booleans, null, arrays, and objects. For command input, options and nested parameters that are labeled with the type `document` must be provided as JSON. Shorthand syntax does not support document types. - @@ -382,5 +380,10 @@ serviceDeployments -> (list) ->>> * `SCALE_UP_IN_PROGRESS` \- Creating the new (green) tasks ->>> * `TEST_TRAFFIC_SHIFT_IN_PROGRESS` \- Shifting test traffic to the new (green) tasks ->>> * `PRODUCTION_TRAFFIC_SHIFT_IN_PROGRESS` \- Shifting production traffic to the new (green) tasks ->>> * `BAKE_TIME_IN_PROGRESS` \- The duration when both blue and green service revisions are running simultaneously after the production traffic has shifted ->>> * `CLEAN_UP_IN_PROGRESS` \- Stopping the old (blue) tasks +>>> * RECONCILE_SERVICE The reconciliation stage that only happens when you start a new service deployment with more than 1 service revision in an ACTIVE state. +>>> * PRE_SCALE_UP The green service revision has not started. The blue service revision is handling 100% of the production traffic. There is no test traffic. +>>> * SCALE_UP The stage when the green service revision scales up to 100% and launches new tasks. The green service revision is not serving any traffic at this point. +>>> * POST_SCALE_UP The green service revision has started. The blue service revision is handling 100% of the production traffic. There is no test traffic. +>>> * TEST_TRAFFIC_SHIFT The blue and green service revisions are running. The blue service revision handles 100% of the production traffic. The green service revision is migrating from 0% to 100% of test traffic. +>>> * POST_TEST_TRAFFIC_SHIFT The test traffic shift is complete. The green service revision handles 100% of the test traffic. +>>> * PRODUCTION_TRAFFIC_SHIFT Production traffic is shifting to the green service revision. The green service revision is migrating from 0% to 100% of production traffic. +>>> * POST_PRODUCTION_TRAFFIC_SHIFT The production traffic shift is complete. +>>> * BAKE_TIME The stage when both blue and green service revisions are running simultaneously after the production traffic has shifted. +>>> * CLEAN_UP The stage when the blue service revision has completely scaled down to 0 running tasks. The green service revision is now the production service revision after this stage. @@ -486 +489 @@ serviceDeployments -> (list) ->>>> The duration when both blue and green service revisions are running simultaneously after the production traffic has shifted. +>>>> The time period when both blue and green service revisions are running simultaneously after the production traffic has shifted. @@ -492 +495 @@ serviceDeployments -> (list) ->>>> An array of deployment lifecycle hook objects to run custom logic at specific stages of the deployment lifecycle. These hooks allow you to run custom logic at key points during the deployment process. +>>>> An array of deployment lifecycle hook objects to run custom logic at specific stages of the deployment lifecycle. @@ -497,0 +501,2 @@ serviceDeployments -> (list) +>>>>> For more information, see [Lifecycle hooks for Amazon ECS service deployments](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-lifecycle-hooks.html) in the _Amazon Elastic Container Service Developer Guide_ . +>>>>> @@ -508 +513 @@ serviceDeployments -> (list) ->>>>>> For more information, see [Permissions required for Lambda functions in Amazon ECS blue/green deployments](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/blue-green-permissions.html) in the*Amazon Elastic Container Service Developer Guide* . +>>>>>> For more information, see [Permissions required for Lambda functions in Amazon ECS blue/green deployments](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/blue-green-permissions.html) in the _Amazon Elastic Container Service Developer Guide_ . @@ -514 +519 @@ serviceDeployments -> (list) ->>>>>> * RECONCILE_SERVICE This stage only happens when you start a new service deployment with more than 1 service revision in an ACTIVE state. You can use a lifecycle hook for this stage. +>>>>>> * RECONCILE_SERVICE The reconciliation stage that only happens when you start a new service deployment with more than 1 service revision in an ACTIVE state. You can use a lifecycle hook for this stage. @@ -516 +520,0 @@ serviceDeployments -> (list) ->>>>>> * SCALE_UP The time when the green service revision scales up to 100% and launches new tasks. The green service revision is not serving any traffic at this point. You can’t use a lifecycle hook for this stage. @@ -521,3 +525 @@ serviceDeployments -> (list) ->>>>>> * POST_PRODUCTION_TRAFFIC_SHIFT The production traffic shift is complete. Yes ->>>>>> * BAKE_TIME The duration when both blue and green service revisions are running simultaneously. You can’t use a lifecycle hook for this stage. ->>>>>> * CLEAN_UP The blue service revision has completely scaled down to 0 running tasks. The green service revision is now the production service revision after this stage. You can’t use a lifecycle hook for this stage. +>>>>>> * POST_PRODUCTION_TRAFFIC_SHIFT The production traffic shift is complete. You can use a lifecycle hook for this stage. @@ -530,4 +531,0 @@ serviceDeployments -> (list) ->>>>> ->>>>> hookDetails -> (document) ->>>>> ->>>>>> Optionally provide details about the hook. Use this field to pass custom parameters to your hook target (such as a Lambda function). @@ -623 +621 @@ failures -> (list) - * [AWS CLI 2.27.51 Command Reference](../../index.html) » + * [AWS CLI 2.27.54 Command Reference](../../index.html) »