docs(client-batch): Added default_x86_64 and default_arm64 as values to the instanceTypes field.

Author: awstools

clients/client-batch/src/models/models_0.ts

@@ -545,8 +545,7 @@ export interface LaunchTemplateSpecificationOverride {
    *                <p>Must be a valid Amazon EC2 instance type or family.</p>
    *             </li>
    *             <li>
-   *                <p>
-   *                   <code>optimal</code> isn't allowed.</p>
+   *                <p>The following Batch <code>InstanceTypes</code> are not allowed: <code>optimal</code>, <code>default_x86_64</code>, and <code>default_arm64</code>.</p>
    *             </li>
    *             <li>
    *                <p>
@@ -765,9 +764,55 @@ export interface ComputeResource {
   /**
    * <p>The instances types that can be launched. You can specify instance families to launch any
    *    instance type within those families (for example, <code>c5</code> or <code>p3</code>), or you can
-   *    specify specific sizes within a family (such as <code>c5.8xlarge</code>). You can also choose
-   *     <code>optimal</code> to select instance types (from the C4, M4, and R4 instance families) that
-   *    match the demand of your job queues.</p>
+   *    specify specific sizes within a family (such as <code>c5.8xlarge</code>). </p>
+   *          <p>Batch can select the instance type for you if you choose one of the following:</p>
+   *          <ul>
+   *             <li>
+   *                <p>
+   *                   <code>optimal</code> to select instance types (from the <code>c4</code>, <code>m4</code>,
+   *     <code>r4</code>, <code>c5</code>, <code>m5</code>, and <code>r5</code>
+   *     instance families) that match the demand of your job queues. </p>
+   *             </li>
+   *             <li>
+   *                <p>
+   *                   <code>default_x86_64</code> to choose x86 based instance types (from the <code>m6i</code>,
+   *      <code>c6i</code>, <code>r6i</code>, and <code>c7i</code> instance families) that matches the resource demands of the job queue.</p>
+   *             </li>
+   *             <li>
+   *                <p>
+   *                   <code>default_arm64</code> to choose x86 based instance types (from the <code>m6g</code>,
+   *      <code>c6g</code>, <code>r6g</code>, and <code>c7g</code> instance families) that matches the resource demands of the job queue.</p>
+   *             </li>
+   *          </ul>
+   *          <note>
+   *             <p>Starting on 11/01/2025 the behavior of <code>optimal</code> is going to be changed to
+   *     match <code>default_x86_64</code>.
+   *
+   *     During the change your instance families could be updated to a newer
+   *     generation.
+   *     You do not need to perform any actions for the upgrade to
+   *     happen. For more information about change, see <a href="https://docs.aws.amazon.com/batch/latest/userguide/optimal-default-instance-troubleshooting.html">Optimal instance type configuration to
+   *      receive automatic instance family updates</a>.</p>
+   *          </note>
+   *          <note>
+   *             <p>Instance family availability varies by
+   *     Amazon Web Services Region.
+   *     For example, some Amazon Web Services Regions may not have any fourth generation instance families
+   *     but have fifth and sixth generation instance families.</p>
+   *             <p>When using <code>default_x86_64</code> or <code>default_arm64</code>
+   *     instance bundles, Batch selects instance families based on a balance of
+   *     cost-effectiveness and performance. While newer generation instances often provide
+   *     better price-performance, Batch may choose an earlier generation instance family
+   *     if it provides the optimal combination of availability, cost, and performance for
+   *     your workload. For example, in an
+   *     Amazon Web Services Region
+   *     where both c6i and c7i instances are available, Batch might select c6i instances
+   *     if they offer better cost-effectiveness for your specific job requirements. For more information on Batch instance types and Amazon Web Services Region availability, see <a href="https://docs.aws.amazon.com/batch/latest/userguide/instance-type-compute-table.html">Instance type compute table</a> in the <i>Batch User Guide</i>.</p>
+   *             <p>Batch periodically updates your instances in default bundles to newer,
+   *     more cost-effective options. Updates happen automatically without requiring any
+   *     action from you. Your workloads continue running during updates with no interruption
+   *    </p>
+   *          </note>
    *          <note>
    *             <p>This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.</p>
    *          </note>
@@ -776,11 +821,6 @@ export interface ComputeResource {
    *     share the same architecture. For example, you can't mix x86 and ARM instances in the same compute
    *     environment.</p>
    *          </note>
-   *          <note>
-   *             <p>Currently, <code>optimal</code> uses instance types from the C4, M4, and R4 instance
-   *     families. In Regions that don't have instance types from those instance families, instance types
-   *     from the C5, M5, and R5 instance families are used.</p>
-   *          </note>
    * @public
    */
   instanceTypes?: string[] | undefined;
@@ -7527,20 +7567,33 @@ export interface ListServiceJobsRequest {
   nextToken?: string | undefined;
 
   /**
-   * <p>The filters to apply to the service job list query. The filter names and values can be:</p>
-   *          <ul>
-   *             <li>
-   *                <p>name: <code>JOB_STATUS</code>
-   *                </p>
-   *                <p>values: <code>SUBMITTED | PENDING | RUNNABLE | STARTING | RUNNING | SUCCEEDED | FAILED | SCHEDULED</code>
-   *                </p>
-   *             </li>
-   *             <li>
-   *                <p>name: <code>JOB_NAME</code>
-   *                </p>
-   *                <p>values: case-insensitive matches for the job name. If a filter value ends with an asterisk (*), it matches any job name that begins with the string before the '*'.</p>
-   *             </li>
-   *          </ul>
+   * <p>The filter to apply to the query. Only one filter can be used at a time. When the filter
+   *            is used, <code>jobStatus</code> is ignored. The results are sorted by the <code>createdAt</code> field,
+   *            with the most recent jobs being first.</p>
+   *          <dl>
+   *             <dt>JOB_NAME</dt>
+   *             <dd>
+   *                <p>The value of the filter is a case-insensitive match for the job name. If the value
+   *                        ends with an asterisk (*), the filter matches any job name that begins with the string
+   *                        before the '*'. This corresponds to the <code>jobName</code> value. For example,
+   *                        <code>test1</code> matches both <code>Test1</code> and <code>test1</code>, and
+   *                        <code>test1*</code> matches both <code>test1</code> and <code>Test10</code>. When the
+   *                        <code>JOB_NAME</code> filter is used, the results are grouped by the job name and
+   *                        version.</p>
+   *             </dd>
+   *             <dt>BEFORE_CREATED_AT</dt>
+   *             <dd>
+   *                <p>The value for the filter is the time that's before the job was created. This
+   *                        corresponds to the <code>createdAt</code> value. The value is a string representation of
+   *                        the number of milliseconds since 00:00:00 UTC (midnight) on January 1, 1970.</p>
+   *             </dd>
+   *             <dt>AFTER_CREATED_AT</dt>
+   *             <dd>
+   *                <p>The value for the filter is the time that's after the job was created. This
+   *                        corresponds to the <code>createdAt</code> value. The value is a string representation of
+   *                        the number of milliseconds since 00:00:00 UTC (midnight) on January 1, 1970.</p>
+   *             </dd>
+   *          </dl>
    * @public
    */
   filters?: KeyValuesPair[] | undefined;
@@ -8708,12 +8761,55 @@ export interface ComputeResourceUpdate {
   /**
    * <p>The instances types that can be launched. You can specify instance families to launch any
    *    instance type within those families (for example, <code>c5</code> or <code>p3</code>), or you can
-   *    specify specific sizes within a family (such as <code>c5.8xlarge</code>). You can also choose
-   *     <code>optimal</code> to select instance types (from the C4, M4, and R4 instance families) that
-   *    match the demand of your job queues.</p>
-   *          <p>When updating a compute environment, changing this setting requires an infrastructure update
-   *    of the compute environment. For more information, 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>
+   *    specify specific sizes within a family (such as <code>c5.8xlarge</code>). </p>
+   *          <p>Batch can select the instance type for you if you choose one of the following:</p>
+   *          <ul>
+   *             <li>
+   *                <p>
+   *                   <code>optimal</code> to select instance types (from the <code>c4</code>, <code>m4</code>,
+   *     <code>r4</code>, <code>c5</code>, <code>m5</code>, and <code>r5</code>
+   *     instance families) that match the demand of your job queues. </p>
+   *             </li>
+   *             <li>
+   *                <p>
+   *                   <code>default_x86_64</code> to choose x86 based instance types (from the <code>m6i</code>,
+   *      <code>c6i</code>, <code>r6i</code>, and <code>c7i</code> instance families) that matches the resource demands of the job queue.</p>
+   *             </li>
+   *             <li>
+   *                <p>
+   *                   <code>default_arm64</code> to choose x86 based instance types (from the <code>m6g</code>,
+   *      <code>c6g</code>, <code>r6g</code>, and <code>c7g</code> instance families) that matches the resource demands of the job queue.</p>
+   *             </li>
+   *          </ul>
+   *          <note>
+   *             <p>Starting on 11/01/2025 the behavior of <code>optimal</code> is going to be changed to
+   *     match <code>default_x86_64</code>.
+   *
+   *     During the change your instance families could be updated to a newer
+   *     generation.
+   *     You do not need to perform any actions for the upgrade to
+   *     happen. For more information about change, see <a href="https://docs.aws.amazon.com/batch/latest/userguide/optimal-default-instance-troubleshooting.html">Optimal instance type configuration to
+   *      receive automatic instance family updates</a>.</p>
+   *          </note>
+   *          <note>
+   *             <p>Instance family availability varies by
+   *     Amazon Web Services Region.
+   *     For example, some Amazon Web Services Regions may not have any fourth generation instance families
+   *     but have fifth and sixth generation instance families.</p>
+   *             <p>When using <code>default_x86_64</code> or <code>default_arm64</code>
+   *     instance bundles, Batch selects instance families based on a balance of
+   *     cost-effectiveness and performance. While newer generation instances often provide
+   *     better price-performance, Batch may choose an earlier generation instance family
+   *     if it provides the optimal combination of availability, cost, and performance for
+   *     your workload. For example, in an
+   *     Amazon Web Services Region
+   *     where both c6i and c7i instances are available, Batch might select c6i instances
+   *     if they offer better cost-effectiveness for your specific job requirements. For more information on Batch instance types and Amazon Web Services Region availability, see <a href="https://docs.aws.amazon.com/batch/latest/userguide/instance-type-compute-table.html">Instance type compute table</a> in the <i>Batch User Guide</i>.</p>
+   *             <p>Batch periodically updates your instances in default bundles to newer,
+   *     more cost-effective options. Updates happen automatically without requiring any
+   *     action from you. Your workloads continue running during updates with no interruption
+   *    </p>
+   *          </note>
    *          <note>
    *             <p>This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.</p>
    *          </note>
@@ -8722,11 +8818,6 @@ export interface ComputeResourceUpdate {
    *     share the same architecture. For example, you can't mix x86 and ARM instances in the same compute
    *     environment.</p>
    *          </note>
-   *          <note>
-   *             <p>Currently, <code>optimal</code> uses instance types from the C4, M4, and R4 instance
-   *     families. In Regions that don't have instance types from those instance families, instance types
-   *     from the C5, M5, and R5 instance families are used.</p>
-   *          </note>
    * @public
    */
   instanceTypes?: string[] | undefined;
@@ -9069,9 +9160,7 @@ export interface UpdateConsumableResourceRequest {
 
   /**
    * <p>If this parameter is specified and two update requests with identical payloads and
-   *           <code>clientToken</code>s are received, these requests are considered the same request and
-   *           the second request is rejected. A <code>clientToken</code> is valid for 8 hours or until
-   *           one hour after the consumable resource is deleted, whichever is less.</p>
+   *           <code>clientToken</code>s are received, these requests are considered the same request. Both requests will succeed, but the update will only happen once. A <code>clientToken</code> is valid for 8 hours.</p>
    * @public
    */
   clientToken?: string | undefined;