AWS cli documentation change
Summary
Updated documentation for ECS delete-service command with clarifications about load balancer ARN types, lifecycle hooks, and deployment stages. Removed redundant sections about document types and hookDetails. Added developer guide references.
Security assessment
Changes focus on improving clarity and accuracy of deployment configurations (e.g., distinguishing ALB/NLB ARNs) and lifecycle hook usage. No explicit mention of security vulnerabilities, patches, or new security features. Removed hookDetails section appears to be documentation cleanup rather than security-related.
Diff
diff --git a/cli/latest/reference/ecs/delete-service.md b/cli/latest/reference/ecs/delete-service.md index 5c6444ff3..0803ce5e4 100644 --- a//cli/latest/reference/ecs/delete-service.md +++ b//cli/latest/reference/ecs/delete-service.md @@ -15 +15 @@ - * [AWS CLI 2.27.51 Command Reference](../../index.html) » + * [AWS CLI 2.27.54 Command Reference](../../index.html) » @@ -72,2 +71,0 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/ecs-20 -`delete-service` 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. - @@ -304 +302 @@ service -> (structure) ->>>>> The Amazon Resource Name (ARN) that identifies the production listener rule for routing production traffic. +>>>>> The Amazon Resource Name (ARN) that that identifies the production listener rule (in the case of an Application Load Balancer) or listener (in the case for an Network Load Balancer) for routing production traffic. @@ -308 +306 @@ service -> (structure) ->>>>> The Amazon Resource Name (ARN) that identifies the test listener rule or listener for routing test traffic. +>>>>> The Amazon Resource Name (ARN) that identifies ) that identifies the test listener rule (in the case of an Application Load Balancer) or listener (in the case for an Network Load Balancer) for routing test traffic. @@ -506 +504 @@ service -> (structure) ->>> 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. @@ -512 +510 @@ service -> (structure) ->>> 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. @@ -517,0 +516,2 @@ service -> (structure) +>>>> 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_ . +>>>> @@ -528 +528 @@ service -> (structure) ->>>>> 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_ . @@ -534 +534 @@ service -> (structure) ->>>>> * 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. @@ -536 +535,0 @@ service -> (structure) ->>>>> * 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. @@ -541,3 +540 @@ service -> (structure) ->>>>> * 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. @@ -550,4 +546,0 @@ service -> (structure) ->>>> ->>>> hookDetails -> (document) ->>>> ->>>>> Optionally provide details about the hook. Use this field to pass custom parameters to your hook target (such as a Lambda function). @@ -776 +769 @@ service -> (structure) ->>>>>>> The Amazon Resource Name (ARN) that identifies the production listener rule for routing production traffic. +>>>>>>> The Amazon Resource Name (ARN) that that identifies the production listener rule (in the case of an Application Load Balancer) or listener (in the case for an Network Load Balancer) for routing production traffic. @@ -780 +773 @@ service -> (structure) ->>>>>>> The Amazon Resource Name (ARN) that identifies the test listener rule or listener for routing test traffic. +>>>>>>> The Amazon Resource Name (ARN) that identifies ) that identifies the test listener rule (in the case of an Application Load Balancer) or listener (in the case for an Network Load Balancer) for routing test traffic. @@ -1802 +1795 @@ service -> (structure) - * [AWS CLI 2.27.51 Command Reference](../../index.html) » + * [AWS CLI 2.27.54 Command Reference](../../index.html) »