aws-sdk-ecs 1.36.0 → 1.37.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2019ee6ea14fa7ba8d023667d486def343e0e1a2
-  data.tar.gz: 104bb8f77fda44a2a3497b50b7d246aa066c5d2e
+  metadata.gz: e8a08b1dea67387381c44930e73aafa4f69d4ac9
+  data.tar.gz: 2c5669523e6bdbaca6a4606f96428e1b0078a8a9
 SHA512:
-  metadata.gz: 163d0ca7decd652184a46462524ec47bae5fc7633a3b47b3b87c49f66c8822135b22989706580abc7d947d90c7ca72893aa70a69b7013f7b77b60db7e35287d1
-  data.tar.gz: ba4e880571a3445ad072b12dc317b2d06859159711792ebb9fb0540938d7428346c10aa77fe405d128629fb94067936571b2cedb6154e12608fa768524b9dd82
+  metadata.gz: a42a6060ad9da60859ed10048d6663d16974b11f0ba34a2e8db9586b605b958b7b0b60c1e11a51b3cd1f7c580553892ed325de9776d1e0ab42fedf3a33d425f4
+  data.tar.gz: 4790d8c9d0c7811b06d192809ee49e9149c16b737e6557b4811d99d6b76a2c0da04c9e3365b3ca83e414f40fdbbec832cb5a7e9b6ad2558dd6ec564a85cd2b8a

data/lib/aws-sdk-ecs.rb

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

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

@@ -1859,6 +1859,9 @@ module Aws::ECS
     #   resp.task_definition.container_definitions[0].log_configuration.log_driver #=> String, one of "json-file", "syslog", "journald", "gelf", "fluentd", "awslogs", "splunk"
     #   resp.task_definition.container_definitions[0].log_configuration.options #=> Hash
     #   resp.task_definition.container_definitions[0].log_configuration.options["String"] #=> String
+    #   resp.task_definition.container_definitions[0].log_configuration.secret_options #=> Array
+    #   resp.task_definition.container_definitions[0].log_configuration.secret_options[0].name #=> String
+    #   resp.task_definition.container_definitions[0].log_configuration.secret_options[0].value_from #=> String
     #   resp.task_definition.container_definitions[0].health_check.command #=> Array
     #   resp.task_definition.container_definitions[0].health_check.command[0] #=> String
     #   resp.task_definition.container_definitions[0].health_check.interval #=> Integer
@@ -2564,6 +2567,9 @@ module Aws::ECS
     #   resp.task_definition.container_definitions[0].log_configuration.log_driver #=> String, one of "json-file", "syslog", "journald", "gelf", "fluentd", "awslogs", "splunk"
     #   resp.task_definition.container_definitions[0].log_configuration.options #=> Hash
     #   resp.task_definition.container_definitions[0].log_configuration.options["String"] #=> String
+    #   resp.task_definition.container_definitions[0].log_configuration.secret_options #=> Array
+    #   resp.task_definition.container_definitions[0].log_configuration.secret_options[0].name #=> String
+    #   resp.task_definition.container_definitions[0].log_configuration.secret_options[0].value_from #=> String
     #   resp.task_definition.container_definitions[0].health_check.command #=> Array
     #   resp.task_definition.container_definitions[0].health_check.command[0] #=> String
     #   resp.task_definition.container_definitions[0].health_check.interval #=> Integer
@@ -4455,13 +4461,18 @@ module Aws::ECS
     # @option params [Types::ProxyConfiguration] :proxy_configuration
     #   The configuration details for the App Mesh proxy.
     #
-    #   Your Amazon ECS container instances require at least version 1.26.0 of
-    #   the container agent and at least version 1.26.0-1 of the `ecs-init`
-    #   package to enable a proxy configuration. If your container instances
-    #   are launched from the Amazon ECS-optimized AMI version `20190301` or
-    #   later, then they contain the required versions of the container agent
-    #   and `ecs-init`. For more information, see [Amazon ECS-optimized Linux
-    #   AMI][1] in the *Amazon Elastic Container Service Developer Guide*.
+    #   For tasks using the EC2 launch type, the container instances require
+    #   at least version 1.26.0 of the container agent and at least version
+    #   1.26.0-1 of the `ecs-init` package to enable a proxy configuration. If
+    #   your container instances are launched from the Amazon ECS-optimized
+    #   AMI version `20190301` or later, then they contain the required
+    #   versions of the container agent and `ecs-init`. For more information,
+    #   see [Amazon ECS-optimized Linux AMI][1] in the *Amazon Elastic
+    #   Container Service Developer Guide*.
+    #
+    #   This parameter is available for tasks using the Fargate launch type in
+    #   the Ohio (us-east-2) region only and the task or service requires
+    #   platform version 1.3.0 or later.
     #
     #
     #
@@ -4644,6 +4655,12 @@ module Aws::ECS
     #           options: {
     #             "String" => "String",
     #           },
+    #           secret_options: [
+    #             {
+    #               name: "String", # required
+    #               value_from: "String", # required
+    #             },
+    #           ],
     #         },
     #         health_check: {
     #           command: ["String"], # required
@@ -4795,6 +4812,9 @@ module Aws::ECS
     #   resp.task_definition.container_definitions[0].log_configuration.log_driver #=> String, one of "json-file", "syslog", "journald", "gelf", "fluentd", "awslogs", "splunk"
     #   resp.task_definition.container_definitions[0].log_configuration.options #=> Hash
     #   resp.task_definition.container_definitions[0].log_configuration.options["String"] #=> String
+    #   resp.task_definition.container_definitions[0].log_configuration.secret_options #=> Array
+    #   resp.task_definition.container_definitions[0].log_configuration.secret_options[0].name #=> String
+    #   resp.task_definition.container_definitions[0].log_configuration.secret_options[0].value_from #=> String
     #   resp.task_definition.container_definitions[0].health_check.command #=> Array
     #   resp.task_definition.container_definitions[0].health_check.command[0] #=> String
     #   resp.task_definition.container_definitions[0].health_check.interval #=> Integer
@@ -6570,7 +6590,7 @@ module Aws::ECS
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-ecs'
-      context[:gem_version] = '1.36.0'
+      context[:gem_version] = '1.37.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

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

@@ -777,6 +777,7 @@ module Aws::ECS
 
     LogConfiguration.add_member(:log_driver, Shapes::ShapeRef.new(shape: LogDriver, required: true, location_name: "logDriver"))
     LogConfiguration.add_member(:options, Shapes::ShapeRef.new(shape: LogConfigurationOptionsMap, location_name: "options"))
+    LogConfiguration.add_member(:secret_options, Shapes::ShapeRef.new(shape: SecretList, location_name: "secretOptions"))
     LogConfiguration.struct_class = Types::LogConfiguration
 
     LogConfigurationOptionsMap.key = Shapes::ShapeRef.new(shape: String)

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

@@ -441,6 +441,12 @@ module Aws::ECS
     #           options: {
     #             "String" => "String",
     #           },
+    #           secret_options: [
+    #             {
+    #               name: "String", # required
+    #               value_from: "String", # required
+    #             },
+    #           ],
     #         },
     #         health_check: {
     #           command: ["String"], # required
@@ -857,18 +863,23 @@ module Aws::ECS
     #   defined for container startup, for container shutdown it is
     #   reversed.
     #
-    #   Your Amazon ECS container instances require at least version 1.26.0
-    #   of the container agent to enable container dependencies. However, we
-    #   recommend using the latest container agent version. For information
-    #   about checking your agent version and updating to the latest
-    #   version, see [Updating the Amazon ECS Container Agent][1] in the
-    #   *Amazon Elastic Container Service Developer Guide*. If you are using
-    #   an Amazon ECS-optimized Linux AMI, your instance needs at least
-    #   version 1.26.0-1 of the `ecs-init` package. If your container
-    #   instances are launched from version `20190301` or later, then they
-    #   contain the required versions of the container agent and `ecs-init`.
-    #   For more information, see [Amazon ECS-optimized Linux AMI][2] in the
-    #   *Amazon Elastic Container Service Developer Guide*.
+    #   For tasks using the EC2 launch type, the container instances require
+    #   at least version 1.26.0 of the container agent to enable container
+    #   dependencies. However, we recommend using the latest container agent
+    #   version. For information about checking your agent version and
+    #   updating to the latest version, see [Updating the Amazon ECS
+    #   Container Agent][1] in the *Amazon Elastic Container Service
+    #   Developer Guide*. If you are using an Amazon ECS-optimized Linux
+    #   AMI, your instance needs at least version 1.26.0-1 of the `ecs-init`
+    #   package. If your container instances are launched from version
+    #   `20190301` or later, then they contain the required versions of the
+    #   container agent and `ecs-init`. For more information, see [Amazon
+    #   ECS-optimized Linux AMI][2] in the *Amazon Elastic Container Service
+    #   Developer Guide*.
+    #
+    #   This parameter is available for tasks using the Fargate launch type
+    #   in the Ohio (us-east-2) region only and the task or service requires
+    #   platform version 1.3.0 or later.
     #
     #
     #
@@ -886,18 +897,23 @@ module Aws::ECS
     #   up and not start. This results in the task transitioning to a
     #   `STOPPED` state.
     #
-    #   Your Amazon ECS container instances require at least version 1.26.0
-    #   of the container agent to enable a container start timeout value.
-    #   However, we recommend using the latest container agent version. For
-    #   information about checking your agent version and updating to the
-    #   latest version, see [Updating the Amazon ECS Container Agent][1] in
-    #   the *Amazon Elastic Container Service Developer Guide*. If you are
-    #   using an Amazon ECS-optimized Linux AMI, your instance needs at
-    #   least version 1.26.0-1 of the `ecs-init` package. If your container
-    #   instances are launched from version `20190301` or later, then they
-    #   contain the required versions of the container agent and `ecs-init`.
-    #   For more information, see [Amazon ECS-optimized Linux AMI][2] in the
-    #   *Amazon Elastic Container Service Developer Guide*.
+    #   For tasks using the EC2 launch type, the container instances require
+    #   at least version 1.26.0 of the container agent to enable a container
+    #   start timeout value. However, we recommend using the latest
+    #   container agent version. For information about checking your agent
+    #   version and updating to the latest version, see [Updating the Amazon
+    #   ECS Container Agent][1] in the *Amazon Elastic Container Service
+    #   Developer Guide*. If you are using an Amazon ECS-optimized Linux
+    #   AMI, your instance needs at least version 1.26.0-1 of the `ecs-init`
+    #   package. If your container instances are launched from version
+    #   `20190301` or later, then they contain the required versions of the
+    #   container agent and `ecs-init`. For more information, see [Amazon
+    #   ECS-optimized Linux AMI][2] in the *Amazon Elastic Container Service
+    #   Developer Guide*.
+    #
+    #   This parameter is available for tasks using the Fargate launch type
+    #   in the Ohio (us-east-2) region only and the task or service requires
+    #   platform version 1.3.0 or later.
     #
     #
     #
@@ -907,22 +923,27 @@ module Aws::ECS
     #
     # @!attribute [rw] stop_timeout
     #   Time duration to wait before the container is forcefully killed if
-    #   it doesn't exit normally on its own. The stop timeout value for the
-    #   container takes precedence over the `ECS_CONTAINER_STOP_TIMEOUT`
-    #   container agent configuration parameter, if used.
+    #   it doesn't exit normally on its own. For tasks using the Fargate
+    #   launch type, the max `stopTimeout` value is 2 minutes. This
+    #   parameter is available for tasks using the Fargate launch type in
+    #   the Ohio (us-east-2) region only and the task or service requires
+    #   platform version 1.3.0 or later.
     #
-    #   Your Amazon ECS container instances require at least version 1.26.0
-    #   of the container agent to enable a container stop timeout value.
-    #   However, we recommend using the latest container agent version. For
-    #   information about checking your agent version and updating to the
-    #   latest version, see [Updating the Amazon ECS Container Agent][1] in
-    #   the *Amazon Elastic Container Service Developer Guide*. If you are
-    #   using an Amazon ECS-optimized Linux AMI, your instance needs at
-    #   least version 1.26.0-1 of the `ecs-init` package. If your container
-    #   instances are launched from version `20190301` or later, then they
-    #   contain the required versions of the container agent and `ecs-init`.
-    #   For more information, see [Amazon ECS-optimized Linux AMI][2] in the
-    #   *Amazon Elastic Container Service Developer Guide*.
+    #   For tasks using the EC2 launch type, the stop timeout value for the
+    #   container takes precedence over the `ECS_CONTAINER_STOP_TIMEOUT`
+    #   container agent configuration parameter, if used. Container
+    #   instances require at least version 1.26.0 of the container agent to
+    #   enable a container stop timeout value. However, we recommend using
+    #   the latest container agent version. For information about checking
+    #   your agent version and updating to the latest version, see [Updating
+    #   the Amazon ECS Container Agent][1] in the *Amazon Elastic Container
+    #   Service Developer Guide*. If you are using an Amazon ECS-optimized
+    #   Linux AMI, your instance needs at least version 1.26.0-1 of the
+    #   `ecs-init` package. If your container instances are launched from
+    #   version `20190301` or later, then they contain the required versions
+    #   of the container agent and `ecs-init`. For more information, see
+    #   [Amazon ECS-optimized Linux AMI][2] in the *Amazon Elastic Container
+    #   Service Developer Guide*.
     #
     #
     #
@@ -1190,8 +1211,12 @@ module Aws::ECS
     # @!attribute [rw] log_configuration
     #   The log configuration specification for the container.
     #
-    #   If you are using the Fargate launch type, the only supported value
-    #   is `awslogs`.
+    #   For tasks using the Fargate launch type, the supported log drivers
+    #   are `awslogs` and `splunk`.
+    #
+    #   For tasks using the EC2 launch type, the supported log drivers are
+    #   `awslogs`, `syslog`, `gelf`, `fluentd`, `splunk`, `journald`, and
+    #   `json-file`.
     #
     #   This parameter maps to `LogConfig` in the [Create a container][1]
     #   section of the [Docker Remote API][2] and the `--log-driver` option
@@ -4462,16 +4487,29 @@ module Aws::ECS
     #         options: {
     #           "String" => "String",
     #         },
+    #         secret_options: [
+    #           {
+    #             name: "String", # required
+    #             value_from: "String", # required
+    #           },
+    #         ],
     #       }
     #
     # @!attribute [rw] log_driver
     #   The log driver to use for the container. The valid values listed for
     #   this parameter are log drivers that the Amazon ECS container agent
-    #   can communicate with by default. If you are using the Fargate launch
-    #   type, the only supported value is `awslogs`. For more information
-    #   about using the `awslogs` driver, see [Using the awslogs Log
-    #   Driver][1] in the *Amazon Elastic Container Service Developer
-    #   Guide*.
+    #   can communicate with by default.
+    #
+    #   For tasks using the Fargate launch type, the supported log drivers
+    #   are `awslogs` and `splunk`.
+    #
+    #   For tasks using the EC2 launch type, the supported log drivers are
+    #   `awslogs`, `syslog`, `gelf`, `fluentd`, `splunk`, `journald`, and
+    #   `json-file`.
+    #
+    #   For more information about using the `awslogs` log driver, see
+    #   [Using the awslogs Log Driver][1] in the *Amazon Elastic Container
+    #   Service Developer Guide*.
     #
     #   <note markdown="1"> If you have a custom driver that is not listed above that you would
     #   like to work with the Amazon ECS container agent, you can fork the
@@ -4504,11 +4542,16 @@ module Aws::ECS
     #   '\{\{.Server.APIVersion\}\}'`
     #   @return [Hash<String,String>]
     #
+    # @!attribute [rw] secret_options
+    #   The secrets to pass to the log configuration.
+    #   @return [Array<Types::Secret>]
+    #
     # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/LogConfiguration AWS API Documentation
     #
     class LogConfiguration < Struct.new(
       :log_driver,
-      :options)
+      :options,
+      :secret_options)
       include Aws::Structure
     end
 
@@ -4858,13 +4901,18 @@ module Aws::ECS
 
     # The configuration details for the App Mesh proxy.
     #
-    # Your Amazon ECS container instances require at least version 1.26.0 of
-    # the container agent and at least version 1.26.0-1 of the `ecs-init`
-    # package to enable a proxy configuration. If your container instances
-    # are launched from the Amazon ECS-optimized AMI version `20190301` or
-    # later, then they contain the required versions of the container agent
-    # and `ecs-init`. For more information, see [Amazon ECS-optimized Linux
-    # AMI][1] in the *Amazon Elastic Container Service Developer Guide*.
+    # For tasks using the EC2 launch type, the container instances require
+    # at least version 1.26.0 of the container agent and at least version
+    # 1.26.0-1 of the `ecs-init` package to enable a proxy configuration. If
+    # your container instances are launched from the Amazon ECS-optimized
+    # AMI version `20190301` or later, then they contain the required
+    # versions of the container agent and `ecs-init`. For more information,
+    # see [Amazon ECS-optimized Linux AMI][1] in the *Amazon Elastic
+    # Container Service Developer Guide*.
+    #
+    # This parameter is available for tasks using the Fargate launch type in
+    # the Ohio (us-east-2) region only and the task or service requires
+    # platform version 1.3.0 or later.
     #
     #
     #
@@ -5311,6 +5359,12 @@ module Aws::ECS
     #               options: {
     #                 "String" => "String",
     #               },
+    #               secret_options: [
+    #                 {
+    #                   name: "String", # required
+    #                   value_from: "String", # required
+    #                 },
+    #               ],
     #             },
     #             health_check: {
     #               command: ["String"], # required
@@ -5629,14 +5683,18 @@ module Aws::ECS
     # @!attribute [rw] proxy_configuration
     #   The configuration details for the App Mesh proxy.
     #
-    #   Your Amazon ECS container instances require at least version 1.26.0
-    #   of the container agent and at least version 1.26.0-1 of the
-    #   `ecs-init` package to enable a proxy configuration. If your
-    #   container instances are launched from the Amazon ECS-optimized AMI
-    #   version `20190301` or later, then they contain the required versions
-    #   of the container agent and `ecs-init`. For more information, see
-    #   [Amazon ECS-optimized Linux AMI][1] in the *Amazon Elastic Container
-    #   Service Developer Guide*.
+    #   For tasks using the EC2 launch type, the container instances require
+    #   at least version 1.26.0 of the container agent and at least version
+    #   1.26.0-1 of the `ecs-init` package to enable a proxy configuration.
+    #   If your container instances are launched from the Amazon
+    #   ECS-optimized AMI version `20190301` or later, then they contain the
+    #   required versions of the container agent and `ecs-init`. For more
+    #   information, see [Amazon ECS-optimized Linux AMI][1] in the *Amazon
+    #   Elastic Container Service Developer Guide*.
+    #
+    #   This parameter is available for tasks using the Fargate launch type
+    #   in the Ohio (us-east-2) region only and the task or service requires
+    #   platform version 1.3.0 or later.
     #
     #
     #
@@ -6059,9 +6117,17 @@ module Aws::ECS
       include Aws::Structure
     end
 
-    # An object representing the secret to expose to your container. For
-    # more information, see [Specifying Sensitive Data][1] in the *Amazon
-    # Elastic Container Service Developer Guide*.
+    # An object representing the secret to expose to your container. Secrets
+    # can be exposed to a container in the following ways:
+    #
+    # * To inject sensitive data into your containers as environment
+    #   variables, use the `secrets` container definition parameter.
+    #
+    # * To reference sensitive information in the log configuration of a
+    #   container, use the `secretOptions` container definition parameter.
+    #
+    # For more information, see [Specifying Sensitive Data][1] in the
+    # *Amazon Elastic Container Service Developer Guide*.
     #
     #
     #
@@ -6076,16 +6142,13 @@ module Aws::ECS
     #       }
     #
     # @!attribute [rw] name
-    #   The value to set as the environment variable on the container.
+    #   The name of the secret.
     #   @return [String]
     #
     # @!attribute [rw] value_from
-    #   The secret to expose to the container. If your task is using the EC2
-    #   launch type, then supported values are either the full ARN of the
-    #   AWS Secrets Manager secret or the full ARN of the parameter in the
-    #   AWS Systems Manager Parameter Store. If your task is using the
-    #   Fargate launch type, then the only supported value is the full ARN
-    #   of the parameter in the AWS Systems Manager Parameter Store.
+    #   The secret to expose to the container. The supported values are
+    #   either the full ARN of the AWS Secrets Manager secret or the full
+    #   ARN of the parameter in the AWS Systems Manager Parameter Store.
     #
     #   <note markdown="1"> If the AWS Systems Manager Parameter Store parameter exists in the
     #   same Region as the task you are launching, then you can use either

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-ecs
 version: !ruby/object:Gem::Version
-  version: 1.36.0
+  version: 1.37.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-03-27 00:00:00.000000000 Z
+date: 2019-05-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core
@@ -60,7 +60,7 @@ files:
 - lib/aws-sdk-ecs/resource.rb
 - lib/aws-sdk-ecs/types.rb
 - lib/aws-sdk-ecs/waiters.rb
-homepage: http://github.com/aws/aws-sdk-ruby
+homepage: https://github.com/aws/aws-sdk-ruby
 licenses:
 - Apache-2.0
 metadata: