@aws-sdk/client-ecs 3.540.0 → 3.541.0

package/dist-types/commands/CreateServiceCommand.d.ts

@@ -31,7 +31,7 @@ declare const CreateServiceCommand_base: {
  * 			Amazon ECS runs another copy of the task in the specified cluster. To update an existing
  * 			service, see the <a>UpdateService</a> action.</p>
  *          <note>
- *             <p>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. </p>
+ *             <p>The following change began on March 21, 2024. When the task definition revision is not specified, Amazon ECS resolves the task definition revision before it authorizes the task definition.</p>
  *          </note>
  *          <p>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
@@ -106,9 +106,11 @@ declare const CreateServiceCommand_base: {
  *          <p>When creating a service that uses the <code>EXTERNAL</code> deployment controller, you
  * 			can specify only parameters that aren't controlled at the task set level. The only
  * 			required parameter is the service name. You control your services using the <a>CreateTaskSet</a> operation. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS deployment types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- *          <p>When the service scheduler launches new tasks, it determines task placement. For
- * 			information about task placement and task placement strategies, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html">Amazon ECS
- * 				task placement</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ *          <p>When the service scheduler launches new tasks, it determines task placement. For information
+ * 			about task placement and task placement strategies, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html">Amazon ECS
+ * 				task placement</a> in the <i>Amazon Elastic Container Service Developer Guide</i>
+ *          </p>
+ *          <p>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. </p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/CreateTaskSetCommand.d.ts

@@ -30,8 +30,11 @@ declare const CreateTaskSetCommand_base: {
  * 			uses the <code>EXTERNAL</code> deployment controller type. For more information, see
  * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html">Amazon ECS deployment
  * 				types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ *          <note>
+ *             <p>The following change began on March 21, 2024. When the task definition revision is not specified, Amazon ECS resolves the task definition revision before it authorizes the task definition.</p>
+ *          </note>
  *          <p>For information about the maximum number of task sets and otther quotas, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html">Amazon ECS
- * 				service quotas</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ * 			service quotas</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/RunTaskCommand.d.ts

@@ -27,14 +27,15 @@ declare const RunTaskCommand_base: {
 };
 /**
  * <p>Starts a new task using the specified task definition.</p>
+ *          <note>
+ *             <p>The following change began on March 21, 2024. When the task definition revision is not specified, Amazon ECS resolves the task definition revision before it authorizes the task definition.</p>
+ *          </note>
  *          <p>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
  * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html">Scheduling Tasks</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
  *          <p>Alternatively, you can use <a>StartTask</a> to use your own scheduler or
  * 			place tasks manually on specific container instances.</p>
- *          <note>
- *             <p>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. </p>
- *          </note>
+ *          <p>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. </p>
  *          <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or
  * 			updating a service. For more infomation, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types">Amazon EBS volumes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
  *          <p>The Amazon ECS API follows an eventual consistency model. This is because of the

package/dist-types/commands/StartTaskCommand.d.ts

@@ -29,8 +29,9 @@ declare const StartTaskCommand_base: {
  * <p>Starts a new task from the specified task definition on the specified container
  * 			instance or instances.</p>
  *          <note>
- *             <p>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. </p>
+ *             <p>The following change began on March 21, 2024. When the task definition revision is not specified, Amazon ECS resolves the task definition revision before it authorizes the task definition.</p>
  *          </note>
+ *          <p>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. </p>
  *          <p>Alternatively, you can use <a>RunTask</a> to place tasks for you. For more
  * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html">Scheduling Tasks</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
  *          <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or

package/dist-types/commands/UpdateServiceCommand.d.ts

@@ -27,6 +27,9 @@ declare const UpdateServiceCommand_base: {
 };
 /**
  * <p>Modifies the parameters of a service.</p>
+ *          <note>
+ *             <p>The following change began on March 21, 2024. When the task definition revision is not specified, Amazon ECS resolves the task definition revision before it authorizes the task definition.</p>
+ *          </note>
  *          <p>For services using the rolling update (<code>ECS</code>) you can update the desired
  * 			count, deployment configuration, network configuration, load balancers, service
  * 			registries, enable ECS managed tags option, propagate tags option, task placement

package/dist-types/models/models_0.d.ts

@@ -852,10 +852,10 @@ export interface Attachment {
      *          <p>For Service Connect services, this includes <code>portName</code>,
      * 				<code>clientAliases</code>, <code>discoveryName</code>, and
      * 				<code>ingressPortOverride</code>.</p>
-     *          <p>For elastic block storage, this includes <code>roleArn</code>, <code>encrypted</code>,
-     * 				<code>filesystemType</code>, <code>iops</code>, <code>kmsKeyId</code>,
-     * 				<code>sizeInGiB</code>, <code>snapshotId</code>, <code>tagSpecifications</code>,
-     * 				<code>throughput</code>, and <code>volumeType</code>.</p>
+     *          <p>For Elastic Block Storage, this includes <code>roleArn</code>,
+     * 				<code>deleteOnTermination</code>, <code>volumeName</code>, <code>volumeId</code>,
+     * 			and <code>statusReason</code> (only when the attachment fails to create or
+     * 			attach).</p>
      * @public
      */
     details?: KeyValuePair[];
@@ -2368,7 +2368,7 @@ export interface CreateServiceRequest {
      *          <note>
      *             <p>Fargate Spot infrastructure is available for use but a capacity provider
      * 				strategy must be used. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-capacity-providers.html">Fargate capacity providers</a> in the
-     * 					<i>Amazon ECS User Guide for Fargate</i>.</p>
+     * 					<i>Amazon ECS Developer Guide</i>.</p>
      *          </note>
      *          <p>The <code>EC2</code> launch type runs your tasks on Amazon EC2 instances registered to your
      * 			cluster.</p>
@@ -2394,8 +2394,7 @@ export interface CreateServiceRequest {
      * <p>The platform version that your tasks in the service are running on. A platform version
      * 			is specified only for tasks using the Fargate launch type. If one isn't
      * 			specified, the <code>LATEST</code> platform version is used. For more information, see
-     * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate platform
-     * 				versions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+     * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate platform versions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      * @public
      */
     platformVersion?: string;
@@ -2460,13 +2459,11 @@ export interface CreateServiceRequest {
      *          <p>If you do not use an Elastic Load Balancing, we recommend that you use the <code>startPeriod</code> in
      * 			the task definition health check parameters. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_HealthCheck.html">Health
      * 				check</a>.</p>
-     *          <p>If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you
-     * 			can specify a health check grace period of up to
-     * 			2,147,483,647
-     * 			seconds (about 69 years). During that time, the Amazon ECS service
-     * 			scheduler ignores health check status. This grace period can prevent the service
-     * 			scheduler from marking tasks as unhealthy and stopping them before they have time to
-     * 			come up.</p>
+     *          <p>If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can
+     * 			specify a health check grace period of up to 2,147,483,647 seconds (about 69 years).
+     * 			During that time, the Amazon ECS service scheduler ignores health check status. This grace
+     * 			period can prevent the service scheduler from marking tasks as unhealthy and stopping
+     * 			them before they have time to come up.</p>
      * @public
      */
     healthCheckGracePeriodSeconds?: number;
@@ -2559,6 +2556,7 @@ export interface CreateServiceRequest {
      * <p>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 <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_TagResource.html">TagResource</a> API action.</p>
+     *          <p>You must set this to a value other than <code>NONE</code> when you use Cost Explorer. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/usage-reports.html">Amazon ECS usage reports</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      *          <p>The default is <code>NONE</code>.</p>
      * @public
      */
@@ -4006,8 +4004,8 @@ export type EnvironmentFileType = (typeof EnvironmentFileType)[keyof typeof Envi
  * 			parameter in a container definition, they take precedence over the variables contained
  * 			within an environment file. If multiple 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 <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/taskdef-envfiles.html">Specifying environment
- * 				variables</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ * 			variable names. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/use-environment-file.html">Use a file to pass environment variables to a container</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ *          <p>Environment variable files are objects in Amazon S3 and all Amazon S3 security considerations apply. </p>
  *          <p>You must use the following platforms for the Fargate launch type:</p>
  *          <ul>
  *             <li>
@@ -4039,7 +4037,8 @@ export interface EnvironmentFile {
      */
     value: string | undefined;
     /**
-     * <p>The file type to use. The only supported value is <code>s3</code>.</p>
+     * <p>The file type to use.  Environment files are objects in Amazon S3. The only supported value is
+     * 				<code>s3</code>.</p>
      * @public
      */
     type: EnvironmentFileType | undefined;
@@ -4119,6 +4118,8 @@ export interface FirelensConfiguration {
  * 			DescribeTasks API operation or when viewing the task details in the console.</p>
  *          <p>The health check is designed to make sure that your containers survive agent restarts,
  * 			upgrades, or temporary unavailability.</p>
+ *          <p>Amazon ECS performs health checks on containers with the default that launched the
+ * 			container instance or the task.</p>
  *          <p>The following describes the possible <code>healthStatus</code> values for a
  * 			container:</p>
  *          <ul>
@@ -4298,8 +4299,7 @@ export interface HealthCheck {
     startPeriod?: number;
 }
 /**
- * <p>The Linux capabilities for the container that are added to or dropped from the default
- * 			configuration provided by Docker. For more information about the default capabilities
+ * <p>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 <a href="https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities">Runtime privilege and Linux capabilities</a> in the <i>Docker run
  * 				reference</i>. For more detailed information about these Linux capabilities,
  * 			see the <a href="http://man7.org/linux/man-pages/man7/capabilities.7.html">capabilities(7)</a> Linux manual page.</p>
@@ -5673,8 +5673,8 @@ export interface ContainerDefinition {
  */
 export interface EphemeralStorage {
     /**
-     * <p>The total amount, in GiB, of ephemeral storage to set for the task. The minimum
-     * 			supported value is <code>21</code> GiB and the maximum supported value is
+     * <p>The total amount, in GiB, of ephemeral storage to set for the task. The minimum supported
+     * 			value is <code>20</code> GiB and the maximum supported value is
      * 				<code>200</code> GiB.</p>
      * @public
      */

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@aws-sdk/client-ecs",
   "description": "AWS SDK for JavaScript Ecs Client for Node.js, Browser and React Native",
-  "version": "3.540.0",
+  "version": "3.541.0",
   "scripts": {
     "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
     "build:cjs": "node ../../scripts/compilation/inline client-ecs",