You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* <i>Amazon Elastic Container Service Developer Guide</i>
3200
3200
* </i>.</p>
3201
+
* <p>The default behavior of <code>AvailabilityZoneRebalancing</code> differs between create and update requests:</p>
3202
+
* <ul>
3203
+
* <li>
3204
+
* <p>For create service requests, when when no value is specified for <code>AvailabilityZoneRebalancing</code>, Amazon ECS defaults the value to to <code>ENABLED</code>.</p>
3205
+
* </li>
3206
+
* <li>
3207
+
* <p>For update service requests, when no value is specified for <code>AvailabilityZoneRebalancing</code>, Amazon ECS defaults to the existing service’s <code>AvailabilityZoneRebalancing</code> value. If the service never had an <code>AvailabilityZoneRebalancing</code> value set, Amazon ECS treats this as <code>DISABLED</code>.</p>
* <p>A load balancer object representing the load balancers to use with your service. For
3207
3216
* more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html">Service load balancing</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
3208
-
* <p>If the service uses the rolling update (<code>ECS</code>) deployment controller and
3217
+
* <p>If the service uses the <code>ECS</code> deployment controller and
3209
3218
* using either an Application Load Balancer or Network Load Balancer, you must specify one or more target group ARNs to attach
3210
3219
* to the service. The service-linked role is required for services that use multiple
3211
3220
* target groups. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using service-linked roles for Amazon ECS</a> in the
* <p>The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy
3375
-
* Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started. If you don't
3376
-
* specify a health check grace period value, the default value of <code>0</code> is used.
3377
-
* If you don't use any of the health checks, then
3378
-
* <code>healthCheckGracePeriodSeconds</code> is unused.</p>
3379
-
* <p>If your service's tasks take a while to start and respond to health checks, you can
3380
-
* specify a health check grace period of up to 2,147,483,647 seconds (about 69 years).
3381
-
* During that time, the Amazon ECS service scheduler ignores health check status. This grace
3382
-
* period can prevent the service scheduler from marking tasks as unhealthy and stopping
3383
-
* them before they have time to come up.</p>
3383
+
* <p>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 <code>healthCheckGracePeriodSeconds</code> is unused.</p>
3384
3384
* @public
3385
3385
*/
3386
3386
healthCheckGracePeriodSeconds?: number | undefined;
@@ -4263,7 +4263,7 @@ export interface Service {
4263
4263
4264
4264
/**
4265
4265
* <p>The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy
4266
-
* Elastic Load Balancing target health checks after a task has first started.</p>
4266
+
* Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started.</p>
4267
4267
* @public
4268
4268
*/
4269
4269
healthCheckGracePeriodSeconds?: number | undefined;
@@ -4377,6 +4377,15 @@ export interface Service {
4377
4377
* the <i>
4378
4378
* <i>Amazon Elastic Container Service Developer Guide</i>
4379
4379
* </i>.</p>
4380
+
* <p>The default behavior of <code>AvailabilityZoneRebalancing</code> differs between create and update requests:</p>
4381
+
* <ul>
4382
+
* <li>
4383
+
* <p>For create service requests, when when no value is specified for <code>AvailabilityZoneRebalancing</code>, Amazon ECS defaults the value to to <code>ENABLED</code>.</p>
4384
+
* </li>
4385
+
* <li>
4386
+
* <p>For update service requests, when no value is specified for <code>AvailabilityZoneRebalancing</code>, Amazon ECS defaults to the existing service’s <code>AvailabilityZoneRebalancing</code> value. If the service never had an <code>AvailabilityZoneRebalancing</code> value set, Amazon ECS treats this as <code>DISABLED</code>.</p>
* <i>Amazon Elastic Container Service Developer Guide</i>
766
766
* </i>.</p>
767
+
* <p>The default behavior of <code>AvailabilityZoneRebalancing</code> differs between create and update requests:</p>
768
+
* <ul>
769
+
* <li>
770
+
* <p>For create service requests, when when no value is specified for <code>AvailabilityZoneRebalancing</code>, Amazon ECS defaults the value to to <code>ENABLED</code>.</p>
771
+
* </li>
772
+
* <li>
773
+
* <p>For update service requests, when no value is specified for <code>AvailabilityZoneRebalancing</code>, Amazon ECS defaults to the existing service’s <code>AvailabilityZoneRebalancing</code> value. If the service never had an <code>AvailabilityZoneRebalancing</code> value set, Amazon ECS treats this as <code>DISABLED</code>.</p>
774
+
* </li>
775
+
* </ul>
767
776
* <p>This parameter doesn't trigger a new service deployment.</p>
0 commit comments