aws-sdk-ecs 1.161.0 → 1.162.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6b5a178cffaf39269127838457a69c73f375da437a3630a97b0d5b3b335e6427
-  data.tar.gz: c2f3698c67f3f95338c9fa511d4b1c571a7f2b531476715f625f7aee1f8ce859
+  metadata.gz: bb4b72671b0e9cb778b7b4d15c95f1ca241c1a569d601aaac7ac6e67505b5b95
+  data.tar.gz: f5b249ff7b9265a28872e21c01925e25a9e97ddc864a608b79b472e0b204de4a
 SHA512:
-  metadata.gz: b1a93cf66cef36ea15265d5b100f42b75d790a46f77ad2c863c15634d9d16235f4b59aa81927ab98b4e52024e3de79013b949a4459186d6c27ebc7add294fd0f
-  data.tar.gz: f0bd9d3ff78c6f310f64307ff3d2c36c8ea0d803b12675d8a17e864d54c22d8e8d68f10e418a22b2d8e46987c3a890c779fbbda4a88dc0611762159fa5b7116f
+  metadata.gz: e4e6ca2b76e483c818816bf002a1deef60cae9a1d9f63a2e88f3b4de775a2453023a5ac11d4652a85dc659ac23be3723db87ffda7f648779617583a83605e77c
+  data.tar.gz: b571ed1ca314aca94d80ea7d9dd4dc258dfef6f84d390bc6cda5a6165798dfbfa5058b32936e261d3a1752984ee2cd50765a1190243f12be442a2577d2c2b1b5

data/CHANGELOG.md

@@ -1,6 +1,11 @@
 Unreleased Changes
 ------------------
 
+1.162.0 (2024-10-10)
+------------------
+
+* Feature - This is a documentation only release that updates to documentation to let customers know that Amazon Elastic Inference is no longer available.
+
 1.161.0 (2024-09-24)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.161.0
+1.162.0

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

@@ -832,6 +832,10 @@ module Aws::ECS
     #
     #  </note>
     #
+    # <note markdown="1"> Amazon Elastic Inference (EI) is no longer available to customers.
+    #
+    #  </note>
+    #
     # In addition to maintaining the desired count of tasks in your service,
     # you can optionally run your service behind one or more load balancers.
     # The load balancers distribute traffic across the tasks that are
@@ -932,15 +936,6 @@ module Aws::ECS
     # strategies, see [Amazon ECS task placement][7] in the *Amazon Elastic
     # Container Service Developer Guide*
     #
-    # Starting April 15, 2023, Amazon Web Services will not onboard new
-    # customers to Amazon Elastic Inference (EI), and will help current
-    # customers migrate their workloads to options that offer better price
-    # and performance. After April 15, 2023, new customers will not be able
-    # to launch instances with Amazon EI accelerators in Amazon SageMaker,
-    # Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI
-    # at least once during the past 30-day period are considered current
-    # customers and will be able to continue using the service.
-    #
     #
     #
     # [1]: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html
@@ -7325,6 +7320,10 @@ module Aws::ECS
     #
     #  </note>
     #
+    # <note markdown="1"> Amazon Elastic Inference (EI) is no longer available to customers.
+    #
+    #  </note>
+    #
     # You can allow Amazon ECS to place tasks for you, or you can customize
     # how Amazon ECS places tasks using placement constraints and placement
     # strategies. For more information, see [Scheduling Tasks][1] in the
@@ -7333,15 +7332,6 @@ module Aws::ECS
     # Alternatively, you can use `StartTask` to use your own scheduler or
     # place tasks manually on specific container instances.
     #
-    # Starting April 15, 2023, Amazon Web Services will not onboard new
-    # customers to Amazon Elastic Inference (EI), and will help current
-    # customers migrate their workloads to options that offer better price
-    # and performance. After April 15, 2023, new customers will not be able
-    # to launch instances with Amazon EI accelerators in Amazon SageMaker,
-    # Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI
-    # at least once during the past 30-day period are considered current
-    # customers and will be able to continue using the service.
-    #
     # You can attach Amazon EBS volumes to Amazon ECS tasks by configuring
     # the volume when creating or updating a service. For more infomation,
     # see [Amazon EBS volumes][2] in the *Amazon Elastic Container Service
@@ -7909,14 +7899,9 @@ module Aws::ECS
     #
     #  </note>
     #
-    # Starting April 15, 2023, Amazon Web Services will not onboard new
-    # customers to Amazon Elastic Inference (EI), and will help current
-    # customers migrate their workloads to options that offer better price
-    # and performance. After April 15, 2023, new customers will not be able
-    # to launch instances with Amazon EI accelerators in Amazon SageMaker,
-    # Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI
-    # at least once during the past 30-day period are considered current
-    # customers and will be able to continue using the service.
+    # <note markdown="1"> Amazon Elastic Inference (EI) is no longer available to customers.
+    #
+    #  </note>
     #
     # Alternatively, you can use`RunTask` to place tasks for you. For more
     # information, see [Scheduling Tasks][1] in the *Amazon Elastic
@@ -10446,7 +10431,7 @@ module Aws::ECS
         tracer: tracer
       )
       context[:gem_name] = 'aws-sdk-ecs'
-      context[:gem_version] = '1.161.0'
+      context[:gem_version] = '1.162.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

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

@@ -405,8 +405,10 @@ module Aws::ECS
     # that's discounted compared to the `FARGATE` price. `FARGATE_SPOT`
     # runs tasks on spare compute capacity. When Amazon Web Services needs
     # the capacity back, your tasks are interrupted with a two-minute
-    # warning. `FARGATE_SPOT` only supports Linux tasks with the X86\_64
-    # architecture on platform version 1.3.0 or later.
+    # warning. `FARGATE_SPOT` supports Linux tasks with the X86\_64
+    # architecture on platform version 1.3.0 or later. `FARGATE_SPOT`
+    # supports Linux tasks with the ARM64 architecture on platform version
+    # 1.4.0 or later.
     #
     # A capacity provider strategy may contain a maximum of 6 capacity
     # providers.
@@ -6528,12 +6530,199 @@ module Aws::ECS
     #   @return [String]
     #
     # @!attribute [rw] options
-    #   The configuration options to send to the log driver. This parameter
-    #   requires version 1.19 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\}\}'`
+    #   The configuration options to send to the log driver.
+    #
+    #   The options you can specify depend on the log driver. Some of the
+    #   options you can specify when you use the `awslogs` log driver to
+    #   route logs to Amazon CloudWatch include the following:
+    #
+    #   awslogs-create-group
+    #
+    #   : Required: No
+    #
+    #     Specify whether you want the log group to be created
+    #     automatically. If this option isn't specified, it defaults to
+    #     `false`.
+    #
+    #     <note markdown="1"> Your IAM policy must include the `logs:CreateLogGroup` permission
+    #     before you attempt to use `awslogs-create-group`.
+    #
+    #      </note>
+    #
+    #   awslogs-region
+    #
+    #   : Required: Yes
+    #
+    #     Specify the Amazon Web Services Region that the `awslogs` log
+    #     driver is to send your Docker logs to. You can choose to send all
+    #     of your logs from clusters in different Regions to a single region
+    #     in CloudWatch Logs. This is so that they're all visible in one
+    #     location. Otherwise, you can separate them by Region for more
+    #     granularity. Make sure that the specified log group exists in the
+    #     Region that you specify with this option.
+    #
+    #   awslogs-group
+    #
+    #   : Required: Yes
+    #
+    #     Make sure to specify a log group that the `awslogs` log driver
+    #     sends its log streams to.
+    #
+    #   awslogs-stream-prefix
+    #
+    #   : Required: Yes, when using the Fargate launch type.Optional for the
+    #     EC2 launch type, required for the Fargate launch type.
+    #
+    #     Use the `awslogs-stream-prefix` option to associate a log stream
+    #     with the specified prefix, the container name, and the ID of the
+    #     Amazon ECS task that the container belongs to. If you specify a
+    #     prefix with this option, then the log stream takes the format
+    #     `prefix-name/container-name/ecs-task-id`.
+    #
+    #     If you don't specify a prefix with this option, then the log
+    #     stream is named after the container ID that's assigned by the
+    #     Docker daemon on the container instance. Because it's difficult
+    #     to trace logs back to the container that sent them with just the
+    #     Docker container ID (which is only available on the container
+    #     instance), we recommend that you specify a prefix with this
+    #     option.
+    #
+    #     For Amazon ECS services, you can use the service name as the
+    #     prefix. Doing so, you can trace log streams to the service that
+    #     the container belongs to, the name of the container that sent
+    #     them, and the ID of the task that the container belongs to.
+    #
+    #     You must specify a stream-prefix for your logs to have your logs
+    #     appear in the Log pane when using the Amazon ECS console.
+    #
+    #   awslogs-datetime-format
+    #
+    #   : Required: No
+    #
+    #     This option defines a multiline start pattern in Python `strftime`
+    #     format. A log message consists of a line that matches the pattern
+    #     and any following lines that don’t match the pattern. The matched
+    #     line is the delimiter between log messages.
+    #
+    #     One example of a use case for using this format is for parsing
+    #     output such as a stack dump, which might otherwise be logged in
+    #     multiple entries. The correct pattern allows it to be captured in
+    #     a single entry.
+    #
+    #     For more information, see [awslogs-datetime-format][1].
+    #
+    #     You cannot configure both the `awslogs-datetime-format` and
+    #     `awslogs-multiline-pattern` options.
+    #
+    #     <note markdown="1"> Multiline logging performs regular expression parsing and matching
+    #     of all log messages. This might have a negative impact on logging
+    #     performance.
+    #
+    #      </note>
+    #
+    #   awslogs-multiline-pattern
+    #
+    #   : Required: No
+    #
+    #     This option defines a multiline start pattern that uses a regular
+    #     expression. A log message consists of a line that matches the
+    #     pattern and any following lines that don’t match the pattern. The
+    #     matched line is the delimiter between log messages.
+    #
+    #     For more information, see [awslogs-multiline-pattern][2].
+    #
+    #     This option is ignored if `awslogs-datetime-format` is also
+    #     configured.
+    #
+    #     You cannot configure both the `awslogs-datetime-format` and
+    #     `awslogs-multiline-pattern` options.
+    #
+    #     <note markdown="1"> Multiline logging performs regular expression parsing and matching
+    #     of all log messages. This might have a negative impact on logging
+    #     performance.
+    #
+    #      </note>
+    #
+    #   mode
+    #
+    #   : Required: No
+    #
+    #     Valid values: `non-blocking` \| `blocking`
+    #
+    #     This option defines the delivery mode of log messages from the
+    #     container to CloudWatch Logs. The delivery mode you choose affects
+    #     application availability when the flow of logs from container to
+    #     CloudWatch is interrupted.
+    #
+    #     If you use the `blocking` mode and the flow of logs to CloudWatch
+    #     is interrupted, calls from container code to write to the `stdout`
+    #     and `stderr` streams will block. The logging thread of the
+    #     application will block as a result. This may cause the application
+    #     to become unresponsive and lead to container healthcheck failure.
+    #
+    #     If you use the `non-blocking` mode, the container's logs are
+    #     instead stored in an in-memory intermediate buffer configured with
+    #     the `max-buffer-size` option. This prevents the application from
+    #     becoming unresponsive when logs cannot be sent to CloudWatch. We
+    #     recommend using this mode if you want to ensure service
+    #     availability and are okay with some log loss. For more
+    #     information, see [Preventing log loss with non-blocking mode in
+    #     the `awslogs` container log driver][3].
+    #
+    #   max-buffer-size
+    #
+    #   : Required: No
+    #
+    #     Default value: `1m`
+    #
+    #     When `non-blocking` mode is used, the `max-buffer-size` log option
+    #     controls the size of the buffer that's used for intermediate
+    #     message storage. Make sure to specify an adequate buffer size
+    #     based on your application. When the buffer fills up, further logs
+    #     cannot be stored. Logs that cannot be stored are lost.
+    #
+    #   To route logs using the `splunk` log router, you need to specify a
+    #   `splunk-token` and a `splunk-url`.
+    #
+    #   When you use the `awsfirelens` log router to route logs to an Amazon
+    #   Web Services Service or Amazon Web Services Partner Network
+    #   destination for log storage and analytics, you can set the
+    #   `log-driver-buffer-limit` option to limit the number of events that
+    #   are buffered in memory, before being sent to the log router
+    #   container. It can help to resolve potential log loss issue because
+    #   high throughput might result in memory running out for the buffer
+    #   inside of Docker.
+    #
+    #   Other options you can specify when using `awsfirelens` to route logs
+    #   depend on the destination. When you export logs to Amazon Data
+    #   Firehose, you can specify the Amazon Web Services Region with
+    #   `region` and a name for the log stream with `delivery_stream`.
+    #
+    #   When you export logs to Amazon Kinesis Data Streams, you can specify
+    #   an Amazon Web Services Region with `region` and a data stream name
+    #   with `stream`.
+    #
+    #   When you export logs to Amazon OpenSearch Service, you can specify
+    #   options like `Name`, `Host` (OpenSearch Service endpoint without
+    #   protocol), `Port`, `Index`, `Type`, `Aws_auth`, `Aws_region`,
+    #   `Suppress_Type_Name`, and `tls`.
+    #
+    #   When you export logs to Amazon S3, you can specify the bucket using
+    #   the `bucket` option. You can also specify `region`,
+    #   `total_file_size`, `upload_timeout`, and `use_put_object` as
+    #   options.
+    #
+    #   This parameter requires version 1.19 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/config/containers/logging/awslogs/#awslogs-datetime-format
+    #   [2]: https://docs.docker.com/config/containers/logging/awslogs/#awslogs-multiline-pattern
+    #   [3]: http://aws.amazon.com/blogs/containers/preventing-log-loss-with-non-blocking-mode-in-the-awslogs-container-log-driver/
     #   @return [Hash<String,String>]
     #
     # @!attribute [rw] secret_options

data/lib/aws-sdk-ecs.rb

@@ -55,7 +55,7 @@ module Aws::ECS
   autoload :EndpointProvider, 'aws-sdk-ecs/endpoint_provider'
   autoload :Endpoints, 'aws-sdk-ecs/endpoints'
 
-  GEM_VERSION = '1.161.0'
+  GEM_VERSION = '1.162.0'
 
 end
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-ecs
 version: !ruby/object:Gem::Version
-  version: 1.161.0
+  version: 1.162.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2024-09-24 00:00:00.000000000 Z
+date: 2024-10-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core