aws-sdk-ecs 1.203.0 → 1.204.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2c4cb1d87e875223890ee5152994b8a031ed45bc6e1fd56f958ddd199073a395
-  data.tar.gz: 5ee2fcb54722c5a38f3450761a8d2f7608a13048609af26ec8803d3d70a1d317
+  metadata.gz: 5a74bf734d34a33e2fef2a312d74d47a75b537546edb624e72ddf145b58479ff
+  data.tar.gz: 627cac1713d3e612e82c56da82b0a6ed278bfc750ffd9198b471448ea3473003
 SHA512:
-  metadata.gz: 9699b68694fa0156577ced783e1b12aa917a2814472dcbaa2025517f8802fe8eb4e7e8837ec5f275d90abc3fa6c4d3a0867485ffe71f4f9432677a59fa5e6943
-  data.tar.gz: ba4da0d616ed0e522fc37fe8f703af71ae0f39206f86c81815d564a8fd78acc9b625783bd0f5b5238fe4a7a8c1c1764acc4b58a69c6d6bd2e0eabe9793c2e539
+  metadata.gz: beeff90b83243b65c589661fa16bafdd04b8610848578afa2489919d145dd57e96aaa7d4a382f847ebe5da98160b1e87134f09890aab7d20d08507ecc379f706
+  data.tar.gz: 32adae7935082adf2e1b70839c6f4616679df8276dc820db2dea534e984035f182d44db66fcb47b3051c1fea03b53e19c22d71788306aa68205462f294fd90b6

data/CHANGELOG.md

@@ -1,6 +1,11 @@
 Unreleased Changes
 ------------------
 
+1.204.0 (2025-09-05)
+------------------
+
+* Feature - This is a documentation only release that adds additional information for Amazon ECS Availability Zone rebalancing.
+
 1.203.0 (2025-08-26)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.203.0
+1.204.0

data/lib/aws-sdk-ecs/client.rb

@@ -1093,6 +1093,19 @@ module Aws::ECS
     #   Availability Zones][1] in the <i> <i>Amazon Elastic Container Service
     #   Developer Guide</i> </i>.
     #
+    #   The default behavior of `AvailabilityZoneRebalancing` differs between
+    #   create and update requests:
+    #
+    #   * For create service requests, when when no value is specified for
+    #     `AvailabilityZoneRebalancing`, Amazon ECS defaults the value to 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`.
+    #
     #
     #
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html
@@ -1102,13 +1115,13 @@ module Aws::ECS
     #   your service. For more information, see [Service load balancing][1] 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][2] in the *Amazon Elastic
-    #   Container Service Developer Guide*.
+    #   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][2] in the *Amazon Elastic Container Service Developer
+    #   Guide*.
     #
     #   If the service uses the `CODE_DEPLOY` deployment controller, the
     #   service is required to use either an Application Load Balancer or
@@ -1288,20 +1301,13 @@ module Aws::ECS
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html
     #
     # @option params [Integer] :health_check_grace_period_seconds
-    #   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
+    #   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.
     #
-    #   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.
-    #
     # @option params [String] :scheduling_strategy
     #   The scheduling strategy to use for the service. For more information,
     #   see [Services][1].
@@ -11703,6 +11709,19 @@ module Aws::ECS
     #   Availability Zones][1] in the <i> <i>Amazon Elastic Container Service
     #   Developer Guide</i> </i>.
     #
+    #   The default behavior of `AvailabilityZoneRebalancing` differs between
+    #   create and update requests:
+    #
+    #   * For create service requests, when when no value is specified for
+    #     `AvailabilityZoneRebalancing`, Amazon ECS defaults the value to 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`.
+    #
     #   This parameter doesn't trigger a new service deployment.
     #
     #
@@ -12814,7 +12833,7 @@ module Aws::ECS
         tracer: tracer
       )
       context[:gem_name] = 'aws-sdk-ecs'
-      context[:gem_version] = '1.203.0'
+      context[:gem_version] = '1.204.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

data/lib/aws-sdk-ecs/customizations.rb

@@ -1,8 +0,0 @@
-# frozen_string_literal: true
-# WARNING ABOUT GENERATED CODE
-#
-# This file is generated. See the contributing for info on making contributions:
-# https://github.com/aws/aws-sdk-ruby/blob/version-3/CONTRIBUTING.md
-#
-# WARNING ABOUT GENERATED CODE
-

data/lib/aws-sdk-ecs/types.rb

@@ -334,7 +334,7 @@ module Aws::ECS
     end
 
     # Your Amazon Web Services account was blocked. For more information,
-    # contact [ Amazon Web ServicesSupport][1].
+    # contact [ Amazon Web Services Support][1].
     #
     #
     #
@@ -966,7 +966,7 @@ module Aws::ECS
     # [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cloudwatch-container-insights.html
     #
     # @!attribute [rw] name
-    #   The name of the cluster setting. The value is `containerInsights` .
+    #   The name of the cluster setting. The value is `containerInsights`.
     #   @return [String]
     #
     # @!attribute [rw] value
@@ -2725,6 +2725,19 @@ module Aws::ECS
     #   Availability Zones][1] in the <i> <i>Amazon Elastic Container
     #   Service Developer Guide</i> </i>.
     #
+    #   The default behavior of `AvailabilityZoneRebalancing` differs
+    #   between create and update requests:
+    #
+    #   * For create service requests, when when no value is specified for
+    #     `AvailabilityZoneRebalancing`, Amazon ECS defaults the value to 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`.
+    #
     #
     #
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html
@@ -2735,13 +2748,13 @@ module Aws::ECS
     #   your service. For more information, see [Service load balancing][1]
     #   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][2] in the *Amazon Elastic
-    #   Container Service Developer Guide*.
+    #   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][2] in the *Amazon Elastic Container Service
+    #   Developer Guide*.
     #
     #   If the service uses the `CODE_DEPLOY` deployment controller, the
     #   service is required to use either an Application Load Balancer or
@@ -2937,19 +2950,12 @@ module Aws::ECS
     #   @return [Types::NetworkConfiguration]
     #
     # @!attribute [rw] health_check_grace_period_seconds
-    #   The period of time, in seconds, that the Amazon ECS service
+    #   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
-    #   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
+    #   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.
-    #
-    #   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.
     #   @return [Integer]
     #
     # @!attribute [rw] scheduling_strategy
@@ -3970,7 +3976,7 @@ module Aws::ECS
     #   stops the unhealthy tasks one-by-one — using the
     #   `minimumHealthyPercent` as a constraint — to clear up capacity to
     #   launch replacement tasks. For more information about how the
-    #   scheduler replaces unhealthy tasks, see [Amazon ECS services][1] .
+    #   scheduler replaces unhealthy tasks, see [Amazon ECS services][1].
     #
     #   For services that *do not* use a load balancer, the following should
     #   be noted:
@@ -9933,8 +9939,8 @@ module Aws::ECS
     #
     # @!attribute [rw] health_check_grace_period_seconds
     #   The period of time, in seconds, that the Amazon ECS service
-    #   scheduler ignores unhealthy Elastic Load Balancing target health
-    #   checks after a task has first started.
+    #   scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and
+    #   container health checks after a task has first started.
     #   @return [Integer]
     #
     # @!attribute [rw] scheduling_strategy
@@ -10035,6 +10041,19 @@ module Aws::ECS
     #   Availability Zones][1] in the <i> <i>Amazon Elastic Container
     #   Service Developer Guide</i> </i>.
     #
+    #   The default behavior of `AvailabilityZoneRebalancing` differs
+    #   between create and update requests:
+    #
+    #   * For create service requests, when when no value is specified for
+    #     `AvailabilityZoneRebalancing`, Amazon ECS defaults the value to 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`.
+    #
     #
     #
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html
@@ -13944,6 +13963,19 @@ module Aws::ECS
     #   Availability Zones][1] in the <i> <i>Amazon Elastic Container
     #   Service Developer Guide</i> </i>.
     #
+    #   The default behavior of `AvailabilityZoneRebalancing` differs
+    #   between create and update requests:
+    #
+    #   * For create service requests, when when no value is specified for
+    #     `AvailabilityZoneRebalancing`, Amazon ECS defaults the value to 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`.
+    #
     #   This parameter doesn't trigger a new service deployment.
     #
     #

data/lib/aws-sdk-ecs.rb

@@ -55,7 +55,7 @@ module Aws::ECS
   autoload :EndpointProvider, 'aws-sdk-ecs/endpoint_provider'
   autoload :Endpoints, 'aws-sdk-ecs/endpoints'
 
-  GEM_VERSION = '1.203.0'
+  GEM_VERSION = '1.204.0'
 
 end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-ecs
 version: !ruby/object:Gem::Version
-  version: 1.203.0
+  version: 1.204.0
 platform: ruby
 authors:
 - Amazon Web Services