aws-sdk-ecs 1.97.0 → 1.100.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '0794594ba7b0c2273ba4bd389f8c3d05943632247317918cf8d8cde40d4fb4c0'
-  data.tar.gz: 7035a87cacfd0e4f6a3855b630f57cb97ff5e213d74e2cffd5d1a3fd26ec63b3
+  metadata.gz: b281c3b06771b917ba901037424e0fd0729911f7fb4a379059854c0ace42794c
+  data.tar.gz: ca27528e3d0d988c2d25082036867137404e2aa08701127b529b9b135f775b99
 SHA512:
-  metadata.gz: 291868aa85fad401246451737f4ca1a1d1dcbe879f0390e9b1ad5b5fba99aac4d63bf340e1faf4f65af09cbe436585a4d3b2420d25d4348c76aeffb2d18e30b9
-  data.tar.gz: 77020b769232aacc7a4f551d002b4a32ccac8d4aa15b524914e7368f033666d395a2a1af2ece2d3d5cde03960d29adc4e41d08e7c20357ff5874c3c8c8c392ca
+  metadata.gz: 4e6f1dde1e63dc7968ade75e69a178fde91bf571aa66cdc18d7b1b48ed42647585440c4bf408aa5d85e63bd6a7f04dff9f1163af0dfeaddb8b4c3f61bf1bc391
+  data.tar.gz: e27a8623fc0de329ec6f72128162a25ca9a1deea292df9f9b3932f957d322f1e6206db46d5895c6731c2f81d4066e7082933a7a336c5b3739f6132d7a268422b

data/CHANGELOG.md

@@ -1,6 +1,21 @@
 Unreleased Changes
 ------------------
 
+1.100.0 (2022-06-21)
+------------------
+
+* Feature - Amazon ECS UpdateService now supports the following parameters: PlacementStrategies, PlacementConstraints and CapacityProviderStrategy.
+
+1.99.0 (2022-03-22)
+------------------
+
+* Feature - Documentation only update to address tickets
+
+1.98.0 (2022-03-15)
+------------------
+
+* Feature - Documentation only update to address tickets
+
 1.97.0 (2022-03-07)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.97.0
+1.100.0

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

@@ -473,7 +473,7 @@ module Aws::ECS
     # that it can manage required resources in other Amazon Web Services
     # services on your behalf. However, if the IAM user that makes the call
     # doesn't have permissions to create the service-linked role, it isn't
-    # created. For more information, see [Using Service-Linked Roles for
+    # created. For more information, see [Using service-linked roles for
     # Amazon ECS][1] in the *Amazon Elastic Container Service Developer
     # Guide*.
     #
@@ -526,7 +526,7 @@ module Aws::ECS
     #   PutAccountSetting or PutAccountSettingDefault.
     #
     # @option params [Types::ClusterConfiguration] :configuration
-    #   The execute command configuration for the cluster.
+    #   The `execute` command configuration for the cluster.
     #
     # @option params [Array<String>] :capacity_providers
     #   The short name of one or more capacity providers to associate with the
@@ -683,8 +683,8 @@ module Aws::ECS
     # In addition to maintaining the desired count of tasks in your service,
     # you can optionally run your service behind one or more load balancers.
     # The load balancers distribute traffic across the tasks that are
-    # associated with the service. For more information, see [Service Load
-    # Balancing][1] in the *Amazon Elastic Container Service Developer
+    # associated with the service. For more information, see [Service load
+    # balancing][1] in the *Amazon Elastic Container Service Developer
     # Guide*.
     #
     # Tasks for services that don't use a load balancer are considered
@@ -698,8 +698,8 @@ module Aws::ECS
     #   your desired number of tasks across your cluster. By default, the
     #   service scheduler spreads tasks across Availability Zones. You can
     #   use task placement strategies and constraints to customize task
-    #   placement decisions. For more information, see [Service Scheduler
-    #   Concepts][2] in the *Amazon Elastic Container Service Developer
+    #   placement decisions. For more information, see [Service scheduler
+    #   concepts][2] in the *Amazon Elastic Container Service Developer
     #   Guide*.
     #
     # * `DAEMON` - The daemon scheduling strategy deploys exactly one task
@@ -709,8 +709,8 @@ module Aws::ECS
     #   tasks. It also stops tasks that don't meet the placement
     #   constraints. When using this strategy, you don't need to specify a
     #   desired number of tasks, a task placement strategy, or use Service
-    #   Auto Scaling policies. For more information, see [Service Scheduler
-    #   Concepts][2] in the *Amazon Elastic Container Service Developer
+    #   Auto Scaling policies. For more information, see [Service scheduler
+    #   concepts][2] in the *Amazon Elastic Container Service Developer
     #   Guide*.
     #
     # You can optionally specify a deployment configuration for your
@@ -766,7 +766,7 @@ module Aws::ECS
     # controller, you can specify only parameters that aren't controlled at
     # the task set level. The only required parameter is the service name.
     # You control your services using the CreateTaskSet operation. For more
-    # information, see [Amazon ECS Deployment Types][3] in the *Amazon
+    # information, see [Amazon ECS deployment types][3] in the *Amazon
     # Elastic Container Service Developer Guide*.
     #
     # When the service scheduler launches new tasks, it determines task
@@ -820,7 +820,7 @@ module Aws::ECS
     #
     # @option params [Array<Types::LoadBalancer>] :load_balancers
     #   A load balancer object representing the load balancers to use with
-    #   your service. For more information, see [Service Load Balancing][1] in
+    #   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
@@ -1100,8 +1100,8 @@ module Aws::ECS
     #
     # @option params [Boolean] :enable_ecs_managed_tags
     #   Specifies whether to turn on Amazon ECS managed tags for the tasks
-    #   within the service. For more information, see [Tagging Your Amazon ECS
-    #   Resources][1] in the *Amazon Elastic Container Service Developer
+    #   within the service. For more information, see [Tagging your Amazon ECS
+    #   resources][1] in the *Amazon Elastic Container Service Developer
     #   Guide*.
     #
     #
@@ -1109,12 +1109,10 @@ module Aws::ECS
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html
     #
     # @option params [String] :propagate_tags
-    #   Specifies whether to propagate the tags from the task definition or
-    #   the service to the tasks in the service. If no value is specified, the
-    #   tags aren't propagated. Tags can only be propagated to the tasks
-    #   within the service during service creation. To add tags to a task
-    #   after service creation or task creation, use the TagResource API
-    #   action.
+    #   Specifies whether to propagate the tags from the task definition to
+    #   the task. If no value is specified, the tags aren't propagated. Tags
+    #   can only be propagated to the task during task creation. To add tags
+    #   to a task after task creation, use the TagResource API action.
     #
     # @option params [Boolean] :enable_execute_command
     #   Determines whether the execute command functionality is enabled for
@@ -1457,7 +1455,7 @@ module Aws::ECS
 
     # Create a task set in the specified cluster and service. This is used
     # when a service uses the `EXTERNAL` deployment controller type. For
-    # more information, see [Amazon ECS Deployment Types][1] in the *Amazon
+    # more information, see [Amazon ECS deployment types][1] in the *Amazon
     # Elastic Container Service Developer Guide*.
     #
     #
@@ -1492,7 +1490,7 @@ module Aws::ECS
     #
     # @option params [Array<Types::ServiceRegistry>] :service_registries
     #   The details of the service discovery registries to assign to this task
-    #   set. For more information, see [Service Discovery][1].
+    #   set. For more information, see [Service discovery][1].
     #
     #
     #
@@ -1500,7 +1498,7 @@ module Aws::ECS
     #
     # @option params [String] :launch_type
     #   The launch type that new tasks in the task set uses. For more
-    #   information, see [Amazon ECS Launch Types][1] in the *Amazon Elastic
+    #   information, see [Amazon ECS launch types][1] in the *Amazon Elastic
     #   Container Service Developer Guide*.
     #
     #   If a `launchType` is specified, the `capacityProviderStrategy`
@@ -2180,7 +2178,7 @@ module Aws::ECS
 
     # Deletes a specified task set within a service. This is used when a
     # service uses the `EXTERNAL` deployment controller type. For more
-    # information, see [Amazon ECS Deployment Types][1] in the *Amazon
+    # information, see [Amazon ECS deployment types][1] in the *Amazon
     # Elastic Container Service Developer Guide*.
     #
     #
@@ -2297,11 +2295,12 @@ module Aws::ECS
     #
     # @option params [required, String] :container_instance
     #   The container instance ID or full ARN of the container instance to
-    #   deregister. The ARN contains the `arn:aws:ecs` namespace, followed by
-    #   the Region of the container instance, the Amazon Web Services account
-    #   ID of the container instance owner, the `container-instance`
-    #   namespace, and then the container instance ID. For example,
-    #   `arn:aws:ecs:region:aws_account_id:container-instance/container_instance_ID`.
+    #   deregister. For more information about the ARN format, see [Amazon
+    #   Resource Name (ARN)][1] in the *Amazon ECS Developer Guide*.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-account-settings.html#ecs-resource-ids
     #
     # @option params [Boolean] :force
     #   Forces the container instance to be deregistered. If you have tasks
@@ -3607,6 +3606,9 @@ module Aws::ECS
 
     # Describes a specified task or tasks.
     #
+    # Currently, stopped tasks appear in the returned results for at least
+    # one hour.
+    #
     # @option params [String] :cluster
     #   The short name or full Amazon Resource Name (ARN) of the cluster that
     #   hosts the task or tasks to describe. If you do not specify a cluster,
@@ -3818,12 +3820,13 @@ module Aws::ECS
     # Returns an endpoint for the Amazon ECS agent to poll for updates.
     #
     # @option params [String] :container_instance
-    #   The container instance ID or full ARN of the container instance. The
-    #   ARN contains the `arn:aws:ecs` namespace, followed by the Region of
-    #   the container instance, the Amazon Web Services account ID of the
-    #   container instance owner, the `container-instance` namespace, and then
-    #   the container instance ID. For example,
-    #   `arn:aws:ecs:region:aws_account_id:container-instance/container_instance_ID`.
+    #   The container instance ID or full ARN of the container instance. For
+    #   more information about the ARN format, see [Amazon Resource Name
+    #   (ARN)][1] in the *Amazon ECS Developer Guide*.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-account-settings.html#ecs-resource-ids
     #
     # @option params [String] :cluster
     #   The short name or full Amazon Resource Name (ARN) of the cluster that
@@ -3857,6 +3860,12 @@ module Aws::ECS
 
     # Runs a command remotely on a container within a task.
     #
+    # If you use a condition key in your IAM policy to refine the conditions
+    # for the policy statement, for example limit the actions to a specific
+    # cluster, you recevie an `AccessDeniedException` when there is a
+    # mismatch between the condition key value and the corresponding
+    # parameter value.
+    #
     # @option params [String] :cluster
     #   The Amazon Resource Name (ARN) or short name of the cluster the task
     #   is running in. If you do not specify a cluster, the default cluster is
@@ -6284,6 +6293,9 @@ module Aws::ECS
     #   containers in this task. If `true`, this enables execute command
     #   functionality on all containers in the task.
     #
+    #   If `true`, then the task definition must have a task role, or you must
+    #   provide one as an override.
+    #
     # @option params [String] :group
     #   The name of the task group to associate with the task. The default
     #   value is the family name of the task definition (for example,
@@ -6427,13 +6439,33 @@ module Aws::ECS
     #   task definition to run. If a `revision` isn't specified, the latest
     #   `ACTIVE` revision is used.
     #
+    #   When you create an IAM policy for run-task, you can set the resource
+    #   to be the latest task definition revision, or a specific revision.
+    #
     #   The full ARN value must match the value that you specified as the
-    #   `Resource` of the IAM principal's permissions policy. For example, if
-    #   the `Resource` is
-    #   arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:*,
-    #   the `taskDefinition` ARN value must be
+    #   `Resource` of the IAM principal's permissions policy.
+    #
+    #   When you specify the policy resource as the latest task definition
+    #   version (by setting the `Resource` in the policy to
+    #   `arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName`),
+    #   then set this value to
     #   `arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName`.
     #
+    #   When you specify the policy resource as a specific task definition
+    #   version (by setting the `Resource` in the policy to
+    #   `arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:1`
+    #   or
+    #   `arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:*`),
+    #   then set this value to
+    #   `arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:1`.
+    #
+    #   For more information, see [Policy Resources for Amazon ECS][1] in the
+    #   Amazon Elastic Container Service developer Guide.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/security_iam_service-with-iam.html#security_iam_service-with-iam-id-based-policies-resources
+    #
     # @return [Types::RunTaskResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
     #   * {Types::RunTaskResponse#tasks #tasks} => Array&lt;Types::Task&gt;
@@ -7857,7 +7889,7 @@ module Aws::ECS
     #   services that do not use a load balancer are considered healthy if
     #   they're in the `RUNNING` state. Tasks for services that use a load
     #   balancer are considered healthy if they're in the `RUNNING` state
-    #   and are reported as healthy by the load balancer..
+    #   and are reported as healthy by the load balancer.
     #
     # * The `maximumPercent` parameter represents an upper limit on the
     #   number of running tasks during task replacement. You can use this to
@@ -7977,29 +8009,23 @@ module Aws::ECS
       req.send_request(options)
     end
 
-    # Updating the task placement strategies and constraints on an Amazon
-    # ECS service remains in preview and is a Beta Service as defined by and
-    # subject to the Beta Service Participation Service Terms located at
-    # [https://aws.amazon.com/service-terms][1] ("Beta Terms"). These Beta
-    # Terms apply to your participation in this preview.
-    #
     # Modifies the parameters of a service.
     #
     # For services using the rolling update (`ECS`) you can update the
-    # desired count, the deployment configuration, the network
-    # configuration, load balancers, service registries, enable ECS managed
-    # tags option, propagate tags option, task placement constraints and
-    # strategies, and the task definition. When you update any of these
-    # parameters, Amazon ECS starts new tasks with the new configuration.
+    # desired count, deployment configuration, network configuration, load
+    # balancers, service registries, enable ECS managed tags option,
+    # propagate tags option, task placement constraints and strategies, and
+    # task definition. When you update any of these parameters, Amazon ECS
+    # starts new tasks with the new configuration.
     #
     # For services using the blue/green (`CODE_DEPLOY`) deployment
-    # controller, only the desired count, deployment configuration, task
-    # placement constraints and strategies, enable ECS managed tags option,
-    # and propagate tags can be updated using this API. If the network
-    # configuration, platform version, task definition, or load balancer
-    # need to be updated, create a new CodeDeploy deployment. For more
-    # information, see [CreateDeployment][2] in the *CodeDeploy API
-    # Reference*.
+    # controller, only the desired count, deployment configuration, health
+    # check grace period, task placement constraints and strategies, enable
+    # ECS managed tags option, and propagate tags can be updated using this
+    # API. If the network configuration, platform version, task definition,
+    # or load balancer need to be updated, create a new CodeDeploy
+    # deployment. For more information, see [CreateDeployment][1] in the
+    # *CodeDeploy API Reference*.
     #
     # For services using an external deployment controller, you can update
     # only the desired count, task placement constraints and strategies,
@@ -8097,9 +8123,9 @@ module Aws::ECS
     # <note markdown="1"> You must have a service-linked role when you update any of the
     # following service properties. If you specified a custom IAM role when
     # you created the service, Amazon ECS automatically replaces the
-    # [roleARN][3] associated with the service with the ARN of your
+    # [roleARN][2] associated with the service with the ARN of your
     # service-linked role. For more information, see [Service-linked
-    # roles][4] in the *Amazon Elastic Container Service Developer Guide*.
+    # roles][3] in the *Amazon Elastic Container Service Developer Guide*.
     #
     #  * `loadBalancers,`
     #
@@ -8109,10 +8135,9 @@ module Aws::ECS
     #
     #
     #
-    # [1]: https://aws.amazon.com/service-terms
-    # [2]: https://docs.aws.amazon.com/codedeploy/latest/APIReference/API_CreateDeployment.html
-    # [3]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_Service.html#ECS-Type-Service-roleArn
-    # [4]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html
+    # [1]: https://docs.aws.amazon.com/codedeploy/latest/APIReference/API_CreateDeployment.html
+    # [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_Service.html#ECS-Type-Service-roleArn
+    # [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html
     #
     # @option params [String] :cluster
     #   The short name or full Amazon Resource Name (ARN) of the cluster that
@@ -8254,8 +8279,32 @@ module Aws::ECS
     #   configuration, and then stops the old tasks when the new tasks are
     #   running.
     #
+    #   For services that use rolling updates, you can add, update, or remove
+    #   Elastic Load Balancing target groups. You can update from a single
+    #   target group to multiple target groups and from multiple target groups
+    #   to a single target group.
+    #
+    #   For services that use blue/green deployments, you can update Elastic
+    #   Load Balancing target groups by using ` CreateDeployment ` through
+    #   CodeDeploy. Note that multiple target groups are not supported for
+    #   blue/green deployments. For more information see [Register multiple
+    #   target groups with a service][1] in the *Amazon Elastic Container
+    #   Service Developer Guide*.
+    #
+    #   For services that use the external deployment controller, you can add,
+    #   update, or remove load balancers by using [CreateTaskSet][2]. Note
+    #   that multiple target groups are not supported for external
+    #   deployments. For more information see [Register multiple target groups
+    #   with a service][1] in the *Amazon Elastic Container Service Developer
+    #   Guide*.
+    #
     #   You can remove existing `loadBalancers` by passing an empty list.
     #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/register-multiple-targetgroups.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html
+    #
     # @option params [String] :propagate_tags
     #   Determines whether to propagate the tags from the task definition or
     #   the service to the task. If no value is specified, the tags aren't
@@ -8708,7 +8757,7 @@ module Aws::ECS
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-ecs'
-      context[:gem_version] = '1.97.0'
+      context[:gem_version] = '1.100.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

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

@@ -506,11 +506,13 @@ module Aws::ECS
     # simultaneously.
     #
     # @!attribute [rw] cluster_arn
-    #   The Amazon Resource Name (ARN) that identifies the cluster. The ARN
-    #   contains the `arn:aws:ecs` namespace, followed by the Region of the
-    #   cluster, the Amazon Web Services account ID of the cluster owner,
-    #   the `cluster` namespace, and then the cluster name. For example,
-    #   `arn:aws:ecs:region:012345678910:cluster/test`.
+    #   The Amazon Resource Name (ARN) that identifies the cluster. For more
+    #   information about the ARN format, see [Amazon Resource Name
+    #   (ARN)][1] in the *Amazon ECS Developer Guide*.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-account-settings.html#ecs-resource-ids
     #   @return [String]
     #
     # @!attribute [rw] cluster_name
@@ -642,8 +644,8 @@ module Aws::ECS
     #
     # @!attribute [rw] attachments
     #   The resources attached to a cluster. When using a capacity provider
-    #   with a cluster, the Auto Scaling plan that's created is returned as
-    #   a cluster attachment.
+    #   with a cluster, the capacity provider and associated resources are
+    #   returned as cluster attachments.
     #   @return [Array<Types::Attachment>]
     #
     # @!attribute [rw] attachments_status
@@ -653,8 +655,6 @@ module Aws::ECS
     #   UPDATE\_IN\_PROGRESS
     #
     #   : The available capacity providers for the cluster are updating.
-    #     This occurs when the Auto Scaling plan is provisioning or
-    #     deprovisioning.
     #
     #   UPDATE\_COMPLETE
     #
@@ -1184,12 +1184,12 @@ module Aws::ECS
     #   container is placed. Otherwise, the value of `memory` is used.
     #
     #   The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of
-    #   memory for a container, so you should not specify fewer than 6 MiB
-    #   of memory for your containers.
+    #   memory for a container. So, don't specify less than 6 MiB of memory
+    #   for your containers.
     #
     #   The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB
-    #   of memory for a container, so you should not specify fewer than 4
-    #   MiB of memory for your containers.
+    #   of memory for a container. So, don't specify less than 4 MiB of
+    #   memory for your containers.
     #
     #
     #
@@ -2073,16 +2073,17 @@ module Aws::ECS
       include Aws::Structure
     end
 
-    # An EC2 instance that's running the Amazon ECS agent and has been
-    # registered with a cluster.
+    # An Amazon EC2 or External instance that's running the Amazon ECS
+    # agent and has been registered with a cluster.
     #
     # @!attribute [rw] container_instance_arn
-    #   The Amazon Resource Name (ARN) of the container instance. The ARN
-    #   contains the `arn:aws:ecs` namespace, followed by the Region of the
-    #   container instance, the Amazon Web Services account ID of the
-    #   container instance owner, the `container-instance` namespace, and
-    #   then the container instance ID. For example,
-    #   `arn:aws:ecs:region:aws_account_id:container-instance/container_instance_ID`.
+    #   The Amazon Resource Name (ARN) of the container instance. For more
+    #   information about the ARN format, see [Amazon Resource Name
+    #   (ARN)][1] in the *Amazon ECS Developer Guide*.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-account-settings.html#ecs-resource-ids
     #   @return [String]
     #
     # @!attribute [rw] ec2_instance_id
@@ -2156,7 +2157,7 @@ module Aws::ECS
     #   tasks. The `DRAINING` indicates that new tasks aren't placed on the
     #   container instance and any service tasks running on the container
     #   instance are removed if possible. For more information, see
-    #   [Container Instance Draining][1] in the *Amazon Elastic Container
+    #   [Container instance draining][1] in the *Amazon Elastic Container
     #   Service Developer Guide*.
     #
     #
@@ -2170,9 +2171,9 @@ module Aws::ECS
     #
     # @!attribute [rw] agent_connected
     #   This parameter returns `true` if the agent is connected to Amazon
-    #   ECS. Registered instances with an agent that may be unhealthy or
-    #   stopped return `false`. Only instances connected to an agent can
-    #   accept placement requests.
+    #   ECS. An instance with an agent that may be unhealthy or stopped
+    #   return `false`. Only instances connected to an agent can accept task
+    #   placement requests.
     #   @return [Boolean]
     #
     # @!attribute [rw] running_tasks_count
@@ -2202,8 +2203,8 @@ module Aws::ECS
     #   @return [Time]
     #
     # @!attribute [rw] attachments
-    #   The resources attached to a container instance, such as elastic
-    #   network interfaces.
+    #   The resources attached to a container instance, such as an elastic
+    #   network interface.
     #   @return [Array<Types::Attachment>]
     #
     # @!attribute [rw] tags
@@ -2624,7 +2625,7 @@ module Aws::ECS
     #   @return [Array<Types::ClusterSetting>]
     #
     # @!attribute [rw] configuration
-    #   The execute command configuration for the cluster.
+    #   The `execute` command configuration for the cluster.
     #   @return [Types::ClusterConfiguration]
     #
     # @!attribute [rw] capacity_providers
@@ -2789,7 +2790,7 @@ module Aws::ECS
     #
     # @!attribute [rw] load_balancers
     #   A load balancer object representing the load balancers to use with
-    #   your service. For more information, see [Service Load Balancing][1]
+    #   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
@@ -3091,8 +3092,8 @@ module Aws::ECS
     #
     # @!attribute [rw] enable_ecs_managed_tags
     #   Specifies whether to turn on Amazon ECS managed tags for the tasks
-    #   within the service. For more information, see [Tagging Your Amazon
-    #   ECS Resources][1] in the *Amazon Elastic Container Service Developer
+    #   within the service. For more information, see [Tagging your Amazon
+    #   ECS resources][1] in the *Amazon Elastic Container Service Developer
     #   Guide*.
     #
     #
@@ -3101,12 +3102,10 @@ module Aws::ECS
     #   @return [Boolean]
     #
     # @!attribute [rw] propagate_tags
-    #   Specifies whether to propagate the tags from the task definition or
-    #   the service to the tasks in the service. If no value is specified,
-    #   the tags aren't propagated. Tags can only be propagated to the
-    #   tasks within the service during service creation. To add tags to a
-    #   task after service creation or task creation, use the TagResource
-    #   API action.
+    #   Specifies whether to propagate the tags from the task definition to
+    #   the task. If no value is specified, the tags aren't propagated.
+    #   Tags can only be propagated to the task during task creation. To add
+    #   tags to a task after task creation, use the TagResource API action.
     #   @return [String]
     #
     # @!attribute [rw] enable_execute_command
@@ -3256,7 +3255,7 @@ module Aws::ECS
     #
     # @!attribute [rw] service_registries
     #   The details of the service discovery registries to assign to this
-    #   task set. For more information, see [Service Discovery][1].
+    #   task set. For more information, see [Service discovery][1].
     #
     #
     #
@@ -3265,7 +3264,7 @@ module Aws::ECS
     #
     # @!attribute [rw] launch_type
     #   The launch type that new tasks in the task set uses. For more
-    #   information, see [Amazon ECS Launch Types][1] in the *Amazon Elastic
+    #   information, see [Amazon ECS launch types][1] in the *Amazon Elastic
     #   Container Service Developer Guide*.
     #
     #   If a `launchType` is specified, the `capacityProviderStrategy`
@@ -3882,54 +3881,83 @@ module Aws::ECS
     #
     # @!attribute [rw] maximum_percent
     #   If a service is using the rolling update (`ECS`) deployment type,
-    #   the **maximum percent** parameter represents an upper limit on the
-    #   number of tasks in a service that are allowed in the `RUNNING` or
-    #   `PENDING` state during a deployment, as a percentage of the desired
-    #   number of tasks (rounded down to the nearest integer), and while any
-    #   container instances are in the `DRAINING` state if the service
-    #   contains tasks using the EC2 launch type. This parameter enables you
-    #   to define the deployment batch size. For example, if your service
-    #   has a desired number of four tasks and a maximum percent value of
-    #   200%, the scheduler may start four new tasks before stopping the
-    #   four older tasks (provided that the cluster resources required to do
-    #   this are available). The default value for maximum percent is 200%.
-    #
-    #   If a service is using the blue/green (`CODE_DEPLOY`) or `EXTERNAL`
-    #   deployment types and tasks that use the EC2 launch type, the
-    #   **maximum percent** value is set to the default value and is used to
-    #   define the upper limit on the number of the tasks in the service
-    #   that remain in the `RUNNING` state while the container instances are
-    #   in the `DRAINING` state. If the tasks in the service use the Fargate
-    #   launch type, the maximum percent value is not used, although it is
-    #   returned when describing your service.
+    #   the `maximumPercent` parameter represents an upper limit on the
+    #   number of your service's tasks that are allowed in the `RUNNING` or
+    #   `PENDING` state during a deployment, as a percentage of the
+    #   `desiredCount` (rounded down to the nearest integer). This parameter
+    #   enables you to define the deployment batch size. For example, if
+    #   your service is using the `REPLICA` service scheduler and has a
+    #   `desiredCount` of four tasks and a `maximumPercent` value of 200%,
+    #   the scheduler may start four new tasks before stopping the four
+    #   older tasks (provided that the cluster resources required to do this
+    #   are available). The default `maximumPercent` value for a service
+    #   using the `REPLICA` service scheduler is 200%.
+    #
+    #   If a service is using either the blue/green (`CODE_DEPLOY`) or
+    #   `EXTERNAL` deployment types and tasks that use the EC2 launch type,
+    #   the **maximum percent** value is set to the default value and is
+    #   used to define the upper limit on the number of the tasks in the
+    #   service that remain in the `RUNNING` state while the container
+    #   instances are in the `DRAINING` state. If the tasks in the service
+    #   use the Fargate launch type, the maximum percent value is not used,
+    #   although it is returned when describing your service.
     #   @return [Integer]
     #
     # @!attribute [rw] minimum_healthy_percent
     #   If a service is using the rolling update (`ECS`) deployment type,
-    #   the **minimum healthy percent** represents a lower limit on the
-    #   number of tasks in a service that must remain in the `RUNNING` state
-    #   during a deployment, as a percentage of the desired number of tasks
-    #   (rounded up to the nearest integer), and while any container
-    #   instances are in the `DRAINING` state if the service contains tasks
-    #   using the EC2 launch type. This parameter enables you to deploy
+    #   the `minimumHealthyPercent` represents a lower limit on the number
+    #   of your service's tasks that must remain in the `RUNNING` state
+    #   during a deployment, as a percentage of the `desiredCount` (rounded
+    #   up to the nearest integer). This parameter enables you to deploy
     #   without using additional cluster capacity. For example, if your
-    #   service has a desired number of four tasks and a minimum healthy
-    #   percent of 50%, the scheduler may stop two existing tasks to free up
-    #   cluster capacity before starting two new tasks. Tasks for services
-    #   that *do not* use a load balancer are considered healthy if they're
-    #   in the `RUNNING` state; tasks for services that *do* use a load
-    #   balancer are considered healthy if they're in the `RUNNING` state
-    #   and they're reported as healthy by the load balancer. The default
-    #   value for minimum healthy percent is 100%.
-    #
-    #   If a service is using the blue/green (`CODE_DEPLOY`) or `EXTERNAL`
-    #   deployment types and tasks that use the EC2 launch type, the
-    #   **minimum healthy percent** value is set to the default value and is
-    #   used to define the lower limit on the number of the tasks in the
-    #   service that remain in the `RUNNING` state while the container
-    #   instances are in the `DRAINING` state. If the tasks in the service
-    #   use the Fargate launch type, the minimum healthy percent value is
-    #   not used, although it is returned when describing your service.
+    #   service has a `desiredCount` of four tasks and a
+    #   `minimumHealthyPercent` of 50%, the service scheduler may stop two
+    #   existing tasks to free up cluster capacity before starting two new
+    #   tasks.
+    #
+    #   For services that *do not* use a load balancer, the following should
+    #   be noted:
+    #
+    #   * A service is considered healthy if all essential containers within
+    #     the tasks in the service pass their health checks.
+    #
+    #   * If a task has no essential containers with a health check defined,
+    #     the service scheduler will wait for 40 seconds after a task
+    #     reaches a `RUNNING` state before the task is counted towards the
+    #     minimum healthy percent total.
+    #
+    #   * If a task has one or more essential containers with a health check
+    #     defined, the service scheduler will wait for the task to reach a
+    #     healthy status before counting it towards the minimum healthy
+    #     percent total. A task is considered healthy when all essential
+    #     containers within the task have passed their health checks. The
+    #     amount of time the service scheduler can wait for is determined by
+    #     the container health check settings.
+    #
+    #   For services are that *do* use a load balancer, the following should
+    #   be noted:
+    #
+    #   * If a task has no essential containers with a health check defined,
+    #     the service scheduler will wait for the load balancer target group
+    #     health check to return a healthy status before counting the task
+    #     towards the minimum healthy percent total.
+    #
+    #   * If a task has an essential container with a health check defined,
+    #     the service scheduler will wait for both the task to reach a
+    #     healthy status and the load balancer target group health check to
+    #     return a healthy status before counting the task towards the
+    #     minimum healthy percent total.
+    #
+    #   If a service is using either the blue/green (`CODE_DEPLOY`) or
+    #   `EXTERNAL` deployment types and is running tasks that use the EC2
+    #   launch type, the **minimum healthy percent** value is set to the
+    #   default value and is used to define the lower limit on the number of
+    #   the tasks in the service that remain in the `RUNNING` state while
+    #   the container instances are in the `DRAINING` state. If a service is
+    #   using either the blue/green (`CODE_DEPLOY`) or `EXTERNAL` deployment
+    #   types and is running tasks that use the Fargate launch type, the
+    #   minimum healthy percent value is not used, although it is returned
+    #   when describing your service.
     #   @return [Integer]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/DeploymentConfiguration AWS API Documentation
@@ -3943,7 +3971,7 @@ module Aws::ECS
     end
 
     # The deployment controller to use for the service. For more
-    # information, see [Amazon ECS Deployment Types][1] in the *Amazon
+    # information, see [Amazon ECS deployment types][1] in the *Amazon
     # Elastic Container Service Developer Guide*.
     #
     #
@@ -4010,11 +4038,12 @@ module Aws::ECS
     #
     # @!attribute [rw] container_instance
     #   The container instance ID or full ARN of the container instance to
-    #   deregister. The ARN contains the `arn:aws:ecs` namespace, followed
-    #   by the Region of the container instance, the Amazon Web Services
-    #   account ID of the container instance owner, the `container-instance`
-    #   namespace, and then the container instance ID. For example,
-    #   `arn:aws:ecs:region:aws_account_id:container-instance/container_instance_ID`.
+    #   deregister. For more information about the ARN format, see [Amazon
+    #   Resource Name (ARN)][1] in the *Amazon ECS Developer Guide*.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-account-settings.html#ecs-resource-ids
     #   @return [String]
     #
     # @!attribute [rw] force
@@ -4580,12 +4609,13 @@ module Aws::ECS
     #       }
     #
     # @!attribute [rw] container_instance
-    #   The container instance ID or full ARN of the container instance. The
-    #   ARN contains the `arn:aws:ecs` namespace, followed by the Region of
-    #   the container instance, the Amazon Web Services account ID of the
-    #   container instance owner, the `container-instance` namespace, and
-    #   then the container instance ID. For example,
-    #   `arn:aws:ecs:region:aws_account_id:container-instance/container_instance_ID`.
+    #   The container instance ID or full ARN of the container instance. For
+    #   more information about the ARN format, see [Amazon Resource Name
+    #   (ARN)][1] in the *Amazon ECS Developer Guide*.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-account-settings.html#ecs-resource-ids
     #   @return [String]
     #
     # @!attribute [rw] cluster
@@ -4731,7 +4761,7 @@ module Aws::ECS
     #   will enforce the path set on the EFS access point. If an access
     #   point is used, transit encryption must be enabled in the
     #   `EFSVolumeConfiguration`. For more information, see [Working with
-    #   Amazon EFS Access Points][1] in the *Amazon Elastic File System User
+    #   Amazon EFS access points][1] in the *Amazon Elastic File System User
     #   Guide*.
     #
     #
@@ -4745,7 +4775,7 @@ module Aws::ECS
     #   enabled, transit encryption must be enabled in the
     #   `EFSVolumeConfiguration`. If this parameter is omitted, the default
     #   value of `DISABLED` is used. For more information, see [Using Amazon
-    #   EFS Access Points][1] in the *Amazon Elastic Container Service
+    #   EFS access points][1] in the *Amazon Elastic Container Service
     #   Developer Guide*.
     #
     #
@@ -4764,7 +4794,7 @@ module Aws::ECS
 
     # This parameter is specified when you're using an Amazon Elastic File
     # System file system for task storage. For more information, see [Amazon
-    # EFS Volumes][1] in the *Amazon Elastic Container Service Developer
+    # EFS volumes][1] in the *Amazon Elastic Container Service Developer
     # Guide*.
     #
     #
@@ -4805,7 +4835,7 @@ module Aws::ECS
     #   between the Amazon ECS host and the Amazon EFS server. Transit
     #   encryption must be enabled if Amazon EFS IAM authorization is used.
     #   If this parameter is omitted, the default value of `DISABLED` is
-    #   used. For more information, see [Encrypting Data in Transit][1] in
+    #   used. For more information, see [Encrypting data in transit][1] in
     #   the *Amazon Elastic File System User Guide*.
     #
     #
@@ -4817,8 +4847,8 @@ module Aws::ECS
     #   The port to use when sending encrypted data between the Amazon ECS
     #   host and the Amazon EFS server. If you do not specify a transit
     #   encryption port, it will use the port selection strategy that the
-    #   Amazon EFS mount helper uses. For more information, see [EFS Mount
-    #   Helper][1] in the *Amazon Elastic File System User Guide*.
+    #   Amazon EFS mount helper uses. For more information, see [EFS mount
+    #   helper][1] in the *Amazon Elastic File System User Guide*.
     #
     #
     #
@@ -5135,8 +5165,8 @@ module Aws::ECS
 
     # The authorization configuration details for Amazon FSx for Windows
     # File Server file system. See
-    # [FSxWindowsFileServerVolumeConfiguration][1] in the *Amazon Elastic
-    # Container Service API Reference*.
+    # [FSxWindowsFileServerVolumeConfiguration][1] in the *Amazon ECS API
+    # Reference*.
     #
     # For more information and the input format, see [Amazon FSx for Windows
     # File Server Volumes][2] in the *Amazon Elastic Container Service
@@ -5159,7 +5189,7 @@ module Aws::ECS
     #   The authorization credential option to use. The authorization
     #   credential options can be provided using either the Amazon Resource
     #   Name (ARN) of an Secrets Manager secret or SSM Parameter Store
-    #   parameter. The ARNs refer to the stored credentials.
+    #   parameter. The ARN refers to the stored credentials.
     #   @return [String]
     #
     # @!attribute [rw] domain
@@ -5185,7 +5215,7 @@ module Aws::ECS
     # File Server][1] file system for task storage.
     #
     # For more information and the input format, see [Amazon FSx for Windows
-    # File Server Volumes][2] in the *Amazon Elastic Container Service
+    # File Server volumes][2] in the *Amazon Elastic Container Service
     # Developer Guide*.
     #
     #
@@ -5260,7 +5290,7 @@ module Aws::ECS
 
     # The FireLens configuration for the container. This is used to specify
     # and configure a log router for container logs. For more information,
-    # see [Custom Log Routing][1] in the *Amazon Elastic Container Service
+    # see [Custom log routing][1] in the *Amazon Elastic Container Service
     # Developer Guide*.
     #
     #
@@ -5289,8 +5319,8 @@ module Aws::ECS
     #   cluster, and container instance details to the log event. If
     #   specified, the syntax to use is
     #   `"options":\{"enable-ecs-log-metadata":"true|false","config-file-type:"s3|file","config-file-value":"arn:aws:s3:::mybucket/fluent.conf|filepath"\}`.
-    #   For more information, see [Creating a Task Definition that Uses a
-    #   FireLens Configuration][1] in the *Amazon Elastic Container Service
+    #   For more information, see [Creating a task definition that uses a
+    #   FireLens configuration][1] in the *Amazon Elastic Container Service
     #   Developer Guide*.
     #
     #   <note markdown="1"> Tasks hosted on Fargate only support the `file` configuration file
@@ -5317,6 +5347,15 @@ module Aws::ECS
     # Docker health checks that exist in the container image (such as those
     # specified in a parent image or from the image's Dockerfile).
     #
+    # <note markdown="1"> The Amazon ECS container agent only monitors and reports on the health
+    # checks specified in the task definition. Amazon ECS does not monitor
+    # Docker health checks that are embedded in a container image and not
+    # specified in the container definition. Health check parameters that
+    # are specified in a container definition override any Docker health
+    # checks that exist in the container image.
+    #
+    #  </note>
+    #
     # You can view the health status of both individual containers and a
     # task with the DescribeTasks API operation or when viewing the task
     # details in the console.
@@ -5354,11 +5393,11 @@ 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][1].
     #
     # * 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].
+    #   using platform version `1.1.0` or greater. For more information, see
+    #   [Fargate platform versions][2].
     #
     # * Container health checks aren't supported for tasks that are part of
     #   a service that's configured to use a Classic Load Balancer.
@@ -6676,7 +6715,7 @@ module Aws::ECS
     # balancers with services and task sets, see the CreateService and
     # CreateTaskSet actions.
     #
-    # When you add, update, or remove a load blaancer configuration, Amazon
+    # When you add, update, or remove a load balancer configuration, Amazon
     # ECS starts a new deployment with the updated Elastic Load Balancing
     # configuration. This causes tasks to register to and deregister from
     # load balancers.
@@ -6685,8 +6724,8 @@ module Aws::ECS
     # update the Elastic Load Balancing configuration.
     #
     # A service-linked role is required for services that use multiple
-    # target groups. For more information, see [Service-linked roles][1] in
-    # the *Amazon Elastic Container Service Developer Guide*.
+    # target groups. For more information, see [Using service-linked
+    # roles][1] in the *Amazon Elastic Container Service Developer Guide*.
     #
     #
     #
@@ -6712,12 +6751,12 @@ module Aws::ECS
     #
     #   For services using the `ECS` deployment controller, you can specify
     #   one or multiple target groups. For more information, see
-    #   [Registering Multiple Target Groups with a Service][1] in the
+    #   [Registering multiple target groups with a service][1] in the
     #   *Amazon Elastic Container Service Developer Guide*.
     #
     #   For services using the `CODE_DEPLOY` deployment controller, you're
     #   required to define two target groups for the load balancer. For more
-    #   information, see [Blue/Green Deployment with CodeDeploy][2] in the
+    #   information, see [Blue/green deployment with CodeDeploy][2] in the
     #   *Amazon Elastic Container Service Developer Guide*.
     #
     #   If your service's task definition uses the `awsvpc` network mode,
@@ -6871,7 +6910,7 @@ module Aws::ECS
     #
     # @!attribute [rw] secret_options
     #   The secrets to pass to the log configuration. For more information,
-    #   see [Specifying Sensitive Data][1] in the *Amazon Elastic Container
+    #   see [Specifying sensitive data][1] in the *Amazon Elastic Container
     #   Service Developer Guide*.
     #
     #
@@ -6966,7 +7005,7 @@ module Aws::ECS
     # scale-out actions of the Auto Scaling group. Amazon ECS manages a
     # target tracking scaling policy using an Amazon ECS managed CloudWatch
     # metric with the specified `targetCapacity` value as the target value
-    # for the metric. For more information, see [Using Managed Scaling][1]
+    # for the metric. For more information, see [Using managed scaling][1]
     # in the *Amazon Elastic Container Service Developer Guide*.
     #
     # If managed scaling is disabled, the user must manage the scaling of
@@ -7185,7 +7224,7 @@ module Aws::ECS
     class NoUpdateAvailableException < Aws::EmptyStructure; end
 
     # An object representing a constraint on task placement. For more
-    # information, see [Task Placement Constraints][1] in the *Amazon
+    # information, see [Task placement constraints][1] in the *Amazon
     # Elastic Container Service Developer Guide*.
     #
     # <note markdown="1"> If you're using the Fargate launch type, task placement constraints
@@ -7234,7 +7273,7 @@ module Aws::ECS
     end
 
     # The task placement strategy for a task or service. For more
-    # information, see [Task Placement Strategies][1] in the *Amazon Elastic
+    # information, see [Task placement strategies][1] in the *Amazon Elastic
     # Container Service Developer Guide*.
     #
     #
@@ -8772,6 +8811,9 @@ module Aws::ECS
     #   Determines whether to use the execute command functionality for the
     #   containers in this task. If `true`, this enables execute command
     #   functionality on all containers in the task.
+    #
+    #   If `true`, then the task definition must have a task role, or you
+    #   must provide one as an override.
     #   @return [Boolean]
     #
     # @!attribute [rw] group
@@ -8928,12 +8970,32 @@ module Aws::ECS
     #   task definition to run. If a `revision` isn't specified, the latest
     #   `ACTIVE` revision is used.
     #
+    #   When you create an IAM policy for run-task, you can set the resource
+    #   to be the latest task definition revision, or a specific revision.
+    #
     #   The full ARN value must match the value that you specified as the
-    #   `Resource` of the IAM principal's permissions policy. For example,
-    #   if the `Resource` is
-    #   arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:*,
-    #   the `taskDefinition` ARN value must be
+    #   `Resource` of the IAM principal's permissions policy.
+    #
+    #   When you specify the policy resource as the latest task definition
+    #   version (by setting the `Resource` in the policy to
+    #   `arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName`),
+    #   then set this value to
     #   `arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName`.
+    #
+    #   When you specify the policy resource as a specific task definition
+    #   version (by setting the `Resource` in the policy to
+    #   `arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:1`
+    #   or
+    #   `arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:*`),
+    #   then set this value to
+    #   `arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:1`.
+    #
+    #   For more information, see [Policy Resources for Amazon ECS][1] in
+    #   the Amazon Elastic Container Service developer Guide.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/security_iam_service-with-iam.html#security_iam_service-with-iam-id-based-policies-resources
     #   @return [String]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/RunTaskRequest AWS API Documentation
@@ -9001,7 +9063,7 @@ module Aws::ECS
     #
     #   You can run your Linux tasks on an ARM-based platform by setting the
     #   value to `ARM64`. This option is avaiable for tasks that run on
-    #   Linuc Amazon EC2 instance or Linux containers on Fargate.
+    #   Linux Amazon EC2 instance or Linux containers on Fargate.
     #   @return [String]
     #
     # @!attribute [rw] operating_system_family
@@ -9056,7 +9118,7 @@ module Aws::ECS
     # * To reference sensitive information in the log configuration of a
     #   container, use the `secretOptions` container definition parameter.
     #
-    # For more information, see [Specifying Sensitive Data][1] in the
+    # For more information, see [Specifying sensitive data][1] in the
     # *Amazon Elastic Container Service Developer Guide*.
     #
     #
@@ -9124,11 +9186,13 @@ module Aws::ECS
     # Details on a service within a cluster
     #
     # @!attribute [rw] service_arn
-    #   The ARN that identifies the service. The ARN contains the
-    #   `arn:aws:ecs` namespace, followed by the Region of the service, the
-    #   Amazon Web Services account ID of the service owner, the `service`
-    #   namespace, and then the service name. For example,
-    #   `arn:aws:ecs:region:012345678910:service/my-service`.
+    #   The ARN that identifies the service. For more information about the
+    #   ARN format, see [Amazon Resource Name (ARN)][1] in the *Amazon ECS
+    #   Developer Guide*.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-account-settings.html#ecs-resource-ids
     #   @return [String]
     #
     # @!attribute [rw] service_name
@@ -10252,8 +10316,23 @@ module Aws::ECS
     #
     class TagResourceResponse < Aws::EmptyStructure; end
 
-    # The target container isn't properly configured with the execute
-    # command agent or the container is no longer active or running.
+    # The execute command cannot run. This error can be caused by any of the
+    # following configuration issues:
+    #
+    # * Incorrect IAM permissions
+    #
+    # * The SSM agent is not installed or is not running
+    #
+    # * There is an interface Amazon VPC endpoint for Amazon ECS, but there
+    #   is not one for for Systems Manager Session Manager
+    #
+    # For information about how to troubleshoot the issues, see
+    # [Troubleshooting issues with ECS Exec][1] in the *Amazon Elastic
+    # Container Service Developer Guide*.
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-exec.html
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/TargetNotConnectedException AWS API Documentation
     #
@@ -12062,7 +12141,31 @@ module Aws::ECS
     #   configuration, and then stops the old tasks when the new tasks are
     #   running.
     #
+    #   For services that use rolling updates, you can add, update, or
+    #   remove Elastic Load Balancing target groups. You can update from a
+    #   single target group to multiple target groups and from multiple
+    #   target groups to a single target group.
+    #
+    #   For services that use blue/green deployments, you can update Elastic
+    #   Load Balancing target groups by using ` CreateDeployment ` through
+    #   CodeDeploy. Note that multiple target groups are not supported for
+    #   blue/green deployments. For more information see [Register multiple
+    #   target groups with a service][1] in the *Amazon Elastic Container
+    #   Service Developer Guide*.
+    #
+    #   For services that use the external deployment controller, you can
+    #   add, update, or remove load balancers by using [CreateTaskSet][2].
+    #   Note that multiple target groups are not supported for external
+    #   deployments. For more information see [Register multiple target
+    #   groups with a service][1] in the *Amazon Elastic Container Service
+    #   Developer Guide*.
+    #
     #   You can remove existing `loadBalancers` by passing an empty list.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/register-multiple-targetgroups.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html
     #   @return [Array<Types::LoadBalancer>]
     #
     # @!attribute [rw] propagate_tags

data/lib/aws-sdk-ecs.rb

@@ -49,6 +49,6 @@ require_relative 'aws-sdk-ecs/customizations'
 # @!group service
 module Aws::ECS
 
-  GEM_VERSION = '1.97.0'
+  GEM_VERSION = '1.100.0'
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-ecs
 version: !ruby/object:Gem::Version
-  version: 1.97.0
+  version: 1.100.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-03-07 00:00:00.000000000 Z
+date: 2022-06-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core