aws-sdk-ecs 1.96.0 → 1.99.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ee0ab596fb46070b4afe1dc2741a478a8ed9143f494a9210e177dc6e2ce324d1
-  data.tar.gz: babab9b58e3ec0d076f9fa9cfced0572f235fa9cd70090f449d3047e352f8f27
+  metadata.gz: e16d5368ec5a0127b3f337f2e935d9ce1a7e327926777a8d45faff0fe8f33e9e
+  data.tar.gz: 66aec1d4a433701f7fc74995ad523a8b1afe54507844b495e5aa4c7f3312406b
 SHA512:
-  metadata.gz: 9b03ebdf1cc2ff27e08cb0ddcfba5f94f0a6ce3299d93ea7dc9b30620ad54ae0e35211daef1f41f801da07e076256136b2412dba4851ab5cdfbf9bb8c646ec3c
-  data.tar.gz: e2c739ad2457df5e233eef8464c90fc20ba4efd21df2920f29f9af4a4b4a6bcefe66847e44ab8558f6e16d3a8e9562d92b1d94033ca00449e222e69f1fefddb9
+  metadata.gz: 37790820c3e93c9ea722ea4c16fca49bba8c556021429edc4d83763c2abf5c697793fd24bfb4cd71700177f0535687851af3347daa2828343372b2c83fff08f7
+  data.tar.gz: cdada09a968a4763ad6f1b7703d454e1b7c79dd9403dc9129a923c1213bd8470e227080ab48ad5cb493440b5fed9c82c87b5b8eea6904ff52d92021de810e1bb

data/CHANGELOG.md

@@ -1,6 +1,21 @@
 Unreleased Changes
 ------------------
 
+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)
+------------------
+
+* Feature - Amazon ECS UpdateService API now supports additional parameters: loadBalancers, propagateTags, enableECSManagedTags, and serviceRegistries
+
 1.96.0 (2022-02-24)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.96.0
+1.99.0

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

@@ -521,12 +521,12 @@ module Aws::ECS
     #
     # @option params [Array<Types::ClusterSetting>] :settings
     #   The setting to use when creating a cluster. This parameter is used to
-    #   enable CloudWatch Container Insights for a cluster. If this value is
+    #   turn on CloudWatch Container Insights for a cluster. If this value is
     #   specified, it overrides the `containerInsights` value set with
     #   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
@@ -690,8 +690,7 @@ module Aws::ECS
     # Tasks for services that don't 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 the container instance that they're hosted on is
-    # reported as healthy by the load balancer.
+    # `RUNNING` state and are reported as healthy by the load balancer.
     #
     # There are two service scheduler strategies available:
     #
@@ -844,11 +843,8 @@ module Aws::ECS
     #   listener that you can use to perform validation tests with Lambda
     #   functions before routing production traffic to it.
     #
-    #   After you create a service using the `ECS` deployment controller, the
-    #   load balancer name or target group ARN, container name, and container
-    #   port that's specified in the service definition are immutable. If you
-    #   use the `CODE_DEPLOY` deployment controller, these values can be
-    #   changed when updating the service.
+    #   If you use the `CODE_DEPLOY` deployment controller, these values can
+    #   be changed when updating the service.
     #
     #   For Application Load Balancers and Network Load Balancers, this object
     #   must contain the load balancer target group ARN, the container name,
@@ -1020,6 +1016,10 @@ module Aws::ECS
     #   defined and you don't specify a health check grace period value, the
     #   default value of `0` is used.
     #
+    #   If you do not use an Elastic Load Balancing, we recomend that you use
+    #   the `startPeriod` in the task definition healtch check parameters. For
+    #   more information, see [Health check][1].
+    #
     #   If your service's tasks take a while to start and respond to Elastic
     #   Load Balancing health checks, you can specify a health check grace
     #   period of up to 2,147,483,647 seconds (about 69 years). During that
@@ -1027,6 +1027,10 @@ module Aws::ECS
     #   This grace period can prevent the service scheduler from marking tasks
     #   as unhealthy and stopping them before they have time to come up.
     #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_HealthCheck.html
+    #
     # @option params [String] :scheduling_strategy
     #   The scheduling strategy to use for the service. For more information,
     #   see [Services][1].
@@ -1095,7 +1099,7 @@ module Aws::ECS
     #     your tags per resource limit.
     #
     # @option params [Boolean] :enable_ecs_managed_tags
-    #   Specifies whether to enable Amazon ECS managed tags for the tasks
+    #   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
     #   Guide*.
@@ -1105,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
@@ -1312,7 +1314,7 @@ module Aws::ECS
     #       },
     #     ],
     #     enable_ecs_managed_tags: false,
-    #     propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE
+    #     propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE, NONE
     #     enable_execute_command: false,
     #   })
     #
@@ -1439,7 +1441,7 @@ module Aws::ECS
     #   resp.service.tags[0].value #=> String
     #   resp.service.created_by #=> String
     #   resp.service.enable_ecs_managed_tags #=> Boolean
-    #   resp.service.propagate_tags #=> String, one of "TASK_DEFINITION", "SERVICE"
+    #   resp.service.propagate_tags #=> String, one of "TASK_DEFINITION", "SERVICE", "NONE"
     #   resp.service.enable_execute_command #=> Boolean
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/CreateService AWS API Documentation
@@ -2162,7 +2164,7 @@ module Aws::ECS
     #   resp.service.tags[0].value #=> String
     #   resp.service.created_by #=> String
     #   resp.service.enable_ecs_managed_tags #=> Boolean
-    #   resp.service.propagate_tags #=> String, one of "TASK_DEFINITION", "SERVICE"
+    #   resp.service.propagate_tags #=> String, one of "TASK_DEFINITION", "SERVICE", "NONE"
     #   resp.service.enable_execute_command #=> Boolean
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/DeleteService AWS API Documentation
@@ -3213,7 +3215,7 @@ module Aws::ECS
     #   resp.services[0].tags[0].value #=> String
     #   resp.services[0].created_by #=> String
     #   resp.services[0].enable_ecs_managed_tags #=> Boolean
-    #   resp.services[0].propagate_tags #=> String, one of "TASK_DEFINITION", "SERVICE"
+    #   resp.services[0].propagate_tags #=> String, one of "TASK_DEFINITION", "SERVICE", "NONE"
     #   resp.services[0].enable_execute_command #=> Boolean
     #   resp.failures #=> Array
     #   resp.failures[0].arn #=> String
@@ -4839,8 +4841,8 @@ module Aws::ECS
     # opt-in and opt-out account setting must be set for each Amazon ECS
     # resource separately. The ARN and resource ID format of a resource is
     # defined by the opt-in status of the IAM user or role that created the
-    # resource. You must enable this setting to use Amazon ECS features such
-    # as resource tagging.
+    # resource. You must turn on this setting to use Amazon ECS features
+    # such as resource tagging.
     #
     # When `awsvpcTrunking` is specified, the elastic network interface
     # (ENI) limit for any new container instances that support the feature
@@ -5694,7 +5696,7 @@ module Aws::ECS
     #
     #   For tasks hosted on Amazon EC2 instances, the container instances
     #   require at least version `1.26.0` of the container agent and at least
-    #   version `1.26.0-1` of the `ecs-init` package to enable a proxy
+    #   version `1.26.0-1` of the `ecs-init` package to use a proxy
     #   configuration. If your container instances are launched from the
     #   Amazon ECS-optimized AMI version `20190301` or later, then they
     #   contain the required versions of the container agent and `ecs-init`.
@@ -6267,7 +6269,7 @@ module Aws::ECS
     #   cluster. You can specify up to 10 tasks for each call.
     #
     # @option params [Boolean] :enable_ecs_managed_tags
-    #   Specifies whether to enable Amazon ECS managed tags for the task. For
+    #   Specifies whether to use Amazon ECS managed tags for the task. For
     #   more information, see [Tagging Your Amazon ECS Resources][1] in the
     #   *Amazon Elastic Container Service Developer Guide*.
     #
@@ -6276,10 +6278,13 @@ module Aws::ECS
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html
     #
     # @option params [Boolean] :enable_execute_command
-    #   Determines whether to enable the execute command functionality for the
+    #   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.
+    #
     # @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,
@@ -6423,13 +6428,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;
@@ -6551,7 +6576,7 @@ module Aws::ECS
     #       },
     #     ],
     #     platform_version: "String",
-    #     propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE
+    #     propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE, NONE
     #     reference_id: "String",
     #     started_by: "String",
     #     tags: [
@@ -6704,7 +6729,7 @@ module Aws::ECS
     #   to 10 container instances.
     #
     # @option params [Boolean] :enable_ecs_managed_tags
-    #   Specifies whether to enable Amazon ECS managed tags for the task. For
+    #   Specifies whether to use Amazon ECS managed tags for the task. For
     #   more information, see [Tagging Your Amazon ECS Resources][1] in the
     #   *Amazon Elastic Container Service Developer Guide*.
     #
@@ -6859,7 +6884,7 @@ module Aws::ECS
     #         size_in_gi_b: 1, # required
     #       },
     #     },
-    #     propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE
+    #     propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE, NONE
     #     reference_id: "String",
     #     started_by: "String",
     #     tags: [
@@ -7640,7 +7665,7 @@ module Aws::ECS
     #
     # @option params [required, Array<Types::ClusterSetting>] :settings
     #   The setting to use by default for a cluster. This parameter is used to
-    #   enable CloudWatch Container Insights for a cluster. If this value is
+    #   turn on CloudWatch Container Insights for a cluster. If this value is
     #   specified, it overrides the `containerInsights` value set with
     #   PutAccountSetting or PutAccountSettingDefault.
     #
@@ -7853,8 +7878,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 the container instance they're hosted on is 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
@@ -7982,24 +8006,28 @@ module Aws::ECS
     #
     # Modifies the parameters of a service.
     #
-    # For services using the rolling update (`ECS`) deployment controller,
-    # the desired count, deployment configuration, network configuration,
-    # task placement constraints and strategies, or task definition used can
-    # be updated.
+    # For services using the rolling update (`ECS`) you can update the
+    # 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, and health check grace period
-    # can be updated using this API. If the network configuration, platform
-    # version, or task definition need to be updated, a new CodeDeploy
-    # deployment is created. 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][2] in the
+    # *CodeDeploy API Reference*.
     #
     # For services using an external deployment controller, you can update
-    # only the desired count, task placement constraints and strategies, and
-    # health check grace period using this API. If the launch type, load
+    # only the desired count, task placement constraints and strategies,
+    # health check grace period, enable ECS managed tags option, and
+    # propagate tags option, using this API. If the launch type, load
     # balancer, network configuration, platform version, or task definition
-    # need to be updated, create a new task set. For more information, see
+    # need to be updated, create a new task set For more information, see
     # CreateTaskSet.
     #
     # You can add to or subtract from the number of instantiations of a task
@@ -8035,8 +8063,7 @@ module Aws::ECS
     #   services that don't 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 the container instance they're hosted on is 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 a deployment. You can use it to
@@ -8088,10 +8115,25 @@ 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. 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
+    # service-linked role. For more information, see [Service-linked
+    # roles][4] in the *Amazon Elastic Container Service Developer Guide*.
+    #
+    #  * `loadBalancers,`
+    #
+    # * `serviceRegistries`
+    #
+    #  </note>
+    #
     #
     #
     # [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
     #
     # @option params [String] :cluster
     #   The short name or full Amazon Resource Name (ARN) of the cluster that
@@ -8208,6 +8250,81 @@ module Aws::ECS
     #   If you do not want to override the value that was set when the service
     #   was created, you can set this to `null` when performing this action.
     #
+    # @option params [Boolean] :enable_ecs_managed_tags
+    #   Determines whether to turn on Amazon ECS managed tags for the tasks in
+    #   the service. For more information, see [Tagging Your Amazon ECS
+    #   Resources][1] in the *Amazon Elastic Container Service Developer
+    #   Guide*.
+    #
+    #   Only tasks launched after the update will reflect the update. To
+    #   update the tags on all tasks, set `forceNewDeployment` to `true`, so
+    #   that Amazon ECS starts new tasks with the updated tags.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html
+    #
+    # @option params [Array<Types::LoadBalancer>] :load_balancers
+    #   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
+    #   a container definition.
+    #
+    #   When you add, update, or remove a load balancer configuration, Amazon
+    #   ECS starts new tasks with the updated Elastic Load Balancing
+    #   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
+    #   propagated.
+    #
+    #   Only tasks launched after the update will reflect the update. To
+    #   update the tags on all tasks, set `forceNewDeployment` to `true`, so
+    #   that Amazon ECS starts new tasks with the updated tags.
+    #
+    # @option params [Array<Types::ServiceRegistry>] :service_registries
+    #   The details for the service discovery registries to assign to this
+    #   service. For more information, see [Service Discovery][1].
+    #
+    #   When you add, update, or remove the service registries configuration,
+    #   Amazon ECS starts new tasks with the updated service registries
+    #   configuration, and then stops the old tasks when the new tasks are
+    #   running.
+    #
+    #   You can remove existing `serviceRegistries` by passing an empty list.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html
+    #
     # @return [Types::UpdateServiceResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
     #   * {Types::UpdateServiceResponse#service #service} => Types::Service
@@ -8284,6 +8401,24 @@ module Aws::ECS
     #     force_new_deployment: false,
     #     health_check_grace_period_seconds: 1,
     #     enable_execute_command: false,
+    #     enable_ecs_managed_tags: false,
+    #     load_balancers: [
+    #       {
+    #         target_group_arn: "String",
+    #         load_balancer_name: "String",
+    #         container_name: "String",
+    #         container_port: 1,
+    #       },
+    #     ],
+    #     propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE, NONE
+    #     service_registries: [
+    #       {
+    #         registry_arn: "String",
+    #         port: 1,
+    #         container_name: "String",
+    #         container_port: 1,
+    #       },
+    #     ],
     #   })
     #
     # @example Response structure
@@ -8409,7 +8544,7 @@ module Aws::ECS
     #   resp.service.tags[0].value #=> String
     #   resp.service.created_by #=> String
     #   resp.service.enable_ecs_managed_tags #=> Boolean
-    #   resp.service.propagate_tags #=> String, one of "TASK_DEFINITION", "SERVICE"
+    #   resp.service.propagate_tags #=> String, one of "TASK_DEFINITION", "SERVICE", "NONE"
     #   resp.service.enable_execute_command #=> Boolean
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/UpdateService AWS API Documentation
@@ -8618,7 +8753,7 @@ module Aws::ECS
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-ecs'
-      context[:gem_version] = '1.96.0'
+      context[:gem_version] = '1.99.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

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

@@ -1658,6 +1658,10 @@ module Aws::ECS
     UpdateServiceRequest.add_member(:force_new_deployment, Shapes::ShapeRef.new(shape: Boolean, location_name: "forceNewDeployment"))
     UpdateServiceRequest.add_member(:health_check_grace_period_seconds, Shapes::ShapeRef.new(shape: BoxedInteger, location_name: "healthCheckGracePeriodSeconds"))
     UpdateServiceRequest.add_member(:enable_execute_command, Shapes::ShapeRef.new(shape: BoxedBoolean, location_name: "enableExecuteCommand"))
+    UpdateServiceRequest.add_member(:enable_ecs_managed_tags, Shapes::ShapeRef.new(shape: BoxedBoolean, location_name: "enableECSManagedTags"))
+    UpdateServiceRequest.add_member(:load_balancers, Shapes::ShapeRef.new(shape: LoadBalancers, location_name: "loadBalancers"))
+    UpdateServiceRequest.add_member(:propagate_tags, Shapes::ShapeRef.new(shape: PropagateTags, location_name: "propagateTags"))
+    UpdateServiceRequest.add_member(:service_registries, Shapes::ShapeRef.new(shape: ServiceRegistries, location_name: "serviceRegistries"))
     UpdateServiceRequest.struct_class = Types::UpdateServiceRequest
 
     UpdateServiceResponse.add_member(:service, Shapes::ShapeRef.new(shape: Service, location_name: "service"))

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

@@ -77,8 +77,8 @@ module Aws::ECS
     end
 
     # An attribute is a name-value pair that's associated with an Amazon
-    # ECS object. Attributes enable you to extend the Amazon ECS data model
-    # by adding custom metadata to your resources. For more information, see
+    # ECS object. Use attributes to extend the Amazon ECS data model by
+    # adding custom metadata to your resources. For more information, see
     # [Attributes][1] in the *Amazon Elastic Container Service Developer
     # Guide*.
     #
@@ -748,7 +748,7 @@ module Aws::ECS
     class ClusterNotFoundException < Aws::EmptyStructure; end
 
     # The settings to use when creating a cluster. This parameter is used to
-    # enable CloudWatch Container Insights for a cluster.
+    # turn on CloudWatch Container Insights for a cluster.
     #
     # @note When making an API call, you may pass ClusterSetting
     #   data as a hash:
@@ -1459,7 +1459,7 @@ module Aws::ECS
     #   reversed.
     #
     #   For tasks using the EC2 launch type, the container instances require
-    #   at least version 1.26.0 of the container agent to enable container
+    #   at least version 1.26.0 of the container agent to turn on container
     #   dependencies. However, we recommend using the latest container agent
     #   version. For information about checking your agent version and
     #   updating to the latest version, see [Updating the Amazon ECS
@@ -1509,7 +1509,7 @@ module Aws::ECS
     #   * Windows platform version `1.0.0` or later.
     #
     #   For tasks using the EC2 launch type, your container instances
-    #   require at least version `1.26.0` of the container agent to enable a
+    #   require at least version `1.26.0` of the container agent to use a
     #   container start timeout value. However, we recommend using the
     #   latest container agent version. For information about checking your
     #   agent version and updating to the latest version, see [Updating the
@@ -1549,7 +1549,7 @@ module Aws::ECS
     #   `ECS_CONTAINER_STOP_TIMEOUT` agent configuration variable are set,
     #   then the default values of 30 seconds for Linux containers and 30
     #   seconds on Windows containers are used. Your container instances
-    #   require at least version 1.26.0 of the container agent to enable a
+    #   require at least version 1.26.0 of the container agent to use a
     #   container stop timeout value. However, we recommend using the latest
     #   container agent version. For information about checking your agent
     #   version and updating to the latest version, see [Updating the Amazon
@@ -2001,7 +2001,7 @@ module Aws::ECS
     # defined for container startup, for container shutdown it is reversed.
     #
     # Your Amazon ECS container instances require at least version 1.26.0 of
-    # the container agent to enable container dependencies. However, we
+    # the container agent to use container dependencies. However, we
     # recommend using the latest container agent version. For information
     # about checking your agent version and updating to the latest version,
     # see [Updating the Amazon ECS Container Agent][1] in the *Amazon
@@ -2618,13 +2618,13 @@ module Aws::ECS
     #
     # @!attribute [rw] settings
     #   The setting to use when creating a cluster. This parameter is used
-    #   to enable CloudWatch Container Insights for a cluster. If this value
-    #   is specified, it overrides the `containerInsights` value set with
-    #   PutAccountSetting or PutAccountSettingDefault.
+    #   to turn on CloudWatch Container Insights for a cluster. If this
+    #   value is specified, it overrides the `containerInsights` value set
+    #   with PutAccountSetting or PutAccountSettingDefault.
     #   @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
@@ -2760,7 +2760,7 @@ module Aws::ECS
     #           },
     #         ],
     #         enable_ecs_managed_tags: false,
-    #         propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE
+    #         propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE, NONE
     #         enable_execute_command: false,
     #       }
     #
@@ -2812,11 +2812,8 @@ module Aws::ECS
     #   optional listener that you can use to perform validation tests with
     #   Lambda functions before routing production traffic to it.
     #
-    #   After you create a service using the `ECS` deployment controller,
-    #   the load balancer name or target group ARN, container name, and
-    #   container port that's specified in the service definition are
-    #   immutable. If you use the `CODE_DEPLOY` deployment controller, these
-    #   values can be changed when updating the service.
+    #   If you use the `CODE_DEPLOY` deployment controller, these values can
+    #   be changed when updating the service.
     #
     #   For Application Load Balancers and Network Load Balancers, this
     #   object must contain the load balancer target group ARN, the
@@ -3004,6 +3001,10 @@ module Aws::ECS
     #   load balancer defined and you don't specify a health check grace
     #   period value, the default value of `0` is used.
     #
+    #   If you do not use an Elastic Load Balancing, we recomend that you
+    #   use the `startPeriod` in the task definition healtch check
+    #   parameters. For more information, see [Health check][1].
+    #
     #   If your service's tasks take a while to start and respond to
     #   Elastic Load Balancing health checks, you can specify a health check
     #   grace period of up to 2,147,483,647 seconds (about 69 years). During
@@ -3011,6 +3012,10 @@ module Aws::ECS
     #   status. This grace period can prevent the service scheduler from
     #   marking tasks as unhealthy and stopping them before they have time
     #   to come up.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_HealthCheck.html
     #   @return [Integer]
     #
     # @!attribute [rw] scheduling_strategy
@@ -3085,7 +3090,7 @@ module Aws::ECS
     #   @return [Array<Types::Tag>]
     #
     # @!attribute [rw] enable_ecs_managed_tags
-    #   Specifies whether to enable Amazon ECS managed tags for the tasks
+    #   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
     #   Guide*.
@@ -3096,12 +3101,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
@@ -3808,9 +3811,9 @@ module Aws::ECS
     # The **deployment circuit breaker** determines whether a service
     # deployment will fail if the service can't reach a steady state. If
     # enabled, a service deployment will transition to a failed state and
-    # stop launching new tasks. You can also enable Amazon ECS to roll back
-    # your service to the last completed deployment after a failure. For
-    # more information, see [Rolling update][1] in the *Amazon Elastic
+    # stop launching new tasks. You can also configure Amazon ECS to roll
+    # back your service to the last completed deployment after a failure.
+    # For more information, see [Rolling update][1] in the *Amazon Elastic
     # Container Service Developer Guide*.
     #
     #
@@ -3826,15 +3829,15 @@ module Aws::ECS
     #       }
     #
     # @!attribute [rw] enable
-    #   Determines whether to enable the deployment circuit breaker logic
-    #   for the service.
+    #   Determines whether to use the deployment circuit breaker logic for
+    #   the service.
     #   @return [Boolean]
     #
     # @!attribute [rw] rollback
-    #   Determines whether to enable Amazon ECS to roll back the service if
-    #   a service deployment fails. If rollback is enabled, when a service
-    #   deployment fails, the service is rolled back to the last deployment
-    #   that completed successfully.
+    #   Determines whether to configure Amazon ECS to roll back the service
+    #   if a service deployment fails. If rollback is enabled, when a
+    #   service deployment fails, the service is rolled back to the last
+    #   deployment that completed successfully.
     #   @return [Boolean]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/DeploymentCircuitBreaker AWS API Documentation
@@ -4796,12 +4799,12 @@ module Aws::ECS
     #   @return [String]
     #
     # @!attribute [rw] transit_encryption
-    #   Determines whether to enable encryption for Amazon EFS data in
-    #   transit 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 the *Amazon Elastic File System User Guide*.
+    #   Determines whether to use encryption for Amazon EFS data in transit
+    #   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
+    #   the *Amazon Elastic File System User Guide*.
     #
     #
     #
@@ -4898,12 +4901,9 @@ module Aws::ECS
     # more information, see [Fargate task storage][1] in the *Amazon ECS
     # User Guide for Fargate*.
     #
-    # <note markdown="1"> This parameter is only supported for tasks hosted on Fargate using the
-    # following platform versions:
-    #
-    #  * Linux platform version `1.4.0` or later.
-    #
-    # * Windows platform version `1.0.0` or later.
+    # <note markdown="1"> This parameter is only supported for tasks hosted on Fargate using
+    # Linux platform version `1.4.0` or later. This parameter is not
+    # supported for Windows containers on Fargate.
     #
     #  </note>
     #
@@ -5010,8 +5010,8 @@ module Aws::ECS
     #   @return [String]
     #
     # @!attribute [rw] cloud_watch_encryption_enabled
-    #   Determines whether to enable encryption on the CloudWatch logs. If
-    #   not specified, encryption will be disabled.
+    #   Determines whether to use encryption on the CloudWatch logs. If not
+    #   specified, encryption will be disabled.
     #   @return [Boolean]
     #
     # @!attribute [rw] s3_bucket_name
@@ -5315,6 +5315,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.
@@ -6674,6 +6683,22 @@ module Aws::ECS
     # balancers with services and task sets, see the CreateService and
     # CreateTaskSet actions.
     #
+    # 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.
+    #
+    # We recommend that you verify this on a test environment before you
+    # 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*.
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html
+    #
     # @note When making an API call, you may pass LoadBalancer
     #   data as a hash:
     #
@@ -6970,8 +6995,7 @@ module Aws::ECS
     #       }
     #
     # @!attribute [rw] status
-    #   Determines whether to enable managed scaling for the capacity
-    #   provider.
+    #   Determines whether to use managed scaling for the capacity provider.
     #   @return [String]
     #
     # @!attribute [rw] target_capacity
@@ -7407,7 +7431,7 @@ module Aws::ECS
     #
     # For tasks that use the EC2 launch type, the container instances
     # require at least version 1.26.0 of the container agent and at least
-    # version 1.26.0-1 of the `ecs-init` package to enable a proxy
+    # version 1.26.0-1 of the `ecs-init` package to use a proxy
     # configuration. If your container instances are launched from the
     # Amazon ECS optimized AMI version `20190301` or later, then they
     # contain the required versions of the container agent and `ecs-init`.
@@ -8391,7 +8415,7 @@ module Aws::ECS
     #
     #   For tasks hosted on Amazon EC2 instances, the container instances
     #   require at least version `1.26.0` of the container agent and at
-    #   least version `1.26.0-1` of the `ecs-init` package to enable a proxy
+    #   least version `1.26.0-1` of the `ecs-init` package to use a proxy
     #   configuration. If your container instances are launched from the
     #   Amazon ECS-optimized AMI version `20190301` or later, then they
     #   contain the required versions of the container agent and `ecs-init`.
@@ -8703,7 +8727,7 @@ module Aws::ECS
     #           },
     #         ],
     #         platform_version: "String",
-    #         propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE
+    #         propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE, NONE
     #         reference_id: "String",
     #         started_by: "String",
     #         tags: [
@@ -8742,9 +8766,9 @@ module Aws::ECS
     #   @return [Integer]
     #
     # @!attribute [rw] enable_ecs_managed_tags
-    #   Specifies whether to enable Amazon ECS managed tags for the task.
-    #   For more information, see [Tagging Your Amazon ECS Resources][1] in
-    #   the *Amazon Elastic Container Service Developer Guide*.
+    #   Specifies whether to use Amazon ECS managed tags for the task. For
+    #   more information, see [Tagging Your Amazon ECS Resources][1] in the
+    #   *Amazon Elastic Container Service Developer Guide*.
     #
     #
     #
@@ -8752,9 +8776,12 @@ module Aws::ECS
     #   @return [Boolean]
     #
     # @!attribute [rw] enable_execute_command
-    #   Determines whether to enable the execute command functionality for
-    #   the containers in this task. If `true`, this enables execute command
+    #   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
@@ -8911,12 +8938,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
@@ -9063,12 +9110,23 @@ module Aws::ECS
     #   either the full ARN of the Secrets Manager secret or the full ARN of
     #   the parameter in the SSM Parameter Store.
     #
+    #   For information about the require Identity and Access Management
+    #   permissions, see [Required IAM permissions for Amazon ECS
+    #   secrets][1] (for Secrets Manager) or [Required IAM permissions for
+    #   Amazon ECS secrets][2] (for Systems Manager Parameter store) in the
+    #   *Amazon Elastic Container Service Developer Guide*.
+    #
     #   <note markdown="1"> If the SSM Parameter Store parameter exists in the same Region as
     #   the task you're launching, then you can use either the full ARN or
     #   name of the parameter. If the parameter exists in a different
     #   Region, then the full ARN must be specified.
     #
     #    </note>
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data-secrets.html#secrets-iam
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data-parameters.html
     #   @return [String]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/Secret AWS API Documentation
@@ -9257,7 +9315,7 @@ module Aws::ECS
     #     placement decisions.
     #
     #   * `DAEMON`-The daemon scheduling strategy deploys exactly one task
-    #     on each active container instance. This taskmeets all of the task
+    #     on each active container instance. This task meets all of the task
     #     placement constraints that you specify in your cluster. The
     #     service scheduler also evaluates the task placement constraints
     #     for running tasks. It stop tasks that don't meet the placement
@@ -9314,8 +9372,8 @@ module Aws::ECS
     #   @return [String]
     #
     # @!attribute [rw] enable_ecs_managed_tags
-    #   Determines whether to enable Amazon ECS managed tags for the tasks
-    #   in the service. For more information, see [Tagging Your Amazon ECS
+    #   Determines whether to use Amazon ECS managed tags for the tasks in
+    #   the service. For more information, see [Tagging Your Amazon ECS
     #   Resources][1] in the *Amazon Elastic Container Service Developer
     #   Guide*.
     #
@@ -9416,6 +9474,13 @@ module Aws::ECS
 
     # The details for the service registry.
     #
+    # Each service may be associated with one service registry. Multiple
+    # service registries for each service are not supported.
+    #
+    # When you add, update, or remove the service registries configuration,
+    # Amazon ECS starts a new deployment. New tasks are registered and
+    # deregistered to the updated service registry configuration.
+    #
     # @note When making an API call, you may pass ServiceRegistry
     #   data as a hash:
     #
@@ -9484,7 +9549,7 @@ module Aws::ECS
     #   @return [String]
     #
     # @!attribute [rw] stream_url
-    #   A URL back to managed agent on the container that the SSM Session
+    #   A URL to the managed agent on the container that the SSM Session
     #   Manager client uses to send commands and receive output from the
     #   container.
     #   @return [String]
@@ -9589,7 +9654,7 @@ module Aws::ECS
     #             size_in_gi_b: 1, # required
     #           },
     #         },
-    #         propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE
+    #         propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE, NONE
     #         reference_id: "String",
     #         started_by: "String",
     #         tags: [
@@ -9614,9 +9679,9 @@ module Aws::ECS
     #   @return [Array<String>]
     #
     # @!attribute [rw] enable_ecs_managed_tags
-    #   Specifies whether to enable Amazon ECS managed tags for the task.
-    #   For more information, see [Tagging Your Amazon ECS Resources][1] in
-    #   the *Amazon Elastic Container Service Developer Guide*.
+    #   Specifies whether to use Amazon ECS managed tags for the task. For
+    #   more information, see [Tagging Your Amazon ECS Resources][1] in the
+    #   *Amazon Elastic Container Service Developer Guide*.
     #
     #
     #
@@ -10217,8 +10282,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
     #
@@ -10456,6 +10536,20 @@ module Aws::ECS
     # @!attribute [rw] stop_code
     #   The stop code indicating why a task was stopped. The `stoppedReason`
     #   might contain additional details.
+    #
+    #   The following are valid values:
+    #
+    #   * `TaskFailedToStart`
+    #
+    #   * `EssentialContainerExited`
+    #
+    #   * `UserInitiated`
+    #
+    #   * `TerminationNotice`
+    #
+    #   * `ServiceSchedulerInitiated`
+    #
+    #   * `SpotInterruption`
     #   @return [String]
     #
     # @!attribute [rw] stopped_at
@@ -10898,12 +10992,12 @@ module Aws::ECS
     #
     #   Your Amazon ECS container instances require at least version 1.26.0
     #   of the container agent and at least version 1.26.0-1 of the
-    #   `ecs-init` package to enable a proxy configuration. If your
-    #   container instances are launched from the Amazon ECS optimized AMI
-    #   version `20190301` or later, they contain the required versions of
-    #   the container agent and `ecs-init`. For more information, see
-    #   [Amazon ECS-optimized Linux AMI][1] in the *Amazon Elastic Container
-    #   Service Developer Guide*.
+    #   `ecs-init` package to use a proxy configuration. If your container
+    #   instances are launched from the Amazon ECS optimized AMI version
+    #   `20190301` or later, they contain the required versions of the
+    #   container agent and `ecs-init`. For more information, see [Amazon
+    #   ECS-optimized Linux AMI][1] in the *Amazon Elastic Container Service
+    #   Developer Guide*.
     #
     #
     #
@@ -11606,9 +11700,9 @@ module Aws::ECS
     #
     # @!attribute [rw] settings
     #   The setting to use by default for a cluster. This parameter is used
-    #   to enable CloudWatch Container Insights for a cluster. If this value
-    #   is specified, it overrides the `containerInsights` value set with
-    #   PutAccountSetting or PutAccountSettingDefault.
+    #   to turn on CloudWatch Container Insights for a cluster. If this
+    #   value is specified, it overrides the `containerInsights` value set
+    #   with PutAccountSetting or PutAccountSettingDefault.
     #   @return [Array<Types::ClusterSetting>]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/UpdateClusterSettingsRequest AWS API Documentation
@@ -11775,7 +11869,7 @@ module Aws::ECS
     end
 
     # @!attribute [rw] task_set
-    #   Details about the task set.
+    #   etails about the task set.
     #   @return [Types::TaskSet]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/UpdateServicePrimaryTaskSetResponse AWS API Documentation
@@ -11832,6 +11926,24 @@ module Aws::ECS
     #         force_new_deployment: false,
     #         health_check_grace_period_seconds: 1,
     #         enable_execute_command: false,
+    #         enable_ecs_managed_tags: false,
+    #         load_balancers: [
+    #           {
+    #             target_group_arn: "String",
+    #             load_balancer_name: "String",
+    #             container_name: "String",
+    #             container_port: 1,
+    #           },
+    #         ],
+    #         propagate_tags: "TASK_DEFINITION", # accepts TASK_DEFINITION, SERVICE, NONE
+    #         service_registries: [
+    #           {
+    #             registry_arn: "String",
+    #             port: 1,
+    #             container_name: "String",
+    #             container_port: 1,
+    #           },
+    #         ],
     #       }
     #
     # @!attribute [rw] cluster
@@ -11969,6 +12081,86 @@ module Aws::ECS
     #   action.
     #   @return [Boolean]
     #
+    # @!attribute [rw] enable_ecs_managed_tags
+    #   Determines whether to turn on Amazon ECS managed tags for the tasks
+    #   in the service. For more information, see [Tagging Your Amazon ECS
+    #   Resources][1] in the *Amazon Elastic Container Service Developer
+    #   Guide*.
+    #
+    #   Only tasks launched after the update will reflect the update. To
+    #   update the tags on all tasks, set `forceNewDeployment` to `true`, so
+    #   that Amazon ECS starts new tasks with the updated tags.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html
+    #   @return [Boolean]
+    #
+    # @!attribute [rw] load_balancers
+    #   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 a container definition.
+    #
+    #   When you add, update, or remove a load balancer configuration,
+    #   Amazon ECS starts new tasks with the updated Elastic Load Balancing
+    #   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
+    #   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
+    #   propagated.
+    #
+    #   Only tasks launched after the update will reflect the update. To
+    #   update the tags on all tasks, set `forceNewDeployment` to `true`, so
+    #   that Amazon ECS starts new tasks with the updated tags.
+    #   @return [String]
+    #
+    # @!attribute [rw] service_registries
+    #   The details for the service discovery registries to assign to this
+    #   service. For more information, see [Service Discovery][1].
+    #
+    #   When you add, update, or remove the service registries
+    #   configuration, Amazon ECS starts new tasks with the updated service
+    #   registries configuration, and then stops the old tasks when the new
+    #   tasks are running.
+    #
+    #   You can remove existing `serviceRegistries` by passing an empty
+    #   list.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html
+    #   @return [Array<Types::ServiceRegistry>]
+    #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/UpdateServiceRequest AWS API Documentation
     #
     class UpdateServiceRequest < Struct.new(
@@ -11984,7 +12176,11 @@ module Aws::ECS
       :platform_version,
       :force_new_deployment,
       :health_check_grace_period_seconds,
-      :enable_execute_command)
+      :enable_execute_command,
+      :enable_ecs_managed_tags,
+      :load_balancers,
+      :propagate_tags,
+      :service_registries)
       SENSITIVE = []
       include Aws::Structure
     end

data/lib/aws-sdk-ecs.rb

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

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-ecs
 version: !ruby/object:Gem::Version
-  version: 1.96.0
+  version: 1.99.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-02-24 00:00:00.000000000 Z
+date: 2022-03-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core