@aws-sdk/client-batch 3.893.0 → 3.895.0

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

@@ -39,9 +39,6 @@ declare const CreateComputeEnvironmentCommand_base: {
  *       your managed compute environment. You can optionally set a maximum price so that Spot
  *       Instances only launch when the Spot Instance price is less than a specified percentage of the
  *       On-Demand price.</p>
- *          <note>
- *             <p>Multi-node parallel jobs aren't supported on Spot Instances.</p>
- *          </note>
  *          <p>In an unmanaged compute environment, you can manage your own EC2 compute resources and
  *       have flexibility with how you configure your compute resources. For example, you can use
  *       custom AMIs. However, you must verify that each of your AMIs meet the Amazon ECS container instance
@@ -52,75 +49,8 @@ declare const CreateComputeEnvironmentCommand_base: {
  *       cluster. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_container_instance.html">Launching an Amazon ECS container
  *         instance</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
  *          <note>
- *             <p>To create a compute environment that uses EKS resources, the caller must have
- *         permissions to call <code>eks:DescribeCluster</code>.</p>
- *          </note>
- *          <note>
  *             <p>Batch doesn't automatically upgrade the AMIs in a compute environment after it's
- *         created. For example, it also doesn't update the AMIs in your compute environment when a
- *         newer version of the Amazon ECS optimized AMI is available. You're responsible for the management
- *         of the guest operating system. This includes any updates and security patches. You're also
- *         responsible for any additional application software or utilities that you install on the
- *         compute resources. There are two ways to use a new AMI for your Batch jobs. The original
- *         method is to complete these steps:</p>
- *             <ol>
- *                <li>
- *                   <p>Create a new compute environment with the new AMI.</p>
- *                </li>
- *                <li>
- *                   <p>Add the compute environment to an existing job queue.</p>
- *                </li>
- *                <li>
- *                   <p>Remove the earlier compute environment from your job queue.</p>
- *                </li>
- *                <li>
- *                   <p>Delete the earlier compute environment.</p>
- *                </li>
- *             </ol>
- *             <p>In April 2022, Batch added enhanced support for updating compute environments. For
- *         more information, see <a href="https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html">Updating compute environments</a>.
- *         To use the enhanced updating of compute environments to update AMIs, follow these
- *         rules:</p>
- *             <ul>
- *                <li>
- *                   <p>Either don't set the service role (<code>serviceRole</code>) parameter or set it to
- *             the <b>AWSBatchServiceRole</b> service-linked role.</p>
- *                </li>
- *                <li>
- *                   <p>Set the allocation strategy (<code>allocationStrategy</code>) parameter to
- *               <code>BEST_FIT_PROGRESSIVE</code>, <code>SPOT_CAPACITY_OPTIMIZED</code>, or
- *               <code>SPOT_PRICE_CAPACITY_OPTIMIZED</code>.</p>
- *                </li>
- *                <li>
- *                   <p>Set the update to latest image version (<code>updateToLatestImageVersion</code>)
- *             parameter to <code>true</code>. The <code>updateToLatestImageVersion</code> parameter
- *             is used when you update a compute environment. This parameter is ignored when you create
- *             a compute environment.</p>
- *                </li>
- *                <li>
- *                   <p>Don't specify an AMI ID in <code>imageId</code>, <code>imageIdOverride</code> (in
- *               <a href="https://docs.aws.amazon.com/batch/latest/APIReference/API_Ec2Configuration.html">
- *                         <code>ec2Configuration</code>
- *                      </a>), or in the launch template
- *               (<code>launchTemplate</code>). In that case, Batch selects the latest Amazon ECS
- *             optimized AMI that's supported by Batch at the time the infrastructure update is
- *             initiated. Alternatively, you can specify the AMI ID in the <code>imageId</code> or
- *               <code>imageIdOverride</code> parameters, or the launch template identified by the
- *               <code>LaunchTemplate</code> properties. Changing any of these properties starts an
- *             infrastructure update. If the AMI ID is specified in the launch template, it can't be
- *             replaced by specifying an AMI ID in either the <code>imageId</code> or
- *               <code>imageIdOverride</code> parameters. It can only be replaced by specifying a
- *             different launch template, or if the launch template version is set to
- *               <code>$Default</code> or <code>$Latest</code>, by setting either a new default version
- *             for the launch template (if <code>$Default</code>) or by adding a new version to the
- *             launch template (if <code>$Latest</code>).</p>
- *                </li>
- *             </ul>
- *             <p>If these rules are followed, any update that starts an infrastructure update causes the
- *         AMI ID to be re-selected. If the <code>version</code> setting in the launch template
- *           (<code>launchTemplate</code>) is set to <code>$Latest</code> or <code>$Default</code>, the
- *         latest or default version of the launch template is evaluated up at the time of the
- *         infrastructure update, even if the <code>launchTemplate</code> wasn't updated.</p>
+ *       created. For more information on how to update a compute environment's AMI, see <a href="https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html">Updating compute environments</a> in the <i>Batch User Guide</i>.</p>
  *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

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

@@ -312,6 +312,13 @@ export interface Ec2Configuration {
      *       specified in an update, but neither an <code>imageId</code> nor a <code>imageIdOverride</code>
      *       parameter is specified, then the latest Amazon ECS optimized AMI for that image type that's
      *       supported by Batch is used.</p>
+     *                <important>
+     *                   <p>Amazon Web Services will end support for Amazon ECS optimized AL2-optimized and AL2-accelerated AMIs. Starting in January 2026, Batch will change
+     *        the default AMI for new Amazon ECS compute environments from Amazon Linux 2 to Amazon Linux 2023.
+     *        We recommend migrating Batch Amazon ECS compute environments to Amazon Linux 2023 to maintain
+     *        optimal performance and security. For more information on upgrading from AL2 to AL2023, see <a href="https://docs.aws.amazon.com/batch/latest/userguide/ecs-migration-2023.html">How to migrate
+     *         from ECS AL2 to ECS AL2023</a> in the <i>Batch User Guide</i>.</p>
+     *                </important>
      *                <dl>
      *                   <dt>ECS_AL2</dt>
      *                   <dd>
@@ -344,12 +351,6 @@ export interface Ec2Configuration {
      *                         <p>ECS_AL2023_NVIDIA doesn't support <code>p3</code> and <code>g3</code> instance types.</p>
      *                      </note>
      *                   </dd>
-     *                   <dt>ECS_AL1</dt>
-     *                   <dd>
-     *                      <p>
-     *                         <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html#alami">Amazon Linux</a>. Amazon Linux has
-     *          reached the end-of-life of standard support. For more information, see <a href="http://aws.amazon.com/amazon-linux-ami/">Amazon Linux AMI</a>.</p>
-     *                   </dd>
      *                </dl>
      *             </dd>
      *             <dt>EKS</dt>
@@ -368,7 +369,7 @@ export interface Ec2Configuration {
      *        using Batch-provided Amazon EKS optimized Amazon Linux 2 AMIs on your Amazon EKS compute
      *        environments beyond the 11/26/25 end-of-support date, these compute environments will no
      *        longer receive any new software updates, security patches, or bug fixes from
-     *        Amazon Web Services. For more information on upgrading from AL2 to AL2023, see <a href="">How to upgrade from EKS AL2 to EKS AL2023</a> in the <i>Batch User Guide</i>.</p>
+     *        Amazon Web Services. For more information on upgrading from AL2 to AL2023, see <a href="https://docs.aws.amazon.com/batch/latest/userguide/eks-migration-2023.html">How to upgrade from EKS AL2 to EKS AL2023</a> in the <i>Batch User Guide</i>.</p>
      *                </important>
      *                <dl>
      *                   <dt>EKS_AL2</dt>
@@ -620,6 +621,9 @@ export interface ComputeResource {
      *          <p> If you choose <code>SPOT</code>, you must also specify an Amazon EC2 Spot Fleet role with the
      *     <code>spotIamFleetRole</code> parameter. For more information, see <a href="https://docs.aws.amazon.com/batch/latest/userguide/spot_fleet_IAM_role.html">Amazon EC2 spot fleet role</a> in the
      *     <i>Batch User Guide</i>.</p>
+     *          <note>
+     *             <p>Multi-node parallel jobs aren't supported on Spot Instances.</p>
+     *          </note>
      * @public
      */
     type: CRType | undefined;
@@ -1066,6 +1070,10 @@ export interface CreateComputeEnvironmentRequest {
     tags?: Record<string, string> | undefined;
     /**
      * <p>The details for the Amazon EKS cluster that supports the compute environment.</p>
+     *          <note>
+     *             <p>To create a compute environment that uses EKS resources, the caller must have
+     *         permissions to call <code>eks:DescribeCluster</code>.</p>
+     *          </note>
      * @public
      */
     eksConfiguration?: EksConfiguration | undefined;
@@ -2318,7 +2326,7 @@ export interface LogConfiguration {
     /**
      * <p>The log driver to use for the container. The valid values that are listed for this parameter
      *    are log drivers that the Amazon ECS container agent can communicate with by default.</p>
-     *          <p>The supported log drivers are <code>awslogs</code>, <code>fluentd</code>, <code>gelf</code>,
+     *          <p>The supported log drivers are <code>awsfirelens</code>, <code>awslogs</code>, <code>fluentd</code>, <code>gelf</code>,
      *     <code>json-file</code>, <code>journald</code>, <code>logentries</code>, <code>syslog</code>, and
      *     <code>splunk</code>.</p>
      *          <note>
@@ -5213,7 +5221,8 @@ export interface EcsTaskDetails {
      */
     platformVersion?: string | undefined;
     /**
-     * <p>The IPC resource namespace to use for the containers in the task.</p>
+     * <p>The IPC resource namespace to use for the containers in the task. The valid values are
+     *    <code>host</code>, <code>task</code>, or <code>none</code>. For more information see <code>ipcMode</code> in <a href="https://docs.aws.amazon.com/batch/latest/APIReference/API_EcsTaskProperties.html">EcsTaskProperties</a>.</p>
      * @public
      */
     ipcMode?: string | undefined;
@@ -5228,7 +5237,8 @@ export interface EcsTaskDetails {
      */
     taskRoleArn?: string | undefined;
     /**
-     * <p>The process namespace to use for the containers in the task.</p>
+     * <p>The process namespace to use for the containers in the task. The valid values are
+     *    <code>host</code>, or <code>task</code>. For more information see <code>pidMode</code> in <a href="https://docs.aws.amazon.com/batch/latest/APIReference/API_EcsTaskProperties.html">EcsTaskProperties</a>.</p>
      * @public
      */
     pidMode?: string | undefined;
@@ -7692,9 +7702,9 @@ export interface SubmitServiceJobRequest {
      */
     serviceJobType: ServiceJobType | undefined;
     /**
-     * <p>The share identifier for the service job. Don't specify this parameter if the job queue doesn't have a fair-
-     *            share scheduling policy. If the job queue has a fair-share scheduling policy, then this parameter
-     *            must be specified.</p>
+     * <p>The share identifier for the service job. Don't specify this parameter if the job
+     *             queue doesn't have a fair-share scheduling policy. If the job queue has a fair-share
+     *             scheduling policy, then this parameter must be specified.</p>
      * @public
      */
     shareIdentifier?: string | undefined;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@aws-sdk/client-batch",
   "description": "AWS SDK for JavaScript Batch Client for Node.js, Browser and React Native",
-  "version": "3.893.0",
+  "version": "3.895.0",
   "scripts": {
     "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
     "build:cjs": "node ../../scripts/compilation/inline client-batch",
@@ -20,17 +20,17 @@
   "dependencies": {
     "@aws-crypto/sha256-browser": "5.2.0",
     "@aws-crypto/sha256-js": "5.2.0",
-    "@aws-sdk/core": "3.893.0",
-    "@aws-sdk/credential-provider-node": "3.893.0",
+    "@aws-sdk/core": "3.894.0",
+    "@aws-sdk/credential-provider-node": "3.895.0",
     "@aws-sdk/middleware-host-header": "3.893.0",
     "@aws-sdk/middleware-logger": "3.893.0",
     "@aws-sdk/middleware-recursion-detection": "3.893.0",
-    "@aws-sdk/middleware-user-agent": "3.893.0",
+    "@aws-sdk/middleware-user-agent": "3.895.0",
     "@aws-sdk/region-config-resolver": "3.893.0",
     "@aws-sdk/types": "3.893.0",
-    "@aws-sdk/util-endpoints": "3.893.0",
+    "@aws-sdk/util-endpoints": "3.895.0",
     "@aws-sdk/util-user-agent-browser": "3.893.0",
-    "@aws-sdk/util-user-agent-node": "3.893.0",
+    "@aws-sdk/util-user-agent-node": "3.895.0",
     "@smithy/config-resolver": "^4.2.2",
     "@smithy/core": "^3.11.1",
     "@smithy/fetch-http-handler": "^5.2.1",