aws-sdk-ecs 1.206.0 → 1.207.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5b37b8cc32db02e58d0d4b93bbdc5fb31120528e8ddf53f6c6416487a02eb65c
-  data.tar.gz: 73e58e61921c639ffe1098f4f60c78a186ffdc55ae5e72cfaf793ca18de7bfda
+  metadata.gz: a83c0f5ec4c5c7c9b8a8ae5726ad22820e231ca3ad603d98284e6ddb867f9599
+  data.tar.gz: 74ecfd2f12dffa5947124d44ea5ce594dcabe215a58cfef4ebb5e0b2c03a5485
 SHA512:
-  metadata.gz: 5fe276978c8a933fb842d2383df40f1c2496dfc1a6c4b7c402f0657686b1c254aca86d3b455cf5f56d31e251a3f3b9472f6a78e8893ac127fda496957d23cffd
-  data.tar.gz: e635ecf6b9dbef422ad53dd0d95ecc4126115266541a09ccbef2f97d50aa015b12765452ab864dd730b782d4d8f367ea04b2b8fb896d7836c69a80738012479a
+  metadata.gz: 24dbf1b122ff1835fe7179177cce3d211a5465417f8ab0323a1170a2a270dcf4a9702781d17b32fe9ecc83e8e8902c1135a57d72157e547b385fa1c952052d57
+  data.tar.gz: f61ede2b1e224d4ffa905edc0ffb00cd45107cc7f3261e53ec752cac65f6e57540deff120fe4de8c86b0bd490d9ed1d412df062543714c4e0ac371f1cc089464

data/CHANGELOG.md

@@ -1,6 +1,11 @@
 Unreleased Changes
 ------------------
 
+1.207.0 (2025-10-01)
+------------------
+
+* Feature - This is a documentation only Amazon ECS release that adds additional information for health checks.
+
 1.206.0 (2025-09-30)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.206.0
+1.207.0

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

@@ -1222,6 +1222,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 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`.
+    #
     #
     #
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html
@@ -1231,13 +1244,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
@@ -1419,17 +1432,13 @@ module Aws::ECS
     # @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
+    #   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.
+    #   If your service has more running tasks than desired, unhealthy tasks
+    #   in the grace period might be stopped to reach the desired count.
     #
     # @option params [String] :scheduling_strategy
     #   The scheduling strategy to use for the service. For more information,
@@ -9332,7 +9341,7 @@ module Aws::ECS
     # @option params [Array<Types::TaskVolumeConfiguration>] :volume_configurations
     #   The details of the volume that was `configuredAtLaunch`. You can
     #   configure the size, volumeType, IOPS, throughput, snapshot and
-    #   encryption in in [TaskManagedEBSVolumeConfiguration][1]. The `name` of
+    #   encryption in [TaskManagedEBSVolumeConfiguration][1]. The `name` of
     #   the volume must match the `name` from the task definition.
     #
     #
@@ -12089,6 +12098,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 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`.
+    #
     #   This parameter doesn't trigger a new service deployment.
     #
     #
@@ -12160,6 +12182,9 @@ module Aws::ECS
     #   can prevent the service scheduler from marking tasks as unhealthy and
     #   stopping them before they have time to come up.
     #
+    #   If your service has more running tasks than desired, unhealthy tasks
+    #   in the grace period might be stopped to reach the desired count.
+    #
     #   This parameter doesn't trigger a new service deployment.
     #
     # @option params [Types::DeploymentController] :deployment_controller
@@ -13202,7 +13227,7 @@ module Aws::ECS
         tracer: tracer
       )
       context[:gem_name] = 'aws-sdk-ecs'
-      context[:gem_version] = '1.206.0'
+      context[:gem_version] = '1.207.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

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

@@ -1067,7 +1067,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
@@ -1429,12 +1429,12 @@ module Aws::ECS
     #   so you can't access a container's mapped port from the host
     #   itself.
     #
-    #   This parameter maps to `PortBindings` in the the docker container
-    #   create command and the `--publish` option to docker run. If the
-    #   network mode of a task definition is set to `none`, then you can't
-    #   specify port mappings. If the network mode of a task definition is
-    #   set to `host`, then host ports must either be undefined or they must
-    #   match the container port in the port mapping.
+    #   This parameter maps to `PortBindings` in the docker container create
+    #   command and the `--publish` option to docker run. If the network
+    #   mode of a task definition is set to `none`, then you can't specify
+    #   port mappings. If the network mode of a task definition is set to
+    #   `host`, then host ports must either be undefined or they must match
+    #   the container port in the port mapping.
     #
     #   <note markdown="1"> After a task reaches the `RUNNING` status, manual and automatic host
     #   and container port assignments are visible in the **Network
@@ -2893,6 +2893,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 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`.
+    #
     #
     #
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html
@@ -2903,13 +2916,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
@@ -3107,17 +3120,13 @@ 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, 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.
+    #   If your service has more running tasks than desired, unhealthy tasks
+    #   in the grace period might be stopped to reach the desired count.
     #   @return [Integer]
     #
     # @!attribute [rw] scheduling_strategy
@@ -4145,7 +4154,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:
@@ -4477,9 +4486,8 @@ module Aws::ECS
     #   @return [Array<String>]
     #
     # @!attribute [rw] hook_details
-    #   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.
+    #   Use this field to specify custom parameters that Amazon ECS will
+    #   pass to your hook target invocations (such as a Lambda function).
     #   @return [Hash,Array,String,Numeric,Boolean]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/DeploymentLifecycleHook AWS API Documentation
@@ -10299,8 +10307,8 @@ module Aws::ECS
     # @!attribute [rw] volume_configurations
     #   The details of the volume that was `configuredAtLaunch`. You can
     #   configure the size, volumeType, IOPS, throughput, snapshot and
-    #   encryption in in [TaskManagedEBSVolumeConfiguration][1]. The `name`
-    #   of the volume must match the `name` from the task definition.
+    #   encryption in [TaskManagedEBSVolumeConfiguration][1]. The `name` of
+    #   the volume must match the `name` from the task definition.
     #
     #
     #
@@ -10640,6 +10648,9 @@ module Aws::ECS
     #   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 your service has more running tasks than desired, unhealthy tasks
+    #   in the grace period might be stopped to reach the desired count.
     #   @return [Integer]
     #
     # @!attribute [rw] scheduling_strategy
@@ -10740,6 +10751,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 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`.
+    #
     #
     #
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html
@@ -14726,6 +14750,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 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`.
+    #
     #   This parameter doesn't trigger a new service deployment.
     #
     #
@@ -14805,6 +14842,9 @@ module Aws::ECS
     #   can prevent the service scheduler from marking tasks as unhealthy
     #   and stopping them before they have time to come up.
     #
+    #   If your service has more running tasks than desired, unhealthy tasks
+    #   in the grace period might be stopped to reach the desired count.
+    #
     #   This parameter doesn't trigger a new service deployment.
     #   @return [Integer]
     #

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.206.0'
+  GEM_VERSION = '1.207.0'
 
 end
 

metadata

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