aws-sdk-ecs 1.6.0 → 1.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 53753bedee288b71f54f3c7159fb138c33258636
-  data.tar.gz: e51e5731b26691a59852e41588bb86a5706ac42f
+  metadata.gz: 1192b07cf1d3c418a52e3b6f24232c709f194c33
+  data.tar.gz: 459dda7b74df8222d05a24d9e032cd911a6af557
 SHA512:
-  metadata.gz: ca4c4779b0511d4692d89173adb7d6fdc1a228154530918ececeea26c1d1a9d5cdd802252ea6eb14c927dddd50e36a12ce114bc0c2fcad469d1419d4de147c8f
-  data.tar.gz: db2e94f0a85499247d5e13b559c19a5ac6c2f2be23d7b6143e55982f7eb3bdb6585f9d5d9492a67e7a13859833ffe5c1fb6e8322ec594b7536a70f1f57508709
+  metadata.gz: 97707f6e2e42433deea9adc95b0d992e4e5d82bd98fecba10f76e88b94956791c4e4731c3cfe03d3afe0f75820d69df0cb4bf756274b384e38814f8a37e46ad2
+  data.tar.gz: debdcf457e39e5edac642f31f71bebde5a73df26bcf79892a6321b369cb9d9dbdeb35e409a1fb9f0385041e21f7007faa5f22ee34c5b731e9d2d38c88e584ef9

data/lib/aws-sdk-ecs.rb

@@ -43,6 +43,6 @@ require_relative 'aws-sdk-ecs/customizations'
 # @service
 module Aws::ECS
 
-  GEM_VERSION = '1.6.0'
+  GEM_VERSION = '1.7.0'
 
 end

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

@@ -2864,6 +2864,10 @@ module Aws::ECS
     #   of the same task on a single container instance when port mappings are
     #   used.
     #
+    #   Docker for Windows uses different network modes than Docker for Linux.
+    #   When you register a task definition with Windows containers, you must
+    #   not specify a network mode.
+    #
     #   For more information, see [Network settings][2] in the *Docker run
     #   reference*.
     #
@@ -4371,7 +4375,7 @@ module Aws::ECS
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-ecs'
-      context[:gem_version] = '1.6.0'
+      context[:gem_version] = '1.7.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

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

@@ -419,20 +419,15 @@ module Aws::ECS
     #   @return [String]
     #
     # @!attribute [rw] cpu
-    #   The number of `cpu` units reserved for the container. If your
-    #   containers will be part of a task using the Fargate launch type,
-    #   this field is optional and the only requirement is that the total
-    #   amount of CPU reserved for all containers within a task be lower
-    #   than the task `cpu` value.
+    #   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].
     #
-    #   For containers that will be part of a task using the EC2 launch
-    #   type, a container instance has 1,024 `cpu` units for every CPU core.
-    #   This parameter specifies the minimum amount of CPU to reserve for a
-    #   container, and containers share unallocated CPU units with other
-    #   containers on the instance with the same ratio as their allocated
-    #   amount. 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].
+    #   This field is optional for tasks using the Fargate launch type, and
+    #   the only requirement is that the total amount of CPU reserved for
+    #   all containers within a task be lower than the task-level `cpu`
+    #   value.
     #
     #   <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
@@ -451,14 +446,28 @@ module Aws::ECS
     #   were 100% active all of the time, they would be limited to 512 CPU
     #   units.
     #
-    #   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 is not 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:
+    #   Linux containers share unallocated CPU units with other containers
+    #   on the container instance with the same ratio as their allocated
+    #   amount. For example, if you run a single-container task on a
+    #   single-core instance type with 512 CPU units specified for that
+    #   container, and that is the only task running on the container
+    #   instance, that container could use the full 1,024 CPU unit share at
+    #   any given time. However, if you launched another copy of the same
+    #   task on that container instance, each task would be guaranteed a
+    #   minimum of 512 CPU units when needed, and each container could float
+    #   to higher CPU usage if the other container was not using it, but if
+    #   both tasks were 100% active all of the time, they would be limited
+    #   to 512 CPU units.
+    #
+    #   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 will allow is 2; however, the CPU
+    #   parameter is not 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:
     #
     #   * **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
@@ -468,6 +477,11 @@ 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.
     #
+    #   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 is described in the task
+    #   definition.
+    #
     #
     #
     #   [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -543,17 +557,20 @@ module Aws::ECS
     #
     # @!attribute [rw] links
     #   The `link` parameter allows containers to communicate with each
-    #   other without the need for port mappings, using the `name` parameter
-    #   and optionally, an `alias` for the link. This construct is analogous
-    #   to `name:alias` in Docker links. This field is not valid for
-    #   containers in tasks using the Fargate launch type. Up to 255 letters
-    #   (uppercase and lowercase), numbers, hyphens, and underscores are
-    #   allowed for each `name` and `alias`. For more information on linking
-    #   Docker containers, see
+    #   other without the need for port mappings. Only supported if the
+    #   network mode of a task definition is set to `bridge`. The
+    #   `name:internalName` construct is analogous to `name:alias` in Docker
+    #   links. Up to 255 letters (uppercase and lowercase), numbers,
+    #   hyphens, and underscores are allowed. For more information about
+    #   linking Docker containers, go to
     #   [https://docs.docker.com/engine/userguide/networking/default\_network/dockerlinks/][1].
     #   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].
+    #   section of the [Docker Remote API][3] and the `--link` option to [
+    #   `docker run` ][4].
+    #
+    #   <note markdown="1"> This parameter is not supported for Windows containers.
+    #
+    #    </note>
     #
     #   Containers that are collocated on a single container instance may be
     #   able to communicate with each other without requiring links or host
@@ -565,7 +582,7 @@ module Aws::ECS
     #   [1]: https://docs.docker.com/engine/userguide/networking/default_network/dockerlinks/
     #   [2]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
     #   [3]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/
-    #   [4]: https://docs.docker.com/engine/reference/run/
+    #   [4]: https://docs.docker.com/engine/reference/commandline/run/
     #   @return [Array<String>]
     #
     # @!attribute [rw] port_mappings
@@ -573,10 +590,15 @@ module Aws::ECS
     #   containers to access ports on the host container instance to send or
     #   receive traffic.
     #
-    #   If using containers in a task with the Fargate, exposed ports should
-    #   be specified using `containerPort`. The `hostPort` can be left blank
+    #   For task definitions that use the `awsvpc` network mode, you should
+    #   only specify the `containerPort`. The `hostPort` can be left blank
     #   or it must be the same value as the `containerPort`.
     #
+    #   Port mappings on Windows use the `NetNAT` gateway address rather
+    #   than `localhost`. There is no loopback for port mappings on Windows,
+    #   so you cannot 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
@@ -673,13 +695,14 @@ module Aws::ECS
     # @!attribute [rw] mount_points
     #   The mount points for data volumes in your container.
     #
-    #   If using the Fargate launch type, the `sourceVolume` parameter is
-    #   not supported.
-    #
     #   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].
     #
+    #   Windows containers can mount whole directories on the same drive as
+    #   `$env:ProgramData`. Windows containers cannot mount directories on a
+    #   different drive, and mount point cannot be across drives.
+    #
     #
     #
     #   [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -701,8 +724,12 @@ module Aws::ECS
     #
     # @!attribute [rw] linux_parameters
     #   Linux-specific modifications that are applied to the container, such
-    #   as Linux KernelCapabilities. This field is not valid for containers
-    #   in tasks using the Fargate launch type.
+    #   as Linux KernelCapabilities.
+    #
+    #   <note markdown="1"> This parameter is not supported for Windows containers or tasks
+    #   using the Fargate launch type.
+    #
+    #    </note>
     #   @return [Types::LinuxParameters]
     #
     # @!attribute [rw] hostname
@@ -722,6 +749,10 @@ module Aws::ECS
     #   `User` in the [Create a container][1] section of the [Docker Remote
     #   API][2] and the `--user` option to [docker run][3].
     #
+    #   <note markdown="1"> This parameter is not supported for Windows containers.
+    #
+    #    </note>
+    #
     #
     #
     #   [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -747,6 +778,10 @@ module Aws::ECS
     #   container. This parameter maps to `NetworkDisabled` in the [Create a
     #   container][1] section of the [Docker Remote API][2].
     #
+    #   <note markdown="1"> This parameter is not supported for Windows containers.
+    #
+    #    </note>
+    #
     #
     #
     #   [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -760,6 +795,11 @@ module Aws::ECS
     #   container][1] section of the [Docker Remote API][2] and the
     #   `--privileged` option to [docker run][3].
     #
+    #   <note markdown="1"> This parameter is not supported for Windows containers or tasks
+    #   using the Fargate launch type.
+    #
+    #    </note>
+    #
     #
     #
     #   [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -773,6 +813,10 @@ module Aws::ECS
     #   the [Create a container][1] section of the [Docker Remote API][2]
     #   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/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -785,6 +829,10 @@ module Aws::ECS
     #   the [Docker Remote API][2] and the `--dns` option to [docker
     #   run][3].
     #
+    #   <note markdown="1"> This parameter is not supported for Windows containers.
+    #
+    #    </note>
+    #
     #
     #
     #   [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -798,6 +846,10 @@ module Aws::ECS
     #   section of the [Docker Remote API][2] and the `--dns-search` option
     #   to [docker run][3].
     #
+    #   <note markdown="1"> This parameter is not supported for Windows containers.
+    #
+    #    </note>
+    #
     #
     #
     #   [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -813,6 +865,10 @@ module Aws::ECS
     #   [Create a container][1] section of the [Docker Remote API][2] and
     #   the `--add-host` option to [docker run][3].
     #
+    #   <note markdown="1"> This parameter is not supported for Windows containers.
+    #
+    #    </note>
+    #
     #
     #
     #   [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -836,6 +892,8 @@ module Aws::ECS
     #   information, see [Amazon ECS Container Agent Configuration][4] in
     #   the *Amazon Elastic Container Service Developer Guide*.
     #
+    #    This parameter is not supported for Windows containers.
+    #
     #    </note>
     #
     #
@@ -873,6 +931,10 @@ module Aws::ECS
     #   container instance, log in to your container instance and run the
     #   following command: `sudo docker version | grep "Server API version"`
     #
+    #   <note markdown="1"> This parameter is not supported for Windows containers.
+    #
+    #    </note>
+    #
     #
     #
     #   [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -2116,8 +2178,8 @@ module Aws::ECS
     #   container instance, the Docker daemon creates it. If the location
     #   does exist, the contents of the source path folder are exported.
     #
-    #   If you are using the Fargate launch type, the `host` parameter is
-    #   not supported.
+    #   If you are using the Fargate launch type, the `sourcePath` parameter
+    #   is not supported.
     #   @return [String]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/HostVolumeProperties AWS API Documentation
@@ -3027,8 +3089,7 @@ module Aws::ECS
     #       }
     #
     # @!attribute [rw] source_volume
-    #   The name of the volume to mount. If using the Fargate launch type,
-    #   the `sourceVolume` parameter is not supported.
+    #   The name of the volume to mount.
     #   @return [String]
     #
     # @!attribute [rw] container_path
@@ -3628,6 +3689,10 @@ module Aws::ECS
     #   instantiations of the same task on a single container instance when
     #   port mappings are used.
     #
+    #   Docker for Windows uses different network modes than Docker for
+    #   Linux. When you register a task definition with Windows containers,
+    #   you must not specify a network mode.
+    #
     #   For more information, see [Network settings][2] in the *Docker run
     #   reference*.
     #
@@ -4673,6 +4738,17 @@ module Aws::ECS
     #   The ARN of the IAM role that containers in this task can assume. All
     #   containers in this task are granted the permissions that are
     #   specified in this role.
+    #
+    #   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 in order to
+    #   take advantage of the feature. For more information, see [Windows
+    #   IAM Roles for Tasks][1] in the *Amazon Elastic Container Service
+    #   Developer Guide*.
+    #
+    #
+    #
+    #   [1]: http://docs.aws.amazon.com/AmazonECS/latest/developerguide/windows_task_IAM_roles.html
     #   @return [String]
     #
     # @!attribute [rw] execution_role_arn
@@ -4705,10 +4781,22 @@ module Aws::ECS
     #   more information, see [Task Networking][1] in the *Amazon Elastic
     #   Container Service Developer Guide*.
     #
+    #   <note markdown="1"> Currently, only the Amazon ECS-optimized AMI, other Amazon Linux
+    #   variants with the `ecs-init` package, or AWS Fargate infrastructure
+    #   support the `awsvpc` network mode.
+    #
+    #    </note>
+    #
     #   If the network mode is `host`, you can't run multiple
     #   instantiations of the same task on a single container instance when
     #   port mappings are used.
     #
+    #   Docker for Windows uses different network modes than Docker for
+    #   Linux. When you register a task definition with Windows containers,
+    #   you must not specify a network mode. If you use the console to
+    #   register a task definition with Windows containers, you must choose
+    #   the `<default>` network mode object.
+    #
     #   For more information, see [Network settings][2] in the *Docker run
     #   reference*.
     #
@@ -5220,8 +5308,11 @@ module Aws::ECS
     #   guaranteed to persist after the containers associated with it stop
     #   running.
     #
-    #   If you are using the Fargate launch type, the `host` parameter is
-    #   not supported.
+    #   Windows containers can mount whole directories on the same drive as
+    #   `$env:ProgramData`. Windows containers cannot mount directories on a
+    #   different drive, and mount point cannot be across drives. For
+    #   example, you can mount `C:\my\path:C:\my\path` and `D:\:D:`, but
+    #   not `D:\my\path:C:\my\path` or `D:\:C:\my\path`.
     #   @return [Types::HostVolumeProperties]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/Volume AWS API Documentation

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-ecs
 version: !ruby/object:Gem::Version
-  version: 1.6.0
+  version: 1.7.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-12-04 00:00:00.000000000 Z
+date: 2017-12-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core