aws-sdk-ecs 1.151.0 → 1.154.0

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

@@ -125,8 +125,13 @@ module Aws::ECS
     end
 
     # You can apply up to 10 custom attributes for each resource. You can
-    # view the attributes of a resource with ListAttributes. You can remove
-    # existing attributes on a resource with DeleteAttributes.
+    # view the attributes of a resource with [ListAttributes][1]. You can
+    # remove existing attributes on a resource with [DeleteAttributes][2].
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListAttributes.html
+    # [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeleteAttributes.html
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/AttributeLimitExceededException AWS API Documentation
     #
@@ -237,12 +242,12 @@ module Aws::ECS
 
     # An object representing the networking details for a task or service.
     # For example
-    # `awsvpcConfiguration=\{subnets=["subnet-12344321"],securityGroups=["sg-12344321"]\}`
+    # `awsVpcConfiguration=\{subnets=["subnet-12344321"],securityGroups=["sg-12344321"]\}`.
     #
     # @!attribute [rw] subnets
     #   The IDs of the subnets associated with the task or service. There's
     #   a limit of 16 subnets that can be specified per
-    #   `AwsVpcConfiguration`.
+    #   `awsvpcConfiguration`.
     #
     #   <note markdown="1"> All specified subnets must be from the same VPC.
     #
@@ -253,7 +258,7 @@ module Aws::ECS
     #   The IDs of the security groups associated with the task or service.
     #   If you don't specify a security group, the default security group
     #   for the VPC is used. There's a limit of 5 security groups that can
-    #   be specified per `AwsVpcConfiguration`.
+    #   be specified per `awsvpcConfiguration`.
     #
     #   <note markdown="1"> All specified security groups must be from the same VPC.
     #
@@ -377,19 +382,19 @@ module Aws::ECS
     end
 
     # The details of a capacity provider strategy. A capacity provider
-    # strategy can be set when using the RunTask or CreateCluster APIs or as
-    # the default capacity provider strategy for a cluster with the
-    # CreateCluster API.
+    # strategy can be set when using the [RunTask][1]or [CreateCluster][2]
+    # APIs or as the default capacity provider strategy for a cluster with
+    # the `CreateCluster` API.
     #
     # Only capacity providers that are already associated with a cluster and
     # have an `ACTIVE` or `UPDATING` status can be used in a capacity
-    # provider strategy. The PutClusterCapacityProviders API is used to
+    # provider strategy. The [PutClusterCapacityProviders][3] API is used to
     # associate a capacity provider with a cluster.
     #
     # If specifying a capacity provider that uses an Auto Scaling group, the
     # capacity provider must already be created. New Auto Scaling group
-    # capacity providers can be created with the CreateCapacityProvider API
-    # operation.
+    # capacity providers can be created with the
+    # [CreateClusterCapacityProvider][4] API operation.
     #
     # To use a Fargate capacity provider, specify either the `FARGATE` or
     # `FARGATE_SPOT` capacity providers. The Fargate capacity providers are
@@ -406,6 +411,13 @@ module Aws::ECS
     # A capacity provider strategy may contain a maximum of 6 capacity
     # providers.
     #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_RunTask.html
+    # [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCluster.html
+    # [3]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html
+    # [4]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateClusterCapacityProvider.html
+    #
     # @!attribute [rw] capacity_provider
     #   The short name of the capacity provider.
     #   @return [String]
@@ -456,6 +468,19 @@ module Aws::ECS
     # have permissions to use the action or resource. Or, it might be
     # specifying an identifier that isn't valid.
     #
+    # The following list includes additional causes for the error:
+    #
+    # * The `RunTask` could not be processed because you use managed scaling
+    #   and there is a capacity error because the quota of tasks in the
+    #   `PROVISIONING` per cluster has been reached. For information about
+    #   the service quotas, see [Amazon ECS service quotas][1].
+    #
+    # ^
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html
+    #
     # @!attribute [rw] message
     #   Message that describes the cause of the exception.
     #   @return [String]
@@ -540,7 +565,11 @@ module Aws::ECS
     #
     # @!attribute [rw] active_services_count
     #   The number of services that are running on the cluster in an
-    #   `ACTIVE` state. You can view these services with ListServices.
+    #   `ACTIVE` state. You can view these services with [PListServices][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListServices.html
     #   @return [Integer]
     #
     # @!attribute [rw] statistics
@@ -702,7 +731,11 @@ module Aws::ECS
 
     # You can't delete a cluster that has registered container instances.
     # First, deregister the container instances before you can delete the
-    # cluster. For more information, see DeregisterContainerInstance.
+    # cluster. For more information, see [DeregisterContainerInstance][1].
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeregisterContainerInstance.html
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/ClusterContainsContainerInstancesException AWS API Documentation
     #
@@ -710,7 +743,13 @@ module Aws::ECS
 
     # You can't delete a cluster that contains services. First, update the
     # service to reduce its desired task count to 0, and then delete the
-    # service. For more information, see UpdateService and DeleteService.
+    # service. For more information, see [UpdateService][1] and
+    # [DeleteService][2].
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html
+    # [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeleteService.html
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/ClusterContainsServicesException AWS API Documentation
     #
@@ -723,7 +762,12 @@ module Aws::ECS
     class ClusterContainsTasksException < Aws::EmptyStructure; end
 
     # The specified cluster wasn't found. You can view your available
-    # clusters with ListClusters. Amazon ECS clusters are Region specific.
+    # clusters with [ListClusters][1]. Amazon ECS clusters are Region
+    # specific.
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListClusters.html
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/ClusterNotFoundException AWS API Documentation
     #
@@ -991,14 +1035,8 @@ module Aws::ECS
     #   entered in the `links` of another container to connect the
     #   containers. Up to 255 letters (uppercase and lowercase), numbers,
     #   underscores, and hyphens are allowed. This parameter maps to `name`
-    #   in the [Create a container][1] section of the [Docker Remote API][2]
-    #   and the `--name` option to [docker run][3].
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
+    #   in tthe docker conainer create command and the `--name` option to
+    #   docker run.
     #   @return [String]
     #
     # @!attribute [rw] image
@@ -1008,9 +1046,8 @@ module Aws::ECS
     #   repository-url/image:tag ` or ` repository-url/image@digest `. Up to
     #   255 letters (uppercase and lowercase), numbers, hyphens,
     #   underscores, colons, periods, forward slashes, and number signs are
-    #   allowed. This parameter maps to `Image` in the [Create a
-    #   container][1] section of the [Docker Remote API][2] and the `IMAGE`
-    #   parameter of [docker run][3].
+    #   allowed. This parameter maps to `Image` in the docker conainer
+    #   create command and the `IMAGE` parameter of docker run.
     #
     #   * When a new task starts, the Amazon ECS container agent pulls the
     #     latest version of the specified image and tag for the container to
@@ -1032,12 +1069,6 @@ module Aws::ECS
     #
     #   * Images in other online repositories are qualified further by a
     #     domain name (for example, `quay.io/assemblyline/ubuntu`).
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [String]
     #
     # @!attribute [rw] repository_credentials
@@ -1046,9 +1077,8 @@ module Aws::ECS
     #
     # @!attribute [rw] cpu
     #   The number of `cpu` units reserved for the container. This parameter
-    #   maps to `CpuShares` in the [Create a container][1] section of the
-    #   [Docker Remote API][2] and the `--cpu-shares` option to [docker
-    #   run][3].
+    #   maps to `CpuShares` in the docker conainer create commandand the
+    #   `--cpu-shares` option to docker run.
     #
     #   This field is optional for tasks using the Fargate launch type, and
     #   the only requirement is that the total amount of CPU reserved for
@@ -1057,7 +1087,7 @@ module Aws::ECS
     #
     #   <note markdown="1"> You can determine the number of CPU units that are available per EC2
     #   instance type by multiplying the vCPUs listed for that instance type
-    #   on the [Amazon EC2 Instances][4] detail page by 1,024.
+    #   on the [Amazon EC2 Instances][1] detail page by 1,024.
     #
     #    </note>
     #
@@ -1076,13 +1106,13 @@ module Aws::ECS
     #
     #   On Linux container instances, the Docker daemon on the container
     #   instance uses the CPU value to calculate the relative CPU share
-    #   ratios for running containers. For more information, see [CPU share
-    #   constraint][5] in the Docker documentation. The minimum valid CPU
-    #   share value that the Linux kernel allows is 2. However, the CPU
-    #   parameter isn't required, and you can use CPU values below 2 in
-    #   your container definitions. For CPU values below 2 (including null),
-    #   the behavior varies based on your Amazon ECS container agent
-    #   version:
+    #   ratios for running containers. The minimum valid CPU share value
+    #   that the Linux kernel allows is 2, and the maximum valid CPU share
+    #   value that the Linux kernel allows is 262144. However, the CPU
+    #   parameter isn't required, and you can use CPU values below 2 or
+    #   above 262144 in your container definitions. For CPU values below 2
+    #   (including null) or above 262144, the behavior varies based on your
+    #   Amazon ECS container agent version:
     #
     #   * **Agent versions less than or equal to 1.1.0:** Null and zero CPU
     #     values are passed to Docker as 0, which Docker then converts to
@@ -1092,6 +1122,10 @@ module Aws::ECS
     #   * **Agent versions greater than or equal to 1.2.0:** Null, zero, and
     #     CPU values of 1 are passed to Docker as 2.
     #
+    #   * **Agent versions greater than or equal to 1.84.0:** CPU values
+    #     greater than 256 vCPU are passed to Docker as 256, which is
+    #     equivalent to 262144 CPU shares.
+    #
     #   On Windows container instances, the CPU limit is enforced as an
     #   absolute limit, or a quota. Windows containers only have access to
     #   the specified amount of CPU that's described in the task
@@ -1100,11 +1134,7 @@ module Aws::ECS
     #
     #
     #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
-    #   [4]: http://aws.amazon.com/ec2/instance-types/
-    #   [5]: https://docs.docker.com/engine/reference/run/#cpu-share-constraint
+    #   [1]: http://aws.amazon.com/ec2/instance-types/
     #   @return [Integer]
     #
     # @!attribute [rw] memory
@@ -1112,9 +1142,9 @@ module Aws::ECS
     #   container attempts to exceed the memory specified here, the
     #   container is killed. The total amount of memory reserved for all
     #   containers within a task must be lower than the task `memory` value,
-    #   if one is specified. This parameter maps to `Memory` in the [Create
-    #   a container][1] section of the [Docker Remote API][2] and the
-    #   `--memory` option to [docker run][3].
+    #   if one is specified. This parameter maps to `Memory` in thethe
+    #   docker conainer create command and the `--memory` option to docker
+    #   run.
     #
     #   If using the Fargate launch type, this parameter is optional.
     #
@@ -1133,12 +1163,6 @@ module Aws::ECS
     #   The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB
     #   of memory for a container. So, don't specify less than 4 MiB of
     #   memory for your containers.
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Integer]
     #
     # @!attribute [rw] memory_reservation
@@ -1148,9 +1172,9 @@ module Aws::ECS
     #   consume more memory when it needs to, up to either the hard limit
     #   specified with the `memory` parameter (if applicable), or all of the
     #   available memory on the container instance, whichever comes first.
-    #   This parameter maps to `MemoryReservation` in the [Create a
-    #   container][1] section of the [Docker Remote API][2] and the
-    #   `--memory-reservation` option to [docker run][3].
+    #   This parameter maps to `MemoryReservation` in the the docker
+    #   conainer create command and the `--memory-reservation` option to
+    #   docker run.
     #
     #   If a task-level memory value is not specified, you must specify a
     #   non-zero integer for one or both of `memory` or `memoryReservation`
@@ -1175,12 +1199,6 @@ module Aws::ECS
     #   The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB
     #   of memory for a container. So, don't specify less than 4 MiB of
     #   memory for your containers.
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Integer]
     #
     # @!attribute [rw] links
@@ -1189,11 +1207,9 @@ module Aws::ECS
     #   supported if the network mode of a task definition is `bridge`. The
     #   `name:internalName` construct is analogous to `name:alias` in Docker
     #   links. Up to 255 letters (uppercase and lowercase), numbers,
-    #   underscores, and hyphens are allowed. For more information about
-    #   linking Docker containers, go to [Legacy container links][1] in the
-    #   Docker documentation. This parameter maps to `Links` in the [Create
-    #   a container][2] section of the [Docker Remote API][3] and the
-    #   `--link` option to [docker run][4].
+    #   underscores, and hyphens are allowed.. This parameter maps to
+    #   `Links` in the docker conainer create command and the `--link`
+    #   option to docker run.
     #
     #   <note markdown="1"> This parameter is not supported for Windows containers.
     #
@@ -1203,13 +1219,6 @@ module Aws::ECS
     #   able to communicate with each other without requiring links or host
     #   port mappings. Network isolation is achieved on the container
     #   instance using security groups and VPC settings.
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/network/links/
-    #   [2]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [3]: https://docs.docker.com/engine/api/v1.35/
-    #   [4]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Array<String>]
     #
     # @!attribute [rw] port_mappings
@@ -1226,27 +1235,24 @@ module Aws::ECS
     #   so you can't access a container's mapped port from the host
     #   itself.
     #
-    #   This parameter maps to `PortBindings` in the [Create a container][1]
-    #   section of the [Docker Remote API][2] and the `--publish` option to
-    #   [docker run][3]. If the network mode of a task definition is set to
-    #   `none`, then you can't specify port mappings. If the network mode
-    #   of a task definition is set to `host`, then host ports must either
-    #   be undefined or they must match the container port in the port
-    #   mapping.
+    #   This parameter maps to `PortBindings` in the the docker conainer
+    #   create command and the `--publish` option to docker run. If the
+    #   network mode of a task definition is set to `none`, then you can't
+    #   specify port mappings. If the network mode of a task definition is
+    #   set to `host`, then host ports must either be undefined or they must
+    #   match the container port in the port mapping.
     #
     #   <note markdown="1"> After a task reaches the `RUNNING` status, manual and automatic host
     #   and container port assignments are visible in the **Network
     #   Bindings** section of a container description for a selected task in
     #   the Amazon ECS console. The assignments are also visible in the
-    #   `networkBindings` section DescribeTasks responses.
+    #   `networkBindings` section [DescribeTasks][1] responses.
     #
     #    </note>
     #
     #
     #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeTasks.html
     #   @return [Array<Types::PortMapping>]
     #
     # @!attribute [rw] essential
@@ -1269,6 +1275,18 @@ module Aws::ECS
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/application_architecture.html
     #   @return [Boolean]
     #
+    # @!attribute [rw] restart_policy
+    #   The restart policy for a container. When you set up a restart
+    #   policy, Amazon ECS can restart the container without needing to
+    #   replace the task. For more information, see [Restart individual
+    #   containers in Amazon ECS tasks with container restart policies][1]
+    #   in the *Amazon Elastic Container Service Developer Guide*.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container-restart-policy.html
+    #   @return [Types::ContainerRestartPolicy]
+    #
     # @!attribute [rw] entry_point
     #   Early versions of the Amazon ECS container agent don't properly
     #   handle `entryPoint` parameters. If you have problems using
@@ -1276,62 +1294,35 @@ module Aws::ECS
     #   arguments as `command` array items instead.
     #
     #   The entry point that's passed to the container. This parameter maps
-    #   to `Entrypoint` in the [Create a container][1] section of the
-    #   [Docker Remote API][2] and the `--entrypoint` option to [docker
-    #   run][3]. For more information, see
-    #   [https://docs.docker.com/engine/reference/builder/#entrypoint][4].
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
-    #   [4]: https://docs.docker.com/engine/reference/builder/#entrypoint
+    #   to `Entrypoint` in tthe docker conainer create command and the
+    #   `--entrypoint` option to docker run.
     #   @return [Array<String>]
     #
     # @!attribute [rw] command
     #   The command that's passed to the container. This parameter maps to
-    #   `Cmd` in the [Create a container][1] section of the [Docker Remote
-    #   API][2] and the `COMMAND` parameter to [docker run][3]. For more
-    #   information, see
-    #   [https://docs.docker.com/engine/reference/builder/#cmd][4]. If there
-    #   are multiple arguments, each argument is a separated string in the
-    #   array.
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
-    #   [4]: https://docs.docker.com/engine/reference/builder/#cmd
+    #   `Cmd` in the docker conainer create command and the `COMMAND`
+    #   parameter to docker run. If there are multiple arguments, each
+    #   argument is a separated string in the array.
     #   @return [Array<String>]
     #
     # @!attribute [rw] environment
     #   The environment variables to pass to a container. This parameter
-    #   maps to `Env` in the [Create a container][1] section of the [Docker
-    #   Remote API][2] and the `--env` option to [docker run][3].
+    #   maps to `Env` in the docker conainer create command and the `--env`
+    #   option to docker run.
     #
     #   We don't recommend that you use plaintext environment variables for
     #   sensitive information, such as credential data.
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Array<Types::KeyValuePair>]
     #
     # @!attribute [rw] environment_files
     #   A list of files containing the environment variables to pass to a
-    #   container. This parameter maps to the `--env-file` option to [docker
-    #   run][1].
+    #   container. This parameter maps to the `--env-file` option to docker
+    #   run.
     #
     #   You can specify up to ten environment files. The file must have a
     #   `.env` file extension. Each line in an environment file contains an
     #   environment variable in `VARIABLE=VALUE` format. Lines beginning
-    #   with `#` are treated as comments and are ignored. For more
-    #   information about the environment variable file syntax, see [Declare
-    #   default environment variables in file][2].
+    #   with `#` are treated as comments and are ignored.
     #
     #   If there are environment variables specified using the `environment`
     #   parameter in a container definition, they take precedence over the
@@ -1339,54 +1330,43 @@ module Aws::ECS
     #   environment files are specified that contain the same variable,
     #   they're processed from the top down. We recommend that you use
     #   unique variable names. For more information, see [Specifying
-    #   Environment Variables][3] in the *Amazon Elastic Container Service
+    #   Environment Variables][1] in the *Amazon Elastic Container Service
     #   Developer Guide*.
     #
     #
     #
-    #   [1]: https://docs.docker.com/engine/reference/run/#security-configuration
-    #   [2]: https://docs.docker.com/compose/env-file/
-    #   [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/taskdef-envfiles.html
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/taskdef-envfiles.html
     #   @return [Array<Types::EnvironmentFile>]
     #
     # @!attribute [rw] mount_points
     #   The mount points for data volumes in your container.
     #
-    #   This parameter maps to `Volumes` in the [Create a container][1]
-    #   section of the [Docker Remote API][2] and the `--volume` option to
-    #   [docker run][3].
+    #   This parameter maps to `Volumes` in the the docker conainer create
+    #   command and the `--volume` option to docker run.
     #
     #   Windows containers can mount whole directories on the same drive as
     #   `$env:ProgramData`. Windows containers can't mount directories on a
     #   different drive, and mount point can't be across drives.
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Array<Types::MountPoint>]
     #
     # @!attribute [rw] volumes_from
     #   Data volumes to mount from another container. This parameter maps to
-    #   `VolumesFrom` in the [Create a container][1] section of the [Docker
-    #   Remote API][2] and the `--volumes-from` option to [docker run][3].
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
+    #   `VolumesFrom` in tthe docker conainer create command and the
+    #   `--volumes-from` option to docker run.
     #   @return [Array<Types::VolumeFrom>]
     #
     # @!attribute [rw] linux_parameters
     #   Linux-specific modifications that are applied to the container, such
     #   as Linux kernel capabilities. For more information see
-    #   KernelCapabilities.
+    #   [KernelCapabilities][1].
     #
     #   <note markdown="1"> This parameter is not supported for Windows containers.
     #
     #    </note>
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_KernelCapabilities.html
     #   @return [Types::LinuxParameters]
     #
     # @!attribute [rw] secrets
@@ -1469,7 +1449,7 @@ module Aws::ECS
     #   [Amazon ECS-optimized Linux AMI][2] in the *Amazon Elastic Container
     #   Service Developer Guide*.
     #
-    #   The valid values are 2-120 seconds.
+    #   The valid values for Fargate are 2-120 seconds.
     #
     #
     #
@@ -1521,25 +1501,19 @@ module Aws::ECS
     #
     # @!attribute [rw] hostname
     #   The hostname to use for your container. This parameter maps to
-    #   `Hostname` in the [Create a container][1] section of the [Docker
-    #   Remote API][2] and the `--hostname` option to [docker run][3].
+    #   `Hostname` in thethe docker conainer create command and the
+    #   `--hostname` option to docker run.
     #
     #   <note markdown="1"> The `hostname` parameter is not supported if you're using the
     #   `awsvpc` network mode.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [String]
     #
     # @!attribute [rw] user
     #   The user to use inside the container. This parameter maps to `User`
-    #   in the [Create a container][1] section of the [Docker Remote API][2]
-    #   and the `--user` option to [docker run][3].
+    #   in the docker conainer create command and the `--user` option to
+    #   docker run.
     #
     #   When running tasks using the `host` network mode, don't run
     #   containers using the root user (UID 0). We recommend using a
@@ -1563,135 +1537,83 @@ module Aws::ECS
     #   <note markdown="1"> This parameter is not supported for Windows containers.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [String]
     #
     # @!attribute [rw] working_directory
     #   The working directory to run commands inside the container in. This
-    #   parameter maps to `WorkingDir` in the [Create a container][1]
-    #   section of the [Docker Remote API][2] and the `--workdir` option to
-    #   [docker run][3].
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
+    #   parameter maps to `WorkingDir` in the docker conainer create command
+    #   and the `--workdir` option to docker run.
     #   @return [String]
     #
     # @!attribute [rw] disable_networking
     #   When this parameter is true, networking is off within the container.
-    #   This parameter maps to `NetworkDisabled` in the [Create a
-    #   container][1] section of the [Docker Remote API][2].
+    #   This parameter maps to `NetworkDisabled` in the docker conainer
+    #   create command.
     #
     #   <note markdown="1"> This parameter is not supported for Windows containers.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
     #   @return [Boolean]
     #
     # @!attribute [rw] privileged
     #   When this parameter is true, the container is given elevated
     #   privileges on the host container instance (similar to the `root`
-    #   user). This parameter maps to `Privileged` in the [Create a
-    #   container][1] section of the [Docker Remote API][2] and the
-    #   `--privileged` option to [docker run][3].
+    #   user). This parameter maps to `Privileged` in the the docker
+    #   conainer create command and the `--privileged` option to docker run
     #
     #   <note markdown="1"> This parameter is not supported for Windows containers or tasks run
     #   on Fargate.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Boolean]
     #
     # @!attribute [rw] readonly_root_filesystem
     #   When this parameter is true, the container is given read-only access
     #   to its root file system. This parameter maps to `ReadonlyRootfs` in
-    #   the [Create a container][1] section of the [Docker Remote API][2]
-    #   and the `--read-only` option to [docker run][3].
+    #   the docker conainer create command and the `--read-only` option to
+    #   docker run.
     #
     #   <note markdown="1"> This parameter is not supported for Windows containers.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Boolean]
     #
     # @!attribute [rw] dns_servers
     #   A list of DNS servers that are presented to the container. This
-    #   parameter maps to `Dns` in the [Create a container][1] section of
-    #   the [Docker Remote API][2] and the `--dns` option to [docker
-    #   run][3].
+    #   parameter maps to `Dns` in the the docker conainer create command
+    #   and the `--dns` option to docker run.
     #
     #   <note markdown="1"> This parameter is not supported for Windows containers.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Array<String>]
     #
     # @!attribute [rw] dns_search_domains
     #   A list of DNS search domains that are presented to the container.
-    #   This parameter maps to `DnsSearch` in the [Create a container][1]
-    #   section of the [Docker Remote API][2] and the `--dns-search` option
-    #   to [docker run][3].
+    #   This parameter maps to `DnsSearch` in the docker conainer create
+    #   command and the `--dns-search` option to docker run.
     #
     #   <note markdown="1"> This parameter is not supported for Windows containers.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Array<String>]
     #
     # @!attribute [rw] extra_hosts
     #   A list of hostnames and IP address mappings to append to the
     #   `/etc/hosts` file on the container. This parameter maps to
-    #   `ExtraHosts` in the [Create a container][1] section of the [Docker
-    #   Remote API][2] and the `--add-host` option to [docker run][3].
+    #   `ExtraHosts` in the docker conainer create command and the
+    #   `--add-host` option to docker run.
     #
     #   <note markdown="1"> This parameter isn't supported for Windows containers or tasks that
     #   use the `awsvpc` network mode.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Array<Types::HostEntry>]
     #
     # @!attribute [rw] docker_security_options
     #   A list of strings to provide custom configuration for multiple
-    #   security systems. For more information about valid values, see
-    #   [Docker Run Security Configuration][1]. This field isn't valid for
-    #   containers in tasks using the Fargate launch type.
+    #   security systems. This field isn't valid for containers in tasks
+    #   using the Fargate launch type.
     #
     #   For Linux tasks on EC2, this parameter can be used to reference
     #   custom labels for SELinux and AppArmor multi-level security systems.
@@ -1699,95 +1621,67 @@ module Aws::ECS
     #   For any tasks on EC2, this parameter can be used to reference a
     #   credential spec file that configures a container for Active
     #   Directory authentication. For more information, see [Using gMSAs for
-    #   Windows Containers][2] and [Using gMSAs for Linux Containers][3] in
+    #   Windows Containers][1] and [Using gMSAs for Linux Containers][2] in
     #   the *Amazon Elastic Container Service Developer Guide*.
     #
-    #   This parameter maps to `SecurityOpt` in the [Create a container][4]
-    #   section of the [Docker Remote API][5] and the `--security-opt`
-    #   option to [docker run][1].
+    #   This parameter maps to `SecurityOpt` in the docker conainer create
+    #   command and the `--security-opt` option to docker run.
     #
     #   <note markdown="1"> The Amazon ECS container agent running on a container instance must
     #   register with the `ECS_SELINUX_CAPABLE=true` or
     #   `ECS_APPARMOR_CAPABLE=true` environment variables before containers
     #   placed on that instance can use these security options. For more
-    #   information, see [Amazon ECS Container Agent Configuration][6] in
+    #   information, see [Amazon ECS Container Agent Configuration][3] in
     #   the *Amazon Elastic Container Service Developer Guide*.
     #
     #    </note>
     #
-    #   For more information about valid values, see [Docker Run Security
-    #   Configuration][1].
-    #
     #   Valid values: "no-new-privileges" \| "apparmor:PROFILE" \|
     #   "label:value" \| "credentialspec:CredentialSpecFilePath"
     #
     #
     #
-    #   [1]: https://docs.docker.com/engine/reference/run/#security-configuration
-    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/windows-gmsa.html
-    #   [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/linux-gmsa.html
-    #   [4]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [5]: https://docs.docker.com/engine/api/v1.35/
-    #   [6]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/windows-gmsa.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/linux-gmsa.html
+    #   [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html
     #   @return [Array<String>]
     #
     # @!attribute [rw] interactive
     #   When this parameter is `true`, you can deploy containerized
     #   applications that require `stdin` or a `tty` to be allocated. This
-    #   parameter maps to `OpenStdin` in the [Create a container][1] section
-    #   of the [Docker Remote API][2] and the `--interactive` option to
-    #   [docker run][3].
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
+    #   parameter maps to `OpenStdin` in the docker conainer create command
+    #   and the `--interactive` option to docker run.
     #   @return [Boolean]
     #
     # @!attribute [rw] pseudo_terminal
     #   When this parameter is `true`, a TTY is allocated. This parameter
-    #   maps to `Tty` in the [Create a container][1] section of the [Docker
-    #   Remote API][2] and the `--tty` option to [docker run][3].
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
+    #   maps to `Tty` in tthe docker conainer create command and the `--tty`
+    #   option to docker run.
     #   @return [Boolean]
     #
     # @!attribute [rw] docker_labels
     #   A key/value map of labels to add to the container. This parameter
-    #   maps to `Labels` in the [Create a container][1] section of the
-    #   [Docker Remote API][2] and the `--label` option to [docker run][3].
-    #   This parameter requires version 1.18 of the Docker Remote API or
-    #   greater on your container instance. To check the Docker Remote API
-    #   version on your container instance, log in to your container
-    #   instance and run the following command: `sudo docker version
-    #   --format '\{\{.Server.APIVersion\}\}'`
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
+    #   maps to `Labels` in the docker conainer create command and the
+    #   `--label` option to docker run. This parameter requires version 1.18
+    #   of the Docker Remote API or greater on your container instance. To
+    #   check the Docker Remote API version on your container instance, log
+    #   in to your container instance and run the following command: `sudo
+    #   docker version --format '\{\{.Server.APIVersion\}\}'`
     #   @return [Hash<String,String>]
     #
     # @!attribute [rw] ulimits
     #   A list of `ulimits` to set in the container. If a `ulimit` value is
     #   specified in a task definition, it overrides the default values set
-    #   by Docker. This parameter maps to `Ulimits` in the [Create a
-    #   container][1] section of the [Docker Remote API][2] and the
-    #   `--ulimit` option to [docker run][3]. Valid naming values are
-    #   displayed in the Ulimit data type.
+    #   by Docker. This parameter maps to `Ulimits` in tthe docker conainer
+    #   create command and the `--ulimit` option to docker run. Valid naming
+    #   values are displayed in the [Ulimit][1] data type.
     #
     #   Amazon ECS tasks hosted on Fargate use the default resource limit
     #   values set by the operating system with the exception of the
     #   `nofile` resource limit parameter which Fargate overrides. The
     #   `nofile` resource limit sets a restriction on the number of open
-    #   files that a container can use. The default `nofile` soft limit is
-    #   `1024` and the default hard limit is `65535`.
+    #   files that a container can use. The default `nofile` soft limit is `
+    #   65535` and the default hard limit is `65535`.
     #
     #   This parameter requires version 1.18 of the Docker Remote API or
     #   greater on your container instance. To check the Docker Remote API
@@ -1801,30 +1695,26 @@ module Aws::ECS
     #
     #
     #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_Ulimit.html
     #   @return [Array<Types::Ulimit>]
     #
     # @!attribute [rw] log_configuration
     #   The log configuration specification for the container.
     #
-    #   This parameter maps to `LogConfig` in the [Create a container][1]
-    #   section of the [Docker Remote API][2] and the `--log-driver` option
-    #   to [docker run][3]. By default, containers use the same logging
-    #   driver that the Docker daemon uses. However the container can use a
-    #   different logging driver than the Docker daemon by specifying a log
-    #   driver with this parameter in the container definition. To use a
-    #   different logging driver for a container, the log system must be
-    #   configured properly on the container instance (or on a different log
-    #   server for remote logging options). For more information about the
-    #   options for different supported log drivers, see [Configure logging
-    #   drivers][4] in the Docker documentation.
+    #   This parameter maps to `LogConfig` in the docker conainer create
+    #   command and the `--log-driver` option to docker run. By default,
+    #   containers use the same logging driver that the Docker daemon uses.
+    #   However the container can use a different logging driver than the
+    #   Docker daemon by specifying a log driver with this parameter in the
+    #   container definition. To use a different logging driver for a
+    #   container, the log system must be configured properly on the
+    #   container instance (or on a different log server for remote logging
+    #   options).
     #
     #   <note markdown="1"> Amazon ECS currently supports a subset of the logging drivers
-    #   available to the Docker daemon (shown in the LogConfiguration data
-    #   type). Additional log drivers may be available in future releases of
-    #   the Amazon ECS container agent.
+    #   available to the Docker daemon (shown in the [LogConfiguration][1]
+    #   data type). Additional log drivers may be available in future
+    #   releases of the Amazon ECS container agent.
     #
     #    </note>
     #
@@ -1839,46 +1729,30 @@ module Aws::ECS
     #   `ECS_AVAILABLE_LOGGING_DRIVERS` environment variable before
     #   containers placed on that instance can use these log configuration
     #   options. For more information, see [Amazon ECS Container Agent
-    #   Configuration][5] in the *Amazon Elastic Container Service Developer
+    #   Configuration][2] in the *Amazon Elastic Container Service Developer
     #   Guide*.
     #
     #    </note>
     #
     #
     #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
-    #   [4]: https://docs.docker.com/engine/admin/logging/overview/
-    #   [5]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_LogConfiguration.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html
     #   @return [Types::LogConfiguration]
     #
     # @!attribute [rw] health_check
     #   The container health check command and associated configuration
     #   parameters for the container. This parameter maps to `HealthCheck`
-    #   in the [Create a container][1] section of the [Docker Remote API][2]
-    #   and the `HEALTHCHECK` parameter of [docker run][3].
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
+    #   in the docker conainer create command and the `HEALTHCHECK`
+    #   parameter of docker run.
     #   @return [Types::HealthCheck]
     #
     # @!attribute [rw] system_controls
     #   A list of namespaced kernel parameters to set in the container. This
-    #   parameter maps to `Sysctls` in the [Create a container][1] section
-    #   of the [Docker Remote API][2] and the `--sysctl` option to [docker
-    #   run][3]. For example, you can configure
-    #   `net.ipv4.tcp_keepalive_time` setting to maintain longer lived
-    #   connections.
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
+    #   parameter maps to `Sysctls` in tthe docker conainer create command
+    #   and the `--sysctl` option to docker run. For example, you can
+    #   configure `net.ipv4.tcp_keepalive_time` setting to maintain longer
+    #   lived connections.
     #   @return [Array<Types::SystemControl>]
     #
     # @!attribute [rw] resource_requirements
@@ -1955,6 +1829,7 @@ module Aws::ECS
       :links,
       :port_mappings,
       :essential,
+      :restart_policy,
       :entry_point,
       :command,
       :environment,
@@ -2185,7 +2060,11 @@ module Aws::ECS
     # @!attribute [rw] attributes
     #   The attributes set for the container instance, either by the Amazon
     #   ECS container agent at instance registration or manually with the
-    #   PutAttributes operation.
+    #   [PutAttributes][1] operation.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutAttributes.html
     #   @return [Array<Types::Attribute>]
     #
     # @!attribute [rw] registered_at
@@ -2357,6 +2236,48 @@ module Aws::ECS
       include Aws::Structure
     end
 
+    # You can enable a restart policy for each container defined in your
+    # task definition, to overcome transient failures faster and maintain
+    # task availability. When you enable a restart policy for a container,
+    # Amazon ECS can restart the container if it exits, without needing to
+    # replace the task. For more information, see [Restart individual
+    # containers in Amazon ECS tasks with container restart policies][1] in
+    # the *Amazon Elastic Container Service Developer Guide*.
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container-restart-policy.html
+    #
+    # @!attribute [rw] enabled
+    #   Specifies whether a restart policy is enabled for the container.
+    #   @return [Boolean]
+    #
+    # @!attribute [rw] ignored_exit_codes
+    #   A list of exit codes that Amazon ECS will ignore and not attempt a
+    #   restart on. You can specify a maximum of 50 container exit codes. By
+    #   default, Amazon ECS does not ignore any exit codes.
+    #   @return [Array<Integer>]
+    #
+    # @!attribute [rw] restart_attempt_period
+    #   A period of time (in seconds) that the container must run for before
+    #   a restart can be attempted. A container can be restarted only once
+    #   every `restartAttemptPeriod` seconds. If a container isn't able to
+    #   run for this time period and exits early, it will not be restarted.
+    #   You can set a minimum `restartAttemptPeriod` of 60 seconds and a
+    #   maximum `restartAttemptPeriod` of 1800 seconds. By default, a
+    #   container must run for 300 seconds before it can be restarted.
+    #   @return [Integer]
+    #
+    # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/ContainerRestartPolicy AWS API Documentation
+    #
+    class ContainerRestartPolicy < Struct.new(
+      :enabled,
+      :ignored_exit_codes,
+      :restart_attempt_period)
+      SENSITIVE = []
+      include Aws::Structure
+    end
+
     # An object that represents a change in state for a container.
     #
     # @!attribute [rw] container_name
@@ -2508,7 +2429,12 @@ module Aws::ECS
     #   The setting to use when creating a cluster. This parameter is used
     #   to turn on CloudWatch Container Insights for a cluster. If this
     #   value is specified, it overrides the `containerInsights` value set
-    #   with PutAccountSetting or PutAccountSettingDefault.
+    #   with [PutAccountSetting][1] or [PutAccountSettingDefault][2].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutAccountSetting.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutAccountSettingDefault.html
     #   @return [Array<Types::ClusterSetting>]
     #
     # @!attribute [rw] configuration
@@ -2553,12 +2479,13 @@ module Aws::ECS
     #
     #   If a default capacity provider strategy isn't defined for a cluster
     #   when it was created, it can be defined later with the
-    #   PutClusterCapacityProviders API operation.
+    #   [PutClusterCapacityProviders][3] API operation.
     #
     #
     #
     #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html
     #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_RunTask.html
+    #   [3]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html
     #   @return [Array<Types::CapacityProviderStrategyItem>]
     #
     # @!attribute [rw] service_connect_defaults
@@ -3124,9 +3051,10 @@ module Aws::ECS
     #   A capacity provider strategy consists of one or more capacity
     #   providers along with the `base` and `weight` to assign to them. A
     #   capacity provider must be associated with the cluster to be used in
-    #   a capacity provider strategy. The PutClusterCapacityProviders API is
-    #   used to associate a capacity provider with a cluster. Only capacity
-    #   providers with an `ACTIVE` or `UPDATING` status can be used.
+    #   a capacity provider strategy. The [PutClusterCapacityProviders][1]
+    #   API is used to associate a capacity provider with a cluster. Only
+    #   capacity providers with an `ACTIVE` or `UPDATING` status can be
+    #   used.
     #
     #   If a `capacityProviderStrategy` is specified, the `launchType`
     #   parameter must be omitted. If no `capacityProviderStrategy` or
@@ -3135,17 +3063,22 @@ module Aws::ECS
     #
     #   If specifying a capacity provider that uses an Auto Scaling group,
     #   the capacity provider must already be created. New capacity
-    #   providers can be created with the CreateCapacityProvider API
-    #   operation.
+    #   providers can be created with the
+    #   [CreateCapacityProviderProvider][2]API operation.
     #
     #   To use a Fargate capacity provider, specify either the `FARGATE` or
     #   `FARGATE_SPOT` capacity providers. The Fargate capacity providers
     #   are available to all accounts and only need to be associated with a
     #   cluster to be used.
     #
-    #   The PutClusterCapacityProviders API operation is used to update the
-    #   list of available capacity providers for a cluster after the cluster
-    #   is created.
+    #   The [PutClusterCapacityProviders][1] API operation is used to update
+    #   the list of available capacity providers for a cluster after the
+    #   cluster is created.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCapacityProviderProvider.html
     #   @return [Array<Types::CapacityProviderStrategyItem>]
     #
     # @!attribute [rw] platform_version
@@ -3593,7 +3526,11 @@ module Aws::ECS
     #   state. If the service fails to reach a steady state and circuit
     #   breaker is turned on, the deployment transitions to a `FAILED`
     #   state. A deployment in `FAILED` state doesn't launch any new tasks.
-    #   For more information, see DeploymentCircuitBreaker.
+    #   For more information, see [DeploymentCircuitBreaker][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeploymentCircuitBreaker.html
     #   @return [String]
     #
     # @!attribute [rw] rollout_state_reason
@@ -3907,7 +3844,8 @@ module Aws::ECS
     #     The number of containers Amazon ECS adds or removes from the
     #     service during a rolling update is controlled by adjusting the
     #     minimum and maximum number of healthy tasks allowed during a
-    #     service deployment, as specified in the DeploymentConfiguration.
+    #     service deployment, as specified in the
+    #     [DeploymentConfiguration][1].
     #
     #   CODE\_DEPLOY
     #
@@ -3921,6 +3859,10 @@ module Aws::ECS
     #   : The external (`EXTERNAL`) deployment type enables you to use any
     #     third-party deployment controller for full control over the
     #     deployment process for an Amazon ECS service.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeploymentConfiguration.html
     #   @return [String]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/DeploymentController AWS API Documentation
@@ -4518,43 +4460,21 @@ module Aws::ECS
     #   placement. If the driver was installed using the Docker plugin CLI,
     #   use `docker plugin ls` to retrieve the driver name from your
     #   container instance. If the driver was installed using another
-    #   method, use Docker plugin discovery to retrieve the driver name. For
-    #   more information, see [Docker plugin discovery][1]. This parameter
-    #   maps to `Driver` in the [Create a volume][2] section of the [Docker
-    #   Remote API][3] and the `xxdriver` option to [docker volume
-    #   create][4].
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/extend/plugin_api/#plugin-discovery
-    #   [2]: https://docs.docker.com/engine/api/v1.35/#operation/VolumeCreate
-    #   [3]: https://docs.docker.com/engine/api/v1.35/
-    #   [4]: https://docs.docker.com/engine/reference/commandline/volume_create/
+    #   method, use Docker plugin discovery to retrieve the driver name.
+    #   This parameter maps to `Driver` in the docker conainer create
+    #   command and the `xxdriver` option to docker volume create.
     #   @return [String]
     #
     # @!attribute [rw] driver_opts
     #   A map of Docker driver-specific options passed through. This
-    #   parameter maps to `DriverOpts` in the [Create a volume][1] section
-    #   of the [Docker Remote API][2] and the `xxopt` option to [docker
-    #   volume create][3].
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/VolumeCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/commandline/volume_create/
+    #   parameter maps to `DriverOpts` in the docker create-volume command
+    #   and the `xxopt` option to docker volume create.
     #   @return [Hash<String,String>]
     #
     # @!attribute [rw] labels
     #   Custom metadata to add to your Docker volume. This parameter maps to
-    #   `Labels` in the [Create a volume][1] section of the [Docker Remote
-    #   API][2] and the `xxlabel` option to [docker volume create][3].
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/VolumeCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/commandline/volume_create/
+    #   `Labels` in the docker conainer create command and the `xxlabel`
+    #   option to docker volume create.
     #   @return [Hash<String,String>]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/DockerVolumeConfiguration AWS API Documentation
@@ -5151,7 +5071,7 @@ module Aws::ECS
     # parameters that are specified in a container definition override any
     # Docker health checks that exist in the container image (such as those
     # specified in a parent image or from the image's Dockerfile). This
-    # configuration maps to the `HEALTHCHECK` parameter of [docker run][1].
+    # configuration maps to the `HEALTHCHECK` parameter of docker run.
     #
     # <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
@@ -5250,20 +5170,19 @@ 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][2].
+    #   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][3].
+    #   [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.
     #
     #
     #
-    # [1]: https://docs.docker.com/engine/reference/run/
-    # [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html
-    # [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html
+    # [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html
     #
     # @!attribute [rw] command
     #   A string array representing the command that the container runs to
@@ -5283,13 +5202,8 @@ module Aws::ECS
     #   ` CMD-SHELL, curl -f http://localhost/ || exit 1`
     #
     #   An exit code of 0 indicates success, and non-zero exit code
-    #   indicates failure. For more information, see `HealthCheck` in the
-    #   [Create a container][1] section of the [Docker Remote API][2].
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
+    #   indicates failure. For more information, see `HealthCheck` in tthe
+    #   docker conainer create command
     #   @return [Array<String>]
     #
     # @!attribute [rw] interval
@@ -5337,7 +5251,11 @@ module Aws::ECS
 
     # Hostnames and IP address entries that are added to the `/etc/hosts`
     # file of a container via the `extraHosts` parameter of its
-    # ContainerDefinition.
+    # [ContainerDefinition][1].
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ContainerDefinition.html
     #
     # @!attribute [rw] hostname
     #   The hostname to use in the `/etc/hosts` entry.
@@ -5482,22 +5400,18 @@ module Aws::ECS
 
     # The Linux capabilities to add or remove from the default Docker
     # configuration for a container defined in the task definition. For more
-    # information about the default capabilities and the non-default
-    # available capabilities, see [Runtime privilege and Linux
-    # capabilities][1] in the *Docker run reference*. For more detailed
-    # information about these Linux capabilities, see the
-    # [capabilities(7)][2] Linux manual page.
+    # detailed information about these Linux capabilities, see the
+    # [capabilities(7)][1] Linux manual page.
     #
     #
     #
-    # [1]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
-    # [2]: http://man7.org/linux/man-pages/man7/capabilities.7.html
+    # [1]: http://man7.org/linux/man-pages/man7/capabilities.7.html
     #
     # @!attribute [rw] add
     #   The Linux capabilities for the container that have been added to the
     #   default configuration provided by Docker. This parameter maps to
-    #   `CapAdd` in the [Create a container][1] section of the [Docker
-    #   Remote API][2] and the `--cap-add` option to [docker run][3].
+    #   `CapAdd` in the docker conainer create command and the `--cap-add`
+    #   option to docker run.
     #
     #   <note markdown="1"> Tasks launched on Fargate only support adding the `SYS_PTRACE`
     #   kernel capability.
@@ -5513,19 +5427,13 @@ module Aws::ECS
     #   "SYS_BOOT" | "SYS_CHROOT" | "SYS_MODULE" | "SYS_NICE" | "SYS_PACCT"
     #   | "SYS_PTRACE" | "SYS_RAWIO" | "SYS_RESOURCE" | "SYS_TIME" |
     #   "SYS_TTY_CONFIG" | "SYSLOG" | "WAKE_ALARM"`
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Array<String>]
     #
     # @!attribute [rw] drop
     #   The Linux capabilities for the container that have been removed from
     #   the default configuration provided by Docker. This parameter maps to
-    #   `CapDrop` in the [Create a container][1] section of the [Docker
-    #   Remote API][2] and the `--cap-drop` option to [docker run][3].
+    #   `CapDrop` in the docker conainer create command and the `--cap-drop`
+    #   option to docker run.
     #
     #   Valid values: `"ALL" | "AUDIT_CONTROL" | "AUDIT_WRITE" |
     #   "BLOCK_SUSPEND" | "CHOWN" | "DAC_OVERRIDE" | "DAC_READ_SEARCH" |
@@ -5536,12 +5444,6 @@ module Aws::ECS
     #   "SYS_BOOT" | "SYS_CHROOT" | "SYS_MODULE" | "SYS_NICE" | "SYS_PACCT"
     #   | "SYS_PTRACE" | "SYS_RAWIO" | "SYS_RESOURCE" | "SYS_TIME" |
     #   "SYS_TTY_CONFIG" | "SYSLOG" | "WAKE_ALARM"`
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Array<String>]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/KernelCapabilities AWS API Documentation
@@ -5600,69 +5502,50 @@ module Aws::ECS
     #
     # @!attribute [rw] devices
     #   Any host devices to expose to the container. This parameter maps to
-    #   `Devices` in the [Create a container][1] section of the [Docker
-    #   Remote API][2] and the `--device` option to [docker run][3].
+    #   `Devices` in tthe docker conainer create command and the `--device`
+    #   option to docker run.
     #
     #   <note markdown="1"> If you're using tasks that use the Fargate launch type, the
     #   `devices` parameter isn't supported.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Array<Types::Device>]
     #
     # @!attribute [rw] init_process_enabled
     #   Run an `init` process inside the container that forwards signals and
     #   reaps processes. This parameter maps to the `--init` option to
-    #   [docker run][1]. This parameter requires version 1.25 of the Docker
+    #   docker run. This parameter requires version 1.25 of the Docker
     #   Remote API or greater on your container instance. To check the
     #   Docker Remote API version on your container instance, log in to your
     #   container instance and run the following command: `sudo docker
     #   version --format '\{\{.Server.APIVersion\}\}'`
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Boolean]
     #
     # @!attribute [rw] shared_memory_size
     #   The value for the size (in MiB) of the `/dev/shm` volume. This
-    #   parameter maps to the `--shm-size` option to [docker run][1].
+    #   parameter maps to the `--shm-size` option to docker run.
     #
     #   <note markdown="1"> If you are using tasks that use the Fargate launch type, the
     #   `sharedMemorySize` parameter is not supported.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Integer]
     #
     # @!attribute [rw] tmpfs
     #   The container path, mount options, and size (in MiB) of the tmpfs
-    #   mount. This parameter maps to the `--tmpfs` option to [docker
-    #   run][1].
+    #   mount. This parameter maps to the `--tmpfs` option to docker run.
     #
     #   <note markdown="1"> If you're using tasks that use the Fargate launch type, the `tmpfs`
     #   parameter isn't supported.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Array<Types::Tmpfs>]
     #
     # @!attribute [rw] max_swap
     #   The total amount of swap memory (in MiB) a container can use. This
-    #   parameter will be translated to the `--memory-swap` option to
-    #   [docker run][1] where the value would be the sum of the container
-    #   memory plus the `maxSwap` value.
+    #   parameter will be translated to the `--memory-swap` option to docker
+    #   run where the value would be the sum of the container memory plus
+    #   the `maxSwap` value.
     #
     #   If a `maxSwap` value of `0` is specified, the container will not use
     #   swap. Accepted values are `0` or any positive integer. If the
@@ -5678,10 +5561,6 @@ module Aws::ECS
     #   parameter isn't supported.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Integer]
     #
     # @!attribute [rw] swappiness
@@ -5692,8 +5571,7 @@ module Aws::ECS
     #   between `0` and `100`. If the `swappiness` parameter is not
     #   specified, a default value of `60` is used. If a value is not
     #   specified for `maxSwap` then this parameter is ignored. This
-    #   parameter maps to the `--memory-swappiness` option to [docker
-    #   run][1].
+    #   parameter maps to the `--memory-swappiness` option to docker run.
     #
     #   <note markdown="1"> If you're using tasks that use the Fargate launch type, the
     #   `swappiness` parameter isn't supported.
@@ -5702,10 +5580,6 @@ module Aws::ECS
     #   parameter isn't supported.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/reference/run/#security-configuration
     #   @return [Integer]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/LinuxParameters AWS API Documentation
@@ -5986,9 +5860,13 @@ module Aws::ECS
     #   Filters the container instances by status. For example, if you
     #   specify the `DRAINING` status, the results include only container
     #   instances that have been set to `DRAINING` using
-    #   UpdateContainerInstancesState. If you don't specify this parameter,
-    #   the default is to include container instances set to all states
-    #   other than `INACTIVE`.
+    #   [UpdateContainerInstancesState][1]. If you don't specify this
+    #   parameter, the default is to include container instances set to all
+    #   states other than `INACTIVE`.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateContainerInstancesState.html
     #   @return [String]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/ListContainerInstancesRequest AWS API Documentation
@@ -6555,15 +6433,13 @@ module Aws::ECS
     end
 
     # The log configuration for the container. This parameter maps to
-    # `LogConfig` in the [Create a container][1] section of the [Docker
-    # Remote API][2] and the `--log-driver` option to [ `docker run` ][3].
+    # `LogConfig` in the docker conainer create command and the
+    # `--log-driver` option to docker run.
     #
     # By default, containers use the same logging driver that the Docker
     # daemon uses. However, the container might use a different logging
     # driver than the Docker daemon by specifying a log driver configuration
-    # in the container definition. For more information about the options
-    # for different supported log drivers, see [Configure logging
-    # drivers][4] in the Docker documentation.
+    # in the container definition.
     #
     # Understand the following when specifying a log configuration for your
     # containers.
@@ -6576,8 +6452,8 @@ module Aws::ECS
     #   `splunk`, and `awsfirelens`.
     #
     #   For tasks hosted on Amazon EC2 instances, the supported log drivers
-    #   are `awslogs`, `fluentd`, `gelf`, `json-file`, `journald`,
-    #   `logentries`,`syslog`, `splunk`, and `awsfirelens`.
+    #   are `awslogs`, `fluentd`, `gelf`, `json-file`, `journald`,`syslog`,
+    #   `splunk`, and `awsfirelens`.
     #
     # * This parameter requires version 1.18 of the Docker Remote API or
     #   greater on your container instance.
@@ -6587,7 +6463,7 @@ module Aws::ECS
     #   `ECS_AVAILABLE_LOGGING_DRIVERS` environment variable before
     #   containers placed on that instance can use these log configuration
     #   options. For more information, see [Amazon ECS container agent
-    #   configuration][5] in the *Amazon Elastic Container Service Developer
+    #   configuration][1] in the *Amazon Elastic Container Service Developer
     #   Guide*.
     #
     # * For tasks that are on Fargate, because you don't have access to the
@@ -6598,11 +6474,7 @@ module Aws::ECS
     #
     #
     #
-    # [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    # [2]: https://docs.docker.com/engine/api/v1.35/
-    # [3]: https://docs.docker.com/engine/reference/commandline/run/
-    # [4]: https://docs.docker.com/engine/admin/logging/overview/
-    # [5]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html
     #
     # @!attribute [rw] log_driver
     #   The log driver to use for the container.
@@ -6611,16 +6483,16 @@ module Aws::ECS
     #   `splunk`, and `awsfirelens`.
     #
     #   For tasks hosted on Amazon EC2 instances, the supported log drivers
-    #   are `awslogs`, `fluentd`, `gelf`, `json-file`, `journald`,
-    #   `logentries`,`syslog`, `splunk`, and `awsfirelens`.
+    #   are `awslogs`, `fluentd`, `gelf`, `json-file`, `journald`, `syslog`,
+    #   `splunk`, and `awsfirelens`.
     #
-    #   For more information about using the `awslogs` log driver, see
-    #   [Using the awslogs log driver][1] in the *Amazon Elastic Container
+    #   For more information about using the `awslogs` log driver, see [Send
+    #   Amazon ECS logs to CloudWatch][1] in the *Amazon Elastic Container
     #   Service Developer Guide*.
     #
     #   For more information about using the `awsfirelens` log driver, see
-    #   [Custom log routing][2] in the *Amazon Elastic Container Service
-    #   Developer Guide*.
+    #   [Send Amazon ECS logs to an Amazon Web Services service or Amazon
+    #   Web Services Partner][2].
     #
     #   <note markdown="1"> If you have a custom driver that isn't listed, you can fork the
     #   Amazon ECS container agent project that's [available on GitHub][3]
@@ -6777,9 +6649,8 @@ module Aws::ECS
     #
     # @!attribute [rw] maximum_scaling_step_size
     #   The maximum number of Amazon EC2 instances that Amazon ECS will
-    #   scale out at one time. The scale in process is not affected by this
-    #   parameter. If this parameter is omitted, the default value of
-    #   `10000` is used.
+    #   scale out at one time. If this parameter is omitted, the default
+    #   value of `10000` is used.
     #   @return [Integer]
     #
     # @!attribute [rw] instance_warmup_period
@@ -6869,7 +6740,11 @@ module Aws::ECS
     # Details on the network bindings between a container and its host
     # container instance. After a task reaches the `RUNNING` status, manual
     # and automatic host and container port assignments are visible in the
-    # `networkBindings` section of DescribeTasks API responses.
+    # `networkBindings` section of [DescribeTasks][1] API responses.
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeTasks.html
     #
     # @!attribute [rw] bind_ip
     #   The IP address that the container is bound to on the container
@@ -7147,11 +7022,10 @@ module Aws::ECS
     # can be left blank or it must be the same value as the `containerPort`.
     #
     # Most fields of this parameter (`containerPort`, `hostPort`,
-    # `protocol`) maps to `PortBindings` in the [Create a container][1]
-    # section of the [Docker Remote API][2] and the `--publish` option to [
-    # `docker run` ][3]. If the network mode of a task definition is set to
-    # `host`, host ports must either be undefined or match the container
-    # port in the port mapping.
+    # `protocol`) maps to `PortBindings` in the docker conainer create
+    # command and the `--publish` option to `docker run`. If the network
+    # mode of a task definition is set to `host`, host ports must either be
+    # undefined or match the container port in the port mapping.
     #
     # <note markdown="1"> You can't expose the same container port for multiple protocols. If
     # you attempt this, an error is returned.
@@ -7160,13 +7034,11 @@ module Aws::ECS
     #
     # After a task reaches the `RUNNING` status, manual and automatic host
     # and container port assignments are visible in the `networkBindings`
-    # section of DescribeTasks API responses.
+    # section of [DescribeTasks][1] API responses.
     #
     #
     #
-    # [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    # [2]: https://docs.docker.com/engine/api/v1.35/
-    # [3]: https://docs.docker.com/engine/reference/commandline/run/
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeTasks.html
     #
     # @!attribute [rw] container_port
     #   The port number on the container that's bound to the user-specified
@@ -7363,8 +7235,13 @@ module Aws::ECS
     end
 
     # An object representing the protection status details for a task. You
-    # can set the protection status with the UpdateTaskProtection API and
-    # get the status of tasks with the GetTaskProtection API.
+    # can set the protection status with the [UpdateTaskProtection][1] API
+    # and get the status of tasks with the [GetTaskProtection][2] API.
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateTaskProtection.html
+    # [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_GetTaskProtection.html
     #
     # @!attribute [rw] task_arn
     #   The task ARN.
@@ -7784,13 +7661,17 @@ module Aws::ECS
     #
     #   If specifying a capacity provider that uses an Auto Scaling group,
     #   the capacity provider must already be created. New capacity
-    #   providers can be created with the CreateCapacityProvider API
+    #   providers can be created with the [CreateCapacityProvider][1] API
     #   operation.
     #
     #   To use a Fargate capacity provider, specify either the `FARGATE` or
     #   `FARGATE_SPOT` capacity providers. The Fargate capacity providers
     #   are available to all accounts and only need to be associated with a
     #   cluster to be used.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCapacityProvider.html
     #   @return [Array<String>]
     #
     # @!attribute [rw] default_capacity_provider_strategy
@@ -7803,19 +7684,25 @@ module Aws::ECS
     #   A capacity provider strategy consists of one or more capacity
     #   providers along with the `base` and `weight` to assign to them. A
     #   capacity provider must be associated with the cluster to be used in
-    #   a capacity provider strategy. The PutClusterCapacityProviders API is
-    #   used to associate a capacity provider with a cluster. Only capacity
-    #   providers with an `ACTIVE` or `UPDATING` status can be used.
+    #   a capacity provider strategy. The [PutClusterCapacityProviders][1]
+    #   API is used to associate a capacity provider with a cluster. Only
+    #   capacity providers with an `ACTIVE` or `UPDATING` status can be
+    #   used.
     #
     #   If specifying a capacity provider that uses an Auto Scaling group,
     #   the capacity provider must already be created. New capacity
-    #   providers can be created with the CreateCapacityProvider API
+    #   providers can be created with the [CreateCapacityProvider][2] API
     #   operation.
     #
     #   To use a Fargate capacity provider, specify either the `FARGATE` or
     #   `FARGATE_SPOT` capacity providers. The Fargate capacity providers
     #   are available to all accounts and only need to be associated with a
     #   cluster to be used.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCapacityProvider.html
     #   @return [Array<Types::CapacityProviderStrategyItem>]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/PutClusterCapacityProvidersRequest AWS API Documentation
@@ -7965,14 +7852,13 @@ module Aws::ECS
     # @!attribute [rw] execution_role_arn
     #   The Amazon Resource Name (ARN) of the task execution role that
     #   grants the Amazon ECS container agent permission to make Amazon Web
-    #   Services API calls on your behalf. The task execution IAM role is
-    #   required depending on the requirements of your task. For more
-    #   information, see [Amazon ECS task execution IAM role][1] in the
+    #   Services API calls on your behalf. For informationabout the required
+    #   IAM roles for Amazon ECS, see [IAM roles for Amazon ECS][1] in the
     #   *Amazon Elastic Container Service Developer Guide*.
     #
     #
     #
-    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_execution_IAM_role.html
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/security-ecs-iam-role-overview.html
     #   @return [String]
     #
     # @!attribute [rw] network_mode
@@ -8002,22 +7888,19 @@ module Aws::ECS
     #   non-root user.
     #
     #   If the network mode is `awsvpc`, the task is allocated an elastic
-    #   network interface, and you must specify a NetworkConfiguration value
-    #   when you create a service or run a task with the task definition.
-    #   For more information, see [Task Networking][1] in the *Amazon
-    #   Elastic Container Service Developer Guide*.
+    #   network interface, and you must specify a [NetworkConfiguration][1]
+    #   value when you create a service or run a task with the task
+    #   definition. For more information, see [Task Networking][2] in the
+    #   *Amazon Elastic Container Service Developer Guide*.
     #
     #   If the network mode is `host`, you cannot run multiple
     #   instantiations of the same task on a single container instance when
     #   port mappings are used.
     #
-    #   For more information, see [Network settings][2] in the *Docker run
-    #   reference*.
-    #
     #
     #
-    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html
-    #   [2]: https://docs.docker.com/engine/reference/run/#network-settings
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_NetworkConfiguration.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html
     #   @return [String]
     #
     # @!attribute [rw] container_definitions
@@ -8190,12 +8073,10 @@ module Aws::ECS
     #   share the same process namespace.
     #
     #   If no value is specified, the default is a private namespace for
-    #   each container. For more information, see [PID settings][1] in the
-    #   *Docker run reference*.
+    #   each container.
     #
     #   If the `host` PID mode is used, there's a heightened risk of
-    #   undesired process namespace exposure. For more information, see
-    #   [Docker security][2].
+    #   undesired process namespace exposure.
     #
     #   <note markdown="1"> This parameter is not supported for Windows containers.
     #
@@ -8206,11 +8087,6 @@ module Aws::ECS
     #   (Linux). This isn't supported for Windows containers on Fargate.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/reference/run/#pid-settings---pid
-    #   [2]: https://docs.docker.com/engine/security/security/
     #   @return [String]
     #
     # @!attribute [rw] ipc_mode
@@ -8224,17 +8100,15 @@ module Aws::ECS
     #   containers of a task are private and not shared with other
     #   containers in a task or on the container instance. If no value is
     #   specified, then the IPC resource namespace sharing depends on the
-    #   Docker daemon setting on the container instance. For more
-    #   information, see [IPC settings][1] in the *Docker run reference*.
+    #   Docker daemon setting on the container instance.
     #
     #   If the `host` IPC mode is used, be aware that there is a heightened
-    #   risk of undesired IPC namespace expose. For more information, see
-    #   [Docker security][2].
+    #   risk of undesired IPC namespace expose.
     #
     #   If you are setting namespaced kernel parameters using
     #   `systemControls` for the containers in the task, the following will
     #   apply to your IPC resource namespace. For more information, see
-    #   [System Controls][3] in the *Amazon Elastic Container Service
+    #   [System Controls][1] in the *Amazon Elastic Container Service
     #   Developer Guide*.
     #
     #   * For tasks that use the `host` IPC mode, IPC namespace related
@@ -8250,9 +8124,7 @@ module Aws::ECS
     #
     #
     #
-    #   [1]: https://docs.docker.com/engine/reference/run/#ipc-settings---ipc
-    #   [2]: https://docs.docker.com/engine/security/security/
-    #   [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html
     #   @return [String]
     #
     # @!attribute [rw] proxy_configuration
@@ -8603,12 +8475,17 @@ module Aws::ECS
     #   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.
+    #   tags to a task after task creation, use the[TagResource][1] API
+    #   action.
     #
     #   <note markdown="1"> An error will be received if you specify the `SERVICE` option when
     #   running a task.
     #
     #    </note>
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_TagResource.html
     #   @return [String]
     #
     # @!attribute [rw] reference_id
@@ -8621,12 +8498,17 @@ module Aws::ECS
     #   you automatically trigger a task to run a batch process job, you
     #   could apply a unique identifier for that job to your task with the
     #   `startedBy` parameter. You can then identify which tasks belong to
-    #   that job by filtering the results of a ListTasks call with the
+    #   that job by filtering the results of a [ListTasks][1] call with the
     #   `startedBy` value. Up to 128 letters (uppercase and lowercase),
-    #   numbers, hyphens (-), and underscores (\_) are allowed.
+    #   numbers, hyphens (-), forward slash (/), and underscores (\_) are
+    #   allowed.
     #
     #   If a task is started by an Amazon ECS service, then the `startedBy`
     #   parameter contains the deployment ID of the service that starts it.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListTasks.html
     #   @return [String]
     #
     # @!attribute [rw] tags
@@ -8934,8 +8816,13 @@ module Aws::ECS
     # @!attribute [rw] desired_count
     #   The desired number of instantiations of the task definition to keep
     #   running on the service. This value is specified when the service is
-    #   created with CreateService, and it can be modified with
-    #   UpdateService.
+    #   created with [CreateService][1] , and it can be modified with
+    #   [UpdateService][2].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html
     #   @return [Integer]
     #
     # @!attribute [rw] running_count
@@ -8981,8 +8868,13 @@ module Aws::ECS
     #
     # @!attribute [rw] task_definition
     #   The task definition to use for tasks in the service. This value is
-    #   specified when the service is created with CreateService, and it can
-    #   be modified with UpdateService.
+    #   specified when the service is created with [CreateService][1], and
+    #   it can be modified with [UpdateService][2].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html
     #   @return [String]
     #
     # @!attribute [rw] deployment_configuration
@@ -9283,15 +9175,13 @@ module Aws::ECS
     #
     # @!attribute [rw] log_configuration
     #   The log configuration for the container. This parameter maps to
-    #   `LogConfig` in the [Create a container][1] section of the [Docker
-    #   Remote API][2] and the `--log-driver` option to [ `docker run` ][3].
+    #   `LogConfig` in the docker conainer create command and the
+    #   `--log-driver` option to docker run.
     #
     #   By default, containers use the same logging driver that the Docker
     #   daemon uses. However, the container might use a different logging
     #   driver than the Docker daemon by specifying a log driver
-    #   configuration in the container definition. For more information
-    #   about the options for different supported log drivers, see
-    #   [Configure logging drivers][4] in the Docker documentation.
+    #   configuration in the container definition.
     #
     #   Understand the following when specifying a log configuration for
     #   your containers.
@@ -9304,8 +9194,8 @@ module Aws::ECS
     #     `splunk`, and `awsfirelens`.
     #
     #     For tasks hosted on Amazon EC2 instances, the supported log
-    #     drivers are `awslogs`, `fluentd`, `gelf`, `json-file`, `journald`,
-    #     `logentries`,`syslog`, `splunk`, and `awsfirelens`.
+    #     drivers are `awslogs`, `fluentd`, `gelf`, `json-file`,
+    #     `journald`,`syslog`, `splunk`, and `awsfirelens`.
     #
     #   * This parameter requires version 1.18 of the Docker Remote API or
     #     greater on your container instance.
@@ -9315,7 +9205,7 @@ module Aws::ECS
     #     the `ECS_AVAILABLE_LOGGING_DRIVERS` environment variable before
     #     containers placed on that instance can use these log configuration
     #     options. For more information, see [Amazon ECS container agent
-    #     configuration][5] in the *Amazon Elastic Container Service
+    #     configuration][1] in the *Amazon Elastic Container Service
     #     Developer Guide*.
     #
     #   * For tasks that are on Fargate, because you don't have access to
@@ -9326,11 +9216,7 @@ module Aws::ECS
     #
     #
     #
-    #   [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    #   [2]: https://docs.docker.com/engine/api/v1.35/
-    #   [3]: https://docs.docker.com/engine/reference/commandline/run/
-    #   [4]: https://docs.docker.com/engine/admin/logging/overview/
-    #   [5]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html
     #   @return [Types::LogConfiguration]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/ServiceConnectConfiguration AWS API Documentation
@@ -9723,15 +9609,23 @@ module Aws::ECS
 
     # The specified service isn't active. You can't update a service
     # that's inactive. If you have previously deleted a service, you can
-    # re-create it with CreateService.
+    # re-create it with [CreateService][1].
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/ServiceNotActiveException AWS API Documentation
     #
     class ServiceNotActiveException < Aws::EmptyStructure; end
 
     # The specified service wasn't found. You can view your available
-    # services with ListServices. Amazon ECS services are cluster specific
-    # and Region specific.
+    # services with [ListServices][1]. Amazon ECS services are cluster
+    # specific and Region specific.
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListServices.html
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/ServiceNotFoundException AWS API Documentation
     #
@@ -9958,12 +9852,17 @@ module Aws::ECS
     #   you automatically trigger a task to run a batch process job, you
     #   could apply a unique identifier for that job to your task with the
     #   `startedBy` parameter. You can then identify which tasks belong to
-    #   that job by filtering the results of a ListTasks call with the
+    #   that job by filtering the results of a [ListTasks][1] call with the
     #   `startedBy` value. Up to 36 letters (uppercase and lowercase),
-    #   numbers, hyphens (-), and underscores (\_) are allowed.
+    #   numbers, hyphens (-), forward slash (/), and underscores (\_) are
+    #   allowed.
     #
     #   If a task is started by an Amazon ECS service, the `startedBy`
     #   parameter contains the deployment ID of the service that starts it.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListTasks.html
     #   @return [String]
     #
     # @!attribute [rw] tags
@@ -10066,7 +9965,12 @@ module Aws::ECS
     #   An optional message specified when a task is stopped. For example,
     #   if you're using a custom scheduler, you can use this parameter to
     #   specify the reason for stopping the task here, and the message
-    #   appears in subsequent DescribeTasks API operations on this task.
+    #   appears in subsequent [DescribeTasks][1]&gt; API operations on this
+    #   task.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeTasks.html
     #   @return [String]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/StopTaskRequest AWS API Documentation
@@ -10254,10 +10158,10 @@ module Aws::ECS
     end
 
     # A list of namespaced kernel parameters to set in the container. This
-    # parameter maps to `Sysctls` in the [Create a container][1] section of
-    # the [Docker Remote API][2] and the `--sysctl` option to [docker
-    # run][3]. For example, you can configure `net.ipv4.tcp_keepalive_time`
-    # setting to maintain longer lived connections.
+    # parameter maps to `Sysctls` in tthe docker conainer create command and
+    # the `--sysctl` option to docker run. For example, you can configure
+    # `net.ipv4.tcp_keepalive_time` setting to maintain longer lived
+    # connections.
     #
     # We don't recommend that you specify network-related `systemControls`
     # parameters for multiple containers in a single task that also uses
@@ -10275,7 +10179,7 @@ module Aws::ECS
     #
     # If you're setting an IPC resource namespace to use for the containers
     # in the task, the following conditions apply to your system controls.
-    # For more information, see [IPC mode][4].
+    # For more information, see [IPC mode][1].
     #
     # * For tasks that use the `host` IPC mode, IPC namespace
     #   `systemControls` aren't supported.
@@ -10295,10 +10199,7 @@ module Aws::ECS
     #
     #
     #
-    # [1]: https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate
-    # [2]: https://docs.docker.com/engine/api/v1.35/
-    # [3]: https://docs.docker.com/engine/reference/run/#security-configuration
-    # [4]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#task_definition_ipcmode
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#task_definition_ipcmode
     #
     # @!attribute [rw] namespace
     #   The namespaced kernel parameter to set a `value` for.
@@ -10448,8 +10349,12 @@ module Aws::ECS
     class TargetNotConnectedException < Aws::EmptyStructure; end
 
     # The specified target wasn't found. You can view your available
-    # container instances with ListContainerInstances. Amazon ECS container
-    # instances are cluster-specific and Region-specific.
+    # container instances with [ListContainerInstances][1]. Amazon ECS
+    # container instances are cluster-specific and Region-specific.
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListContainerInstances.html
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/TargetNotFoundException AWS API Documentation
     #
@@ -10861,33 +10766,26 @@ module Aws::ECS
     # @!attribute [rw] task_role_arn
     #   The short name or full Amazon Resource Name (ARN) of the Identity
     #   and Access Management role that grants containers in the task
-    #   permission to call Amazon Web Services APIs on your behalf. For more
-    #   information, see [Amazon ECS Task Role][1] in the *Amazon Elastic
-    #   Container Service Developer Guide*.
-    #
-    #   IAM roles for tasks on Windows require that the `-EnableTaskIAMRole`
-    #   option is set when you launch the Amazon ECS-optimized Windows AMI.
-    #   Your containers must also run some configuration code to use the
-    #   feature. For more information, see [Windows IAM roles for tasks][2]
-    #   in the *Amazon Elastic Container Service Developer Guide*.
+    #   permission to call Amazon Web Services APIs on your behalf. For
+    #   informationabout the required IAM roles for Amazon ECS, see [IAM
+    #   roles for Amazon ECS][1] in the *Amazon Elastic Container Service
+    #   Developer Guide*.
     #
     #
     #
-    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html
-    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/windows_task_IAM_roles.html
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/security-ecs-iam-role-overview.html
     #   @return [String]
     #
     # @!attribute [rw] execution_role_arn
     #   The Amazon Resource Name (ARN) of the task execution role that
     #   grants the Amazon ECS container agent permission to make Amazon Web
-    #   Services API calls on your behalf. The task execution IAM role is
-    #   required depending on the requirements of your task. For more
-    #   information, see [Amazon ECS task execution IAM role][1] in the
+    #   Services API calls on your behalf. For informationabout the required
+    #   IAM roles for Amazon ECS, see [IAM roles for Amazon ECS][1] in the
     #   *Amazon Elastic Container Service Developer Guide*.
     #
     #
     #
-    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_execution_IAM_role.html
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/security-ecs-iam-role-overview.html
     #   @return [String]
     #
     # @!attribute [rw] network_mode
@@ -10917,22 +10815,19 @@ module Aws::ECS
     #   non-root user.
     #
     #   If the network mode is `awsvpc`, the task is allocated an elastic
-    #   network interface, and you must specify a NetworkConfiguration value
-    #   when you create a service or run a task with the task definition.
-    #   For more information, see [Task Networking][1] in the *Amazon
-    #   Elastic Container Service Developer Guide*.
+    #   network interface, and you must specify a [NetworkConfiguration][1]
+    #   value when you create a service or run a task with the task
+    #   definition. For more information, see [Task Networking][2] in the
+    #   *Amazon Elastic Container Service Developer Guide*.
     #
     #   If the network mode is `host`, you cannot run multiple
     #   instantiations of the same task on a single container instance when
     #   port mappings are used.
     #
-    #   For more information, see [Network settings][2] in the *Docker run
-    #   reference*.
-    #
     #
     #
-    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html
-    #   [2]: https://docs.docker.com/engine/reference/run/#network-settings
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_NetworkConfiguration.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html
     #   @return [String]
     #
     # @!attribute [rw] revision
@@ -10968,10 +10863,11 @@ module Aws::ECS
     #   Amazon EC2 instance is registered to your cluster, the Amazon ECS
     #   container agent assigns some standard attributes to the instance.
     #   You can apply custom attributes. These are specified as key-value
-    #   pairs using the Amazon ECS console or the PutAttributes API. These
-    #   attributes are used when determining task placement for tasks hosted
-    #   on Amazon EC2 instances. For more information, see [Attributes][1]
-    #   in the *Amazon Elastic Container Service Developer Guide*.
+    #   pairs using the Amazon ECS console or the [PutAttributes][1] API.
+    #   These attributes are used when determining task placement for tasks
+    #   hosted on Amazon EC2 instances. For more information, see
+    #   [Attributes][2] in the *Amazon Elastic Container Service Developer
+    #   Guide*.
     #
     #   <note markdown="1"> This parameter isn't supported for tasks run on Fargate.
     #
@@ -10979,7 +10875,8 @@ module Aws::ECS
     #
     #
     #
-    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html#attributes
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutAttributes.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html#attributes
     #   @return [Array<Types::Attribute>]
     #
     # @!attribute [rw] placement_constraints
@@ -11028,6 +10925,10 @@ module Aws::ECS
     #   one of the following values. The value that you choose determines
     #   your range of valid values for the `memory` parameter.
     #
+    #   If you use the EC2 launch type, this field is optional. Supported
+    #   values are between `128` CPU units (`0.125` vCPUs) and `10240` CPU
+    #   units (`10` vCPUs).
+    #
     #   The CPU units cannot be less than 1 vCPU when you use Windows
     #   containers on Fargate.
     #
@@ -11121,12 +11022,10 @@ module Aws::ECS
     #   share the same process namespace.
     #
     #   If no value is specified, the default is a private namespace for
-    #   each container. For more information, see [PID settings][1] in the
-    #   *Docker run reference*.
+    #   each container.
     #
     #   If the `host` PID mode is used, there's a heightened risk of
-    #   undesired process namespace exposure. For more information, see
-    #   [Docker security][2].
+    #   undesired process namespace exposure.
     #
     #   <note markdown="1"> This parameter is not supported for Windows containers.
     #
@@ -11137,11 +11036,6 @@ module Aws::ECS
     #   (Linux). This isn't supported for Windows containers on Fargate.
     #
     #    </note>
-    #
-    #
-    #
-    #   [1]: https://docs.docker.com/engine/reference/run/#pid-settings---pid
-    #   [2]: https://docs.docker.com/engine/security/security/
     #   @return [String]
     #
     # @!attribute [rw] ipc_mode
@@ -11155,17 +11049,15 @@ module Aws::ECS
     #   containers of a task are private and not shared with other
     #   containers in a task or on the container instance. If no value is
     #   specified, then the IPC resource namespace sharing depends on the
-    #   Docker daemon setting on the container instance. For more
-    #   information, see [IPC settings][1] in the *Docker run reference*.
+    #   Docker daemon setting on the container instance.
     #
     #   If the `host` IPC mode is used, be aware that there is a heightened
-    #   risk of undesired IPC namespace expose. For more information, see
-    #   [Docker security][2].
+    #   risk of undesired IPC namespace expose.
     #
     #   If you are setting namespaced kernel parameters using
     #   `systemControls` for the containers in the task, the following will
     #   apply to your IPC resource namespace. For more information, see
-    #   [System Controls][3] in the *Amazon Elastic Container Service
+    #   [System Controls][1] in the *Amazon Elastic Container Service
     #   Developer Guide*.
     #
     #   * For tasks that use the `host` IPC mode, IPC namespace related
@@ -11181,9 +11073,7 @@ module Aws::ECS
     #
     #
     #
-    #   [1]: https://docs.docker.com/engine/reference/run/#ipc-settings---ipc
-    #   [2]: https://docs.docker.com/engine/security/security/
-    #   [3]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html
     #   @return [String]
     #
     # @!attribute [rw] proxy_configuration
@@ -11839,8 +11729,12 @@ module Aws::ECS
     end
 
     # The specified task set wasn't found. You can view your available task
-    # sets with DescribeTaskSets. Task sets are specific to each cluster,
-    # service and Region.
+    # sets with [DescribeTaskSets][1]. Task sets are specific to each
+    # cluster, service and Region.
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeTaskSets.html
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/TaskSetNotFoundException AWS API Documentation
     #
@@ -11944,7 +11838,7 @@ module Aws::ECS
     # values set by the operating system with the exception of the `nofile`
     # resource limit parameter which Fargate overrides. The `nofile`
     # resource limit sets a restriction on the number of open files that a
-    # container can use. The default `nofile` soft limit is `1024` and the
+    # container can use. The default `nofile` soft limit is ` 65535` and the
     # default hard limit is `65535`.
     #
     # You can specify the `ulimit` settings for a container in a task
@@ -12099,7 +11993,7 @@ module Aws::ECS
     #   The setting to use by default for a cluster. This parameter is used
     #   to turn on CloudWatch Container Insights for a cluster. If this
     #   value is specified, it overrides the `containerInsights` value set
-    #   with PutAccountSetting or PutAccountSettingDefault.
+    #   with [PutAccountSetting][1] or [PutAccountSettingDefault][2].
     #
     #   Currently, if you delete an existing cluster that does not have
     #   Container Insights turned on, and then create a new cluster with the
@@ -12107,6 +12001,11 @@ module Aws::ECS
     #   not actually be turned on. If you want to preserve the same name for
     #   your existing cluster and turn on Container Insights, you must wait
     #   7 days before you can re-create it.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutAccountSetting.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutAccountSettingDefault.html
     #   @return [Array<Types::ClusterSetting>]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/UpdateClusterSettingsRequest AWS API Documentation
@@ -12296,23 +12195,31 @@ module Aws::ECS
     #   A capacity provider strategy consists of one or more capacity
     #   providers along with the `base` and `weight` to assign to them. A
     #   capacity provider must be associated with the cluster to be used in
-    #   a capacity provider strategy. The PutClusterCapacityProviders API is
-    #   used to associate a capacity provider with a cluster. Only capacity
-    #   providers with an `ACTIVE` or `UPDATING` status can be used.
+    #   a capacity provider strategy. The [PutClusterCapacityProviders][1]
+    #   API is used to associate a capacity provider with a cluster. Only
+    #   capacity providers with an `ACTIVE` or `UPDATING` status can be
+    #   used.
     #
     #   If specifying a capacity provider that uses an Auto Scaling group,
     #   the capacity provider must already be created. New capacity
-    #   providers can be created with the CreateCapacityProvider API
-    #   operation.
+    #   providers can be created with the [CreateClusterCapacityProvider][2]
+    #   API operation.
     #
     #   To use a Fargate capacity provider, specify either the `FARGATE` or
     #   `FARGATE_SPOT` capacity providers. The Fargate capacity providers
     #   are available to all accounts and only need to be associated with a
     #   cluster to be used.
     #
-    #   The PutClusterCapacityProviders API operation is used to update the
-    #   list of available capacity providers for a cluster after the cluster
-    #   is created.
+    #   The [PutClusterCapacityProviders][1]API operation is used to update
+    #   the list of available capacity providers for a cluster after the
+    #   cluster is created.
+    #
+    #
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html
+    #   [2]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateClusterCapacityProvider.html
     #   @return [Array<Types::CapacityProviderStrategyItem>]
     #
     # @!attribute [rw] deployment_configuration