aws-sdk-ecs 1.192.0 → 1.194.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 98c19597f8dbe1de1f1618fbda56f0469479eb6b08970d15407276f5746cf703
-  data.tar.gz: 4bedccfd80a9695b0b55e84de17b0d60e3c7df2ceadba83ecb8828da29a9f1fa
+  metadata.gz: ee3ea98304c30b7f4a951642bcdcaefe62f892514bde76debabd1cc01542237f
+  data.tar.gz: fe6518043d1024c569ad19f76723a3a3b95d7667e6e38315d66524e7073bb7e1
 SHA512:
-  metadata.gz: 3a08f10c4dccebd955cfceee551589e7ce896078bd89e6bec1a5b6f7b3e9eae159e212d3a40d78b58f7ddeddeea67caf999ce5d60d92f4821bfc0241524f0bd7
-  data.tar.gz: 89778af0c0cf3f7e1b8e8d98259d62dcb3466d9d2210da184be20696a7c0a150b4d2fba1616dacd36a0f0e73a920daf8a9c1f62fc1acd92e8aaef9ac371b0b38
+  metadata.gz: 7704db613a2eca8b7668508b4996940bf720a46514f7ca11683649af8fd766b616aa933d35addf1da7c1b203458f250ca8ef6ada66e18f0d3e024483fd8c1573
+  data.tar.gz: 6d6bda55d509d52b8fda932bba887c24bb8b2fc0e464958661f8aa04a95617ec129983bb3faea99ccab99089bab0c971deab289eaff2538d6b3eb9271c556dc2

data/CHANGELOG.md

@@ -1,6 +1,16 @@
 Unreleased Changes
 ------------------
 
+1.194.0 (2025-06-12)
+------------------
+
+* Feature - This Amazon ECS  release supports updating the capacityProviderStrategy parameter in update-service.
+
+1.193.0 (2025-06-02)
+------------------
+
+* Feature - Updates Amazon ECS documentation to include note for upcoming default log driver mode change.
+
 1.192.0 (2025-05-16)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.192.0
+1.194.0

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

@@ -6789,6 +6789,18 @@ module Aws::ECS
     #     using this account setting will be used as the default. For more
     #     information about log delivery modes, see [LogConfiguration][7].
     #
+    #     <note markdown="1"> On June 25, 2025, Amazon ECS is changing the default log driver mode
+    #     from `blocking` to `non-blocking` to prioritize task availability
+    #     over logging. To continue using the `blocking` mode after this
+    #     change, do one of the following:
+    #
+    #      * Set the `mode` option in your container definition's
+    #       `logConfiguration` as `blocking`.
+    #
+    #     * Set the `defaultLogDriverMode` account setting to `blocking`.
+    #
+    #      </note>
+    #
     #   * `guardDutyActivate` - The `guardDutyActivate` parameter is read-only
     #     in Amazon ECS and indicates whether Amazon ECS Runtime Monitoring is
     #     enabled or disabled by your security administrator in your Amazon
@@ -7016,6 +7028,18 @@ module Aws::ECS
     #     using this account setting will be used as the default. For more
     #     information about log delivery modes, see [LogConfiguration][7].
     #
+    #     <note markdown="1"> On June 25, 2025, Amazon ECS is changing the default log driver mode
+    #     from `blocking` to `non-blocking` to prioritize task availability
+    #     over logging. To continue using the `blocking` mode after this
+    #     change, do one of the following:
+    #
+    #      * Set the `mode` option in your container definition's
+    #       `logConfiguration` as `blocking`.
+    #
+    #     * Set the `defaultLogDriverMode` account setting to `blocking`.
+    #
+    #      </note>
+    #
     #   * `guardDutyActivate` - The `guardDutyActivate` parameter is read-only
     #     in Amazon ECS and indicates whether Amazon ECS Runtime Monitoring is
     #     enabled or disabled by your security administrator in your Amazon
@@ -11433,31 +11457,20 @@ module Aws::ECS
     #   Zone (based on the previous steps), favoring container instances
     #   with the largest number of running tasks for this service.
     #
-    # <note markdown="1"> You must have a service-linked role when you update any of the
-    # following service properties:
-    #
-    #  * `loadBalancers`,
-    #
-    # * `serviceRegistries`
-    #
-    #  For more information about the role see the `CreateService` request
-    # parameter [ `role` ][5].
-    #
-    #  </note>
-    #
     #
     #
     # [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types
     # [2]: https://docs.aws.amazon.com/codedeploy/latest/APIReference/API_CreateDeployment.html
     # [3]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html
     # [4]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html
-    # [5]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html#ECS-CreateService-request-role
     #
     # @option params [String] :cluster
     #   The short name or full Amazon Resource Name (ARN) of the cluster that
     #   your service runs on. If you do not specify a cluster, the default
     #   cluster is assumed.
     #
+    #   You can't change the cluster name.
+    #
     # @option params [required, String] :service
     #   The name of the service to update.
     #
@@ -11474,41 +11487,39 @@ module Aws::ECS
     #   after the new version is running.
     #
     # @option params [Array<Types::CapacityProviderStrategyItem>] :capacity_provider_strategy
-    #   The capacity provider strategy to update the service to use.
+    #   The details of a capacity provider strategy. You can set a capacity
+    #   provider when you create a cluster, run a task, or update a service.
     #
-    #   if the service uses the default capacity provider strategy for the
-    #   cluster, the service can be updated to use one or more capacity
-    #   providers as opposed to the default capacity provider strategy.
-    #   However, when a service is using a capacity provider strategy that's
-    #   not the default capacity provider strategy, the service can't be
-    #   updated to use the cluster's default capacity provider strategy.
+    #   When you use Fargate, the capacity providers are `FARGATE` or
+    #   `FARGATE_SPOT`.
     #
-    #   A capacity provider strategy consists of one or more capacity
-    #   providers along with the `base` and `weight` to assign to them. A
-    #   capacity provider must be associated with the cluster to be used in a
-    #   capacity provider strategy. The [PutClusterCapacityProviders][1] API
-    #   is used to associate a capacity provider with a cluster. Only capacity
-    #   providers with an `ACTIVE` or `UPDATING` status can be used.
+    #   When you use Amazon EC2, the capacity providers are Auto Scaling
+    #   groups.
     #
-    #   If specifying a capacity provider that uses an Auto Scaling group, the
-    #   capacity provider must already be created. New capacity providers can
-    #   be created with the [CreateClusterCapacityProvider][2] API operation.
+    #   You can change capacity providers for rolling deployments and
+    #   blue/green deployments.
     #
-    #   To use a Fargate capacity provider, specify either the `FARGATE` or
-    #   `FARGATE_SPOT` capacity providers. The Fargate capacity providers are
-    #   available to all accounts and only need to be associated with a
-    #   cluster to be used.
+    #   The following list provides the valid transitions:
     #
-    #   The [PutClusterCapacityProviders][1]API operation is used to update
-    #   the list of available capacity providers for a cluster after the
-    #   cluster is created.
+    #   * Update the Fargate launch type to an EC2 capacity provider.
     #
+    #   * Update the Amazon EC2 launch type to a Fargate capacity provider.
     #
+    #   * Update the Fargate capacity provider to an EC2 capacity provider.
     #
+    #   * Update the Amazon EC2 capacity provider to a Fargate capacity
+    #     provider.
     #
+    #   * Update the EC2 or Fargate capacity provider back to the launch type.
     #
-    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html
-    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateClusterCapacityProvider.html
+    #     Pass an empty list in the `capacityProvider` parameter.
+    #
+    #   For information about Amazon Web Services CDK considerations, see
+    #   [Amazon Web Services CDK considerations][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/update-service-parameters.html
     #
     # @option params [Types::DeploymentConfiguration] :deployment_configuration
     #   Optional deployment parameters that control how many tasks run during
@@ -11605,6 +11616,10 @@ module Aws::ECS
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html
     #
     # @option params [Array<Types::LoadBalancer>] :load_balancers
+    #   <note markdown="1"> You must have a service-linked role when you update this property
+    #
+    #    </note>
+    #
     #   A list of Elastic Load Balancing load balancer objects. It contains
     #   the load balancer name, the container name, and the container port to
     #   access from the load balancer. The container name is as it appears in
@@ -11651,8 +11666,15 @@ module Aws::ECS
     #   that Amazon ECS starts new tasks with the updated tags.
     #
     # @option params [Array<Types::ServiceRegistry>] :service_registries
+    #   <note markdown="1"> You must have a service-linked role when you update this property.
+    #
+    #    For more information about the role see the `CreateService` request
+    #   parameter [ `role` ][1].
+    #
+    #    </note>
+    #
     #   The details for the service discovery registries to assign to this
-    #   service. For more information, see [Service Discovery][1].
+    #   service. For more information, see [Service Discovery][2].
     #
     #   When you add, update, or remove the service registries configuration,
     #   Amazon ECS starts new tasks with the updated service registries
@@ -11663,7 +11685,8 @@ module Aws::ECS
     #
     #
     #
-    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html#ECS-CreateService-request-role
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html
     #
     # @option params [Types::ServiceConnectConfiguration] :service_connect_configuration
     #   The configuration for this service to discover and connect to
@@ -12539,7 +12562,7 @@ module Aws::ECS
         tracer: tracer
       )
       context[:gem_name] = 'aws-sdk-ecs'
-      context[:gem_version] = '1.192.0'
+      context[:gem_version] = '1.194.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

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

@@ -5382,6 +5382,45 @@ module Aws::ECS
     # are part of a service, if the task reports as unhealthy then the task
     # will be stopped and the service scheduler will replace it.
     #
+    # When a container health check fails for a task that is part of a
+    # service, the following process occurs:
+    #
+    # 1.  The task is marked as `UNHEALTHY`.
+    #
+    # 2.  The unhealthy task will be stopped, and during the stopping
+    #     process, it will go through the following states:
+    #
+    #     * `DEACTIVATING` - In this state, Amazon ECS performs additional
+    #       steps before stopping the task. For example, for tasks that are
+    #       part of services configured to use Elastic Load Balancing target
+    #       groups, target groups will be deregistered in this state.
+    #
+    #     * `STOPPING` - The task is in the process of being stopped.
+    #
+    #     * `DEPROVISIONING` - Resources associated with the task are being
+    #       cleaned up.
+    #
+    #     * `STOPPED` - The task has been completely stopped.
+    # 3.  After the old task stops, a new task will be launched to ensure
+    #     service operation, and the new task will go through the following
+    #     lifecycle:
+    #
+    #     * `PROVISIONING` - Resources required for the task are being
+    #       provisioned.
+    #
+    #     * `PENDING` - The task is waiting to be placed on a container
+    #       instance.
+    #
+    #     * `ACTIVATING` - In this state, Amazon ECS pulls container images,
+    #       creates containers, configures task networking, registers load
+    #       balancer target groups, and configures service discovery status.
+    #
+    #     * `RUNNING` - The task is running and performing its work.
+    #
+    # For more detailed information about task lifecycle states, see [Task
+    # lifecycle][1] in the *Amazon Elastic Container Service Developer
+    # Guide*.
+    #
     # The following are notes about container health check support:
     #
     # * If the Amazon ECS container agent becomes disconnected from the
@@ -5396,25 +5435,26 @@ module Aws::ECS
     #
     # * Container health checks require version `1.17.0` or greater of the
     #   Amazon ECS container agent. For more information, see [Updating the
-    #   Amazon ECS container agent][1].
+    #   Amazon ECS container agent][2].
     #
     # * Container health checks are supported for Fargate tasks if you're
     #   using platform version `1.1.0` or greater. For more information, see
-    #   [Fargate platform versions][2].
+    #   [Fargate platform versions][3].
     #
     # * Container health checks aren't supported for tasks that are part of
     #   a service that's configured to use a Classic Load Balancer.
     #
     # For an example of how to specify a task definition with multiple
     # containers where container dependency is specified, see [Container
-    # dependency][3] in the *Amazon Elastic Container Service Developer
+    # dependency][4] in the *Amazon Elastic Container Service Developer
     # Guide*.
     #
     #
     #
-    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html
-    # [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html
-    # [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/example_task_definitions.html#example_task_definition-containerdependency
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-lifecycle-explanation.html
+    # [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html
+    # [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html
+    # [4]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/example_task_definitions.html#example_task_definition-containerdependency
     #
     # @!attribute [rw] command
     #   A string array representing the command that the container runs to
@@ -7027,6 +7067,18 @@ module Aws::ECS
     #     see [Default log driver mode][4] in the *Amazon Elastic Container
     #     Service Developer Guide*.
     #
+    #     <note markdown="1"> On June 25, 2025, Amazon ECS is changing the default log driver
+    #     mode from `blocking` to `non-blocking` to prioritize task
+    #     availability over logging. To continue using the `blocking` mode
+    #     after this change, do one of the following:
+    #
+    #      * Set the `mode` option in your container definition's
+    #       `logConfiguration` as `blocking`.
+    #
+    #     * Set the `defaultLogDriverMode` account setting to `blocking`.
+    #
+    #      </note>
+    #
     #   max-buffer-size
     #
     #   : Required: No
@@ -8017,6 +8069,18 @@ module Aws::ECS
     #     using this account setting will be used as the default. For more
     #     information about log delivery modes, see [LogConfiguration][7].
     #
+    #     <note markdown="1"> On June 25, 2025, Amazon ECS is changing the default log driver
+    #     mode from `blocking` to `non-blocking` to prioritize task
+    #     availability over logging. To continue using the `blocking` mode
+    #     after this change, do one of the following:
+    #
+    #      * Set the `mode` option in your container definition's
+    #       `logConfiguration` as `blocking`.
+    #
+    #     * Set the `defaultLogDriverMode` account setting to `blocking`.
+    #
+    #      </note>
+    #
     #   * `guardDutyActivate` - The `guardDutyActivate` parameter is
     #     read-only in Amazon ECS and indicates whether Amazon ECS Runtime
     #     Monitoring is enabled or disabled by your security administrator
@@ -8172,6 +8236,18 @@ module Aws::ECS
     #     using this account setting will be used as the default. For more
     #     information about log delivery modes, see [LogConfiguration][7].
     #
+    #     <note markdown="1"> On June 25, 2025, Amazon ECS is changing the default log driver
+    #     mode from `blocking` to `non-blocking` to prioritize task
+    #     availability over logging. To continue using the `blocking` mode
+    #     after this change, do one of the following:
+    #
+    #      * Set the `mode` option in your container definition's
+    #       `logConfiguration` as `blocking`.
+    #
+    #     * Set the `defaultLogDriverMode` account setting to `blocking`.
+    #
+    #      </note>
+    #
     #   * `guardDutyActivate` - The `guardDutyActivate` parameter is
     #     read-only in Amazon ECS and indicates whether Amazon ECS Runtime
     #     Monitoring is enabled or disabled by your security administrator
@@ -13316,6 +13392,8 @@ module Aws::ECS
     #   The short name or full Amazon Resource Name (ARN) of the cluster
     #   that your service runs on. If you do not specify a cluster, the
     #   default cluster is assumed.
+    #
+    #   You can't change the cluster name.
     #   @return [String]
     #
     # @!attribute [rw] service
@@ -13337,44 +13415,40 @@ module Aws::ECS
     #   @return [String]
     #
     # @!attribute [rw] capacity_provider_strategy
-    #   The capacity provider strategy to update the service to use.
+    #   The details of a capacity provider strategy. You can set a capacity
+    #   provider when you create a cluster, run a task, or update a service.
     #
-    #   if the service uses the default capacity provider strategy for the
-    #   cluster, the service can be updated to use one or more capacity
-    #   providers as opposed to the default capacity provider strategy.
-    #   However, when a service is using a capacity provider strategy
-    #   that's not the default capacity provider strategy, the service
-    #   can't be updated to use the cluster's default capacity provider
-    #   strategy.
+    #   When you use Fargate, the capacity providers are `FARGATE` or
+    #   `FARGATE_SPOT`.
     #
-    #   A capacity provider strategy consists of one or more capacity
-    #   providers along with the `base` and `weight` to assign to them. A
-    #   capacity provider must be associated with the cluster to be used in
-    #   a capacity provider strategy. The [PutClusterCapacityProviders][1]
-    #   API is used to associate a capacity provider with a cluster. Only
-    #   capacity providers with an `ACTIVE` or `UPDATING` status can be
-    #   used.
+    #   When you use Amazon EC2, the capacity providers are Auto Scaling
+    #   groups.
     #
-    #   If specifying a capacity provider that uses an Auto Scaling group,
-    #   the capacity provider must already be created. New capacity
-    #   providers can be created with the [CreateClusterCapacityProvider][2]
-    #   API operation.
+    #   You can change capacity providers for rolling deployments and
+    #   blue/green deployments.
     #
-    #   To use a Fargate capacity provider, specify either the `FARGATE` or
-    #   `FARGATE_SPOT` capacity providers. The Fargate capacity providers
-    #   are available to all accounts and only need to be associated with a
-    #   cluster to be used.
+    #   The following list provides the valid transitions:
     #
-    #   The [PutClusterCapacityProviders][1]API operation is used to update
-    #   the list of available capacity providers for a cluster after the
-    #   cluster is created.
+    #   * Update the Fargate launch type to an EC2 capacity provider.
     #
+    #   * Update the Amazon EC2 launch type to a Fargate capacity provider.
     #
+    #   * Update the Fargate capacity provider to an EC2 capacity provider.
     #
+    #   * Update the Amazon EC2 capacity provider to a Fargate capacity
+    #     provider.
     #
+    #   * Update the EC2 or Fargate capacity provider back to the launch
+    #     type.
     #
-    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html
-    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateClusterCapacityProvider.html
+    #     Pass an empty list in the `capacityProvider` parameter.
+    #
+    #   For information about Amazon Web Services CDK considerations, see
+    #   [Amazon Web Services CDK considerations][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/update-service-parameters.html
     #   @return [Array<Types::CapacityProviderStrategyItem>]
     #
     # @!attribute [rw] deployment_configuration
@@ -13486,6 +13560,10 @@ module Aws::ECS
     #   @return [Boolean]
     #
     # @!attribute [rw] load_balancers
+    #   <note markdown="1"> You must have a service-linked role when you update this property
+    #
+    #    </note>
+    #
     #   A list of Elastic Load Balancing load balancer objects. It contains
     #   the load balancer name, the container name, and the container port
     #   to access from the load balancer. The container name is as it
@@ -13534,8 +13612,15 @@ module Aws::ECS
     #   @return [String]
     #
     # @!attribute [rw] service_registries
+    #   <note markdown="1"> You must have a service-linked role when you update this property.
+    #
+    #    For more information about the role see the `CreateService` request
+    #   parameter [ `role` ][1].
+    #
+    #    </note>
+    #
     #   The details for the service discovery registries to assign to this
-    #   service. For more information, see [Service Discovery][1].
+    #   service. For more information, see [Service Discovery][2].
     #
     #   When you add, update, or remove the service registries
     #   configuration, Amazon ECS starts new tasks with the updated service
@@ -13547,7 +13632,8 @@ module Aws::ECS
     #
     #
     #
-    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html#ECS-CreateService-request-role
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html
     #   @return [Array<Types::ServiceRegistry>]
     #
     # @!attribute [rw] service_connect_configuration
@@ -13747,7 +13833,7 @@ module Aws::ECS
     #
     #
     #
-    #   [1]: https://github.com/aws/amazon-ecs-agent/commits/master
+    #   [1]: https://github.com/aws/amazon-ecs-agent
     #   @return [String]
     #
     # @!attribute [rw] docker_version

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.192.0'
+  GEM_VERSION = '1.194.0'
 
 end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-ecs
 version: !ruby/object:Gem::Version
-  version: 1.192.0
+  version: 1.194.0
 platform: ruby
 authors:
 - Amazon Web Services
@@ -18,7 +18,7 @@ dependencies:
         version: '3'
     - - ">="
       - !ruby/object:Gem::Version
-        version: 3.216.0
+        version: 3.225.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -28,7 +28,7 @@ dependencies:
         version: '3'
     - - ">="
       - !ruby/object:Gem::Version
-        version: 3.216.0
+        version: 3.225.0
 - !ruby/object:Gem::Dependency
   name: aws-sigv4
   requirement: !ruby/object:Gem::Requirement
@@ -84,7 +84,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '2.5'
+      version: '2.7'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="