AWS cli documentation change
Summary
Clarified deployment controller requirements for load balancer usage
Security assessment
Added specificity about 'rolling update (ECS)' deployment controller but no security implications mentioned.
Diff
diff --git a/cli/latest/reference/ecs/create-service.md b/cli/latest/reference/ecs/create-service.md index e10c7f6e0..d97d61e61 100644 --- a//cli/latest/reference/ecs/create-service.md +++ b//cli/latest/reference/ecs/create-service.md @@ -15 +15 @@ - * [AWS CLI 2.31.3 Command Reference](../../index.html) » + * [AWS CLI 2.31.5 Command Reference](../../index.html) » @@ -194,7 +193,0 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/ecs-20 -> -> The default behavior of `AvailabilityZoneRebalancing` differs between create and update requests: -> -> * For create service requests, when no value is specified for `AvailabilityZoneRebalancing` , Amazon ECS defaults the value to `ENABLED` . -> * For update service requests, when no value is specified for `AvailabilityZoneRebalancing` , Amazon ECS defaults to the existing service’s `AvailabilityZoneRebalancing` value. If the service never had an `AvailabilityZoneRebalancing` value set, Amazon ECS treats this as `DISABLED` . -> - @@ -213 +206 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/ecs-20 -> If the service uses the `ECS` deployment controller and using either an Application Load Balancer or Network Load Balancer, you must specify one or more target group ARNs to attach to the service. The service-linked role is required for services that use multiple target groups. For more information, see [Using service-linked roles for Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html) in the _Amazon Elastic Container Service Developer Guide_ . +> If the service uses the rolling update (`ECS` ) deployment controller and using either an Application Load Balancer or Network Load Balancer, you must specify one or more target group ARNs to attach to the service. The service-linked role is required for services that use multiple target groups. For more information, see [Using service-linked roles for Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html) in the _Amazon Elastic Container Service Developer Guide_ . @@ -393,0 +387 @@ JSON Syntax: +> * `MANAGED_INSTANCES` @@ -673 +667 @@ JSON Syntax: ->>>> Use this field to specify custom parameters that Amazon ECS will pass to your hook target invocations (such as a Lambda function). +>>>> The details of the deployment lifecycle hook. This provides additional configuration for how the hook should be executed during deployment operations on Amazon ECS Managed Instances. @@ -861 +855,3 @@ JSON Syntax: -> The period of time, in seconds, that the Amazon Amazon ECS 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. If you do not use any of the health checks, then `healthCheckGracePeriodSeconds` is unused. +> The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started. If you don’t specify a health check grace period value, the default value of `0` is used. If you don’t use any of the health checks, then `healthCheckGracePeriodSeconds` is unused. +> +> If your service’s tasks take a while to start and respond to health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. @@ -2390,0 +2387 @@ service -> (structure) +>> * `MANAGED_INSTANCES` @@ -2647 +2644 @@ service -> (structure) ->>>>> Use this field to specify custom parameters that Amazon ECS will pass to your hook target invocations (such as a Lambda function). +>>>>> The details of the deployment lifecycle hook. This provides additional configuration for how the hook should be executed during deployment operations on Amazon ECS Managed Instances. @@ -2733,0 +2731 @@ service -> (structure) +>>>> * `MANAGED_INSTANCES` @@ -3226,0 +3225 @@ service -> (structure) +>>>> * `MANAGED_INSTANCES` @@ -4202,7 +4200,0 @@ service -> (structure) ->> ->> The default behavior of `AvailabilityZoneRebalancing` differs between create and update requests: ->> ->> * For create service requests, when no value is specified for `AvailabilityZoneRebalancing` , Amazon ECS defaults the value to `ENABLED` . ->> * For update service requests, when no value is specified for `AvailabilityZoneRebalancing` , Amazon ECS defaults to the existing service’s `AvailabilityZoneRebalancing` value. If the service never had an `AvailabilityZoneRebalancing` value set, Amazon ECS treats this as `DISABLED` . ->> - @@ -4227 +4219 @@ service -> (structure) - * [AWS CLI 2.31.3 Command Reference](../../index.html) » + * [AWS CLI 2.31.5 Command Reference](../../index.html) »