@aws-sdk/client-batch 3.893.0 → 3.894.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/dist-types/commands/CreateComputeEnvironmentCommand.d.ts +1 -71
  2. package/dist-types/models/models_0.d.ts +23 -13
  3. package/package.json +5 -5
package/dist-types/commands/CreateComputeEnvironmentCommand.d.ts CHANGED
@@ -39,9 +39,6 @@ declare const CreateComputeEnvironmentCommand_base: {
39
39
  * your managed compute environment. You can optionally set a maximum price so that Spot
40
40
  * Instances only launch when the Spot Instance price is less than a specified percentage of the
41
41
  * On-Demand price.</p>
42
- * <note>
43
- * <p>Multi-node parallel jobs aren't supported on Spot Instances.</p>
44
- * </note>
45
42
  * <p>In an unmanaged compute environment, you can manage your own EC2 compute resources and
46
43
  * have flexibility with how you configure your compute resources. For example, you can use
47
44
  * 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: {
52
49
  * cluster. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_container_instance.html">Launching an Amazon ECS container
53
50
  * instance</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
54
51
  * <note>
55
- * <p>To create a compute environment that uses EKS resources, the caller must have
56
- * permissions to call <code>eks:DescribeCluster</code>.</p>
57
- * </note>
58
- * <note>
59
52
  * <p>Batch doesn't automatically upgrade the AMIs in a compute environment after it's
60
- * created. For example, it also doesn't update the AMIs in your compute environment when a
61
- * newer version of the Amazon ECS optimized AMI is available. You're responsible for the management
62
- * of the guest operating system. This includes any updates and security patches. You're also
63
- * responsible for any additional application software or utilities that you install on the
64
- * compute resources. There are two ways to use a new AMI for your Batch jobs. The original
65
- * method is to complete these steps:</p>
66
- * <ol>
67
- * <li>
68
- * <p>Create a new compute environment with the new AMI.</p>
69
- * </li>
70
- * <li>
71
- * <p>Add the compute environment to an existing job queue.</p>
72
- * </li>
73
- * <li>
74
- * <p>Remove the earlier compute environment from your job queue.</p>
75
- * </li>
76
- * <li>
77
- * <p>Delete the earlier compute environment.</p>
78
- * </li>
79
- * </ol>
80
- * <p>In April 2022, Batch added enhanced support for updating compute environments. For
81
- * more information, see <a href="https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html">Updating compute environments</a>.
82
- * To use the enhanced updating of compute environments to update AMIs, follow these
83
- * rules:</p>
84
- * <ul>
85
- * <li>
86
- * <p>Either don't set the service role (<code>serviceRole</code>) parameter or set it to
87
- * the <b>AWSBatchServiceRole</b> service-linked role.</p>
88
- * </li>
89
- * <li>
90
- * <p>Set the allocation strategy (<code>allocationStrategy</code>) parameter to
91
- * <code>BEST_FIT_PROGRESSIVE</code>, <code>SPOT_CAPACITY_OPTIMIZED</code>, or
92
- * <code>SPOT_PRICE_CAPACITY_OPTIMIZED</code>.</p>
93
- * </li>
94
- * <li>
95
- * <p>Set the update to latest image version (<code>updateToLatestImageVersion</code>)
96
- * parameter to <code>true</code>. The <code>updateToLatestImageVersion</code> parameter
97
- * is used when you update a compute environment. This parameter is ignored when you create
98
- * a compute environment.</p>
99
- * </li>
100
- * <li>
101
- * <p>Don't specify an AMI ID in <code>imageId</code>, <code>imageIdOverride</code> (in
102
- * <a href="https://docs.aws.amazon.com/batch/latest/APIReference/API_Ec2Configuration.html">
103
- * <code>ec2Configuration</code>
104
- * </a>), or in the launch template
105
- * (<code>launchTemplate</code>). In that case, Batch selects the latest Amazon ECS
106
- * optimized AMI that's supported by Batch at the time the infrastructure update is
107
- * initiated. Alternatively, you can specify the AMI ID in the <code>imageId</code> or
108
- * <code>imageIdOverride</code> parameters, or the launch template identified by the
109
- * <code>LaunchTemplate</code> properties. Changing any of these properties starts an
110
- * infrastructure update. If the AMI ID is specified in the launch template, it can't be
111
- * replaced by specifying an AMI ID in either the <code>imageId</code> or
112
- * <code>imageIdOverride</code> parameters. It can only be replaced by specifying a
113
- * different launch template, or if the launch template version is set to
114
- * <code>$Default</code> or <code>$Latest</code>, by setting either a new default version
115
- * for the launch template (if <code>$Default</code>) or by adding a new version to the
116
- * launch template (if <code>$Latest</code>).</p>
117
- * </li>
118
- * </ul>
119
- * <p>If these rules are followed, any update that starts an infrastructure update causes the
120
- * AMI ID to be re-selected. If the <code>version</code> setting in the launch template
121
- * (<code>launchTemplate</code>) is set to <code>$Latest</code> or <code>$Default</code>, the
122
- * latest or default version of the launch template is evaluated up at the time of the
123
- * infrastructure update, even if the <code>launchTemplate</code> wasn't updated.</p>
53
+ * 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>
124
54
  * </note>
125
55
  * @example
126
56
  * Use a bare-bones client and the command you need to make an API call.
package/dist-types/models/models_0.d.ts CHANGED
@@ -312,6 +312,13 @@ export interface Ec2Configuration {
312
312
  * specified in an update, but neither an <code>imageId</code> nor a <code>imageIdOverride</code>
313
313
  * parameter is specified, then the latest Amazon ECS optimized AMI for that image type that's
314
314
  * supported by Batch is used.</p>
315
+ * <important>
316
+ * <p>Amazon Web Services will end support for Amazon ECS optimized AL2-optimized and AL2-accelerated AMIs. Starting in January 2026, Batch will change
317
+ * the default AMI for new Amazon ECS compute environments from Amazon Linux 2 to Amazon Linux 2023.
318
+ * We recommend migrating Batch Amazon ECS compute environments to Amazon Linux 2023 to maintain
319
+ * 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
320
+ * from ECS AL2 to ECS AL2023</a> in the <i>Batch User Guide</i>.</p>
321
+ * </important>
315
322
  * <dl>
316
323
  * <dt>ECS_AL2</dt>
317
324
  * <dd>
@@ -344,12 +351,6 @@ export interface Ec2Configuration {
344
351
  * <p>ECS_AL2023_NVIDIA doesn't support <code>p3</code> and <code>g3</code> instance types.</p>
345
352
  * </note>
346
353
  * </dd>
347
- * <dt>ECS_AL1</dt>
348
- * <dd>
349
- * <p>
350
- * <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html#alami">Amazon Linux</a>. Amazon Linux has
351
- * 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>
352
- * </dd>
353
354
  * </dl>
354
355
  * </dd>
355
356
  * <dt>EKS</dt>
@@ -368,7 +369,7 @@ export interface Ec2Configuration {
368
369
  * using Batch-provided Amazon EKS optimized Amazon Linux 2 AMIs on your Amazon EKS compute
369
370
  * environments beyond the 11/26/25 end-of-support date, these compute environments will no
370
371
  * longer receive any new software updates, security patches, or bug fixes from
371
- * 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>
372
+ * 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>
372
373
  * </important>
373
374
  * <dl>
374
375
  * <dt>EKS_AL2</dt>
@@ -620,6 +621,9 @@ export interface ComputeResource {
620
621
  * <p> If you choose <code>SPOT</code>, you must also specify an Amazon EC2 Spot Fleet role with the
621
622
  * <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
622
623
  * <i>Batch User Guide</i>.</p>
624
+ * <note>
625
+ * <p>Multi-node parallel jobs aren't supported on Spot Instances.</p>
626
+ * </note>
623
627
  * @public
624
628
  */
625
629
  type: CRType | undefined;
@@ -1066,6 +1070,10 @@ export interface CreateComputeEnvironmentRequest {
1066
1070
  tags?: Record<string, string> | undefined;
1067
1071
  /**
1068
1072
  * <p>The details for the Amazon EKS cluster that supports the compute environment.</p>
1073
+ * <note>
1074
+ * <p>To create a compute environment that uses EKS resources, the caller must have
1075
+ * permissions to call <code>eks:DescribeCluster</code>.</p>
1076
+ * </note>
1069
1077
  * @public
1070
1078
  */
1071
1079
  eksConfiguration?: EksConfiguration | undefined;
@@ -2318,7 +2326,7 @@ export interface LogConfiguration {
2318
2326
  /**
2319
2327
  * <p>The log driver to use for the container. The valid values that are listed for this parameter
2320
2328
  * are log drivers that the Amazon ECS container agent can communicate with by default.</p>
2321
- * <p>The supported log drivers are <code>awslogs</code>, <code>fluentd</code>, <code>gelf</code>,
2329
+ * <p>The supported log drivers are <code>awsfirelens</code>, <code>awslogs</code>, <code>fluentd</code>, <code>gelf</code>,
2322
2330
  * <code>json-file</code>, <code>journald</code>, <code>logentries</code>, <code>syslog</code>, and
2323
2331
  * <code>splunk</code>.</p>
2324
2332
  * <note>
@@ -5213,7 +5221,8 @@ export interface EcsTaskDetails {
5213
5221
  */
5214
5222
  platformVersion?: string | undefined;
5215
5223
  /**
5216
- * <p>The IPC resource namespace to use for the containers in the task.</p>
5224
+ * <p>The IPC resource namespace to use for the containers in the task. The valid values are
5225
+ * <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>
5217
5226
  * @public
5218
5227
  */
5219
5228
  ipcMode?: string | undefined;
@@ -5228,7 +5237,8 @@ export interface EcsTaskDetails {
5228
5237
  */
5229
5238
  taskRoleArn?: string | undefined;
5230
5239
  /**
5231
- * <p>The process namespace to use for the containers in the task.</p>
5240
+ * <p>The process namespace to use for the containers in the task. The valid values are
5241
+ * <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>
5232
5242
  * @public
5233
5243
  */
5234
5244
  pidMode?: string | undefined;
@@ -7692,9 +7702,9 @@ export interface SubmitServiceJobRequest {
7692
7702
  */
7693
7703
  serviceJobType: ServiceJobType | undefined;
7694
7704
  /**
7695
- * <p>The share identifier for the service job. Don't specify this parameter if the job queue doesn't have a fair-
7696
- * share scheduling policy. If the job queue has a fair-share scheduling policy, then this parameter
7697
- * must be specified.</p>
7705
+ * <p>The share identifier for the service job. Don't specify this parameter if the job
7706
+ * queue doesn't have a fair-share scheduling policy. If the job queue has a fair-share
7707
+ * scheduling policy, then this parameter must be specified.</p>
7698
7708
  * @public
7699
7709
  */
7700
7710
  shareIdentifier?: string | undefined;
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@aws-sdk/client-batch",
3
3
  "description": "AWS SDK for JavaScript Batch Client for Node.js, Browser and React Native",
4
- "version": "3.893.0",
4
+ "version": "3.894.0",
5
5
  "scripts": {
6
6
  "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
7
7
  "build:cjs": "node ../../scripts/compilation/inline client-batch",
@@ -20,17 +20,17 @@
20
20
  "dependencies": {
21
21
  "@aws-crypto/sha256-browser": "5.2.0",
22
22
  "@aws-crypto/sha256-js": "5.2.0",
23
- "@aws-sdk/core": "3.893.0",
24
- "@aws-sdk/credential-provider-node": "3.893.0",
23
+ "@aws-sdk/core": "3.894.0",
24
+ "@aws-sdk/credential-provider-node": "3.894.0",
25
25
  "@aws-sdk/middleware-host-header": "3.893.0",
26
26
  "@aws-sdk/middleware-logger": "3.893.0",
27
27
  "@aws-sdk/middleware-recursion-detection": "3.893.0",
28
- "@aws-sdk/middleware-user-agent": "3.893.0",
28
+ "@aws-sdk/middleware-user-agent": "3.894.0",
29
29
  "@aws-sdk/region-config-resolver": "3.893.0",
30
30
  "@aws-sdk/types": "3.893.0",
31
31
  "@aws-sdk/util-endpoints": "3.893.0",
32
32
  "@aws-sdk/util-user-agent-browser": "3.893.0",
33
- "@aws-sdk/util-user-agent-node": "3.893.0",
33
+ "@aws-sdk/util-user-agent-node": "3.894.0",
34
34
  "@smithy/config-resolver": "^4.2.2",
35
35
  "@smithy/core": "^3.11.1",
36
36
  "@smithy/fetch-http-handler": "^5.2.1",