feat: update AWS API models

Author: aws-sdk-kotlin-ci

codegen/sdk/aws-models/batch.json

@@ -1913,7 +1913,7 @@
                 "instanceTypes": {
                     "target": "com.amazonaws.batch#StringList",
                     "traits": {
-                        "smithy.api#documentation": "<p>The instances types that can be launched. You can specify instance families to launch any\n   instance type within those families (for example, <code>c5</code> or <code>p3</code>), or you can\n   specify specific sizes within a family (such as <code>c5.8xlarge</code>). You can also choose\n    <code>optimal</code> to select instance types (from the C4, M4, and R4 instance families) that\n   match the demand of your job queues.</p>\n         <note>\n            <p>This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.</p>\n         </note>\n         <note>\n            <p>When you create a compute environment, the instance types that you select for the compute environment must\n    share the same architecture. For example, you can't mix x86 and ARM instances in the same compute\n    environment.</p>\n         </note>\n         <note>\n            <p>Currently, <code>optimal</code> uses instance types from the C4, M4, and R4 instance\n    families. In Regions that don't have instance types from those instance families, instance types\n    from the C5, M5, and R5 instance families are used.</p>\n         </note>"
+                        "smithy.api#documentation": "<p>The instances types that can be launched. You can specify instance families to launch any\n   instance type within those families (for example, <code>c5</code> or <code>p3</code>), or you can\n   specify specific sizes within a family (such as <code>c5.8xlarge</code>). </p>\n         <p>Batch can select the instance type for you if you choose one of the following:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>optimal</code> to select instance types (from the <code>c4</code>, <code>m4</code>,\n    <code>r4</code>, <code>c5</code>, <code>m5</code>, and <code>r5</code>\n    instance families) that match the demand of your job queues. </p>\n            </li>\n            <li>\n               <p>\n                  <code>default_x86_64</code> to choose x86 based instance types (from the <code>m6i</code>,\n     <code>c6i</code>, <code>r6i</code>, and <code>c7i</code> instance families) that matches the resource demands of the job queue.</p>\n            </li>\n            <li>\n               <p>\n                  <code>default_arm64</code> to choose x86 based instance types (from the <code>m6g</code>,\n     <code>c6g</code>, <code>r6g</code>, and <code>c7g</code> instance families) that matches the resource demands of the job queue.</p>\n            </li>\n         </ul>\n         <note>\n            <p>Starting on 11/01/2025 the behavior of <code>optimal</code> is going to be changed to\n    match <code>default_x86_64</code>.\n    \n    During the change your instance families could be updated to a newer\n    generation.\n    You do not need to perform any actions for the upgrade to\n    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\n     receive automatic instance family updates</a>.</p>\n         </note>\n         <note>\n            <p>Instance family availability varies by\n    Amazon Web Services Region.\n    For example, some Amazon Web Services Regions may not have any fourth generation instance families\n    but have fifth and sixth generation instance families.</p>\n            <p>When using <code>default_x86_64</code> or <code>default_arm64</code>\n    instance bundles, Batch selects instance families based on a balance of\n    cost-effectiveness and performance. While newer generation instances often provide\n    better price-performance, Batch may choose an earlier generation instance family\n    if it provides the optimal combination of availability, cost, and performance for\n    your workload. For example, in an\n    Amazon Web Services Region\n    where both c6i and c7i instances are available, Batch might select c6i instances\n    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>\n            <p>Batch periodically updates your instances in default bundles to newer,\n    more cost-effective options. Updates happen automatically without requiring any\n    action from you. Your workloads continue running during updates with no interruption\n   </p>\n         </note>\n         <note>\n            <p>This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.</p>\n         </note>\n         <note>\n            <p>When you create a compute environment, the instance types that you select for the compute environment must\n    share the same architecture. For example, you can't mix x86 and ARM instances in the same compute\n    environment.</p>\n         </note>"
                     }
                 },
                 "imageId": {
@@ -2034,7 +2034,7 @@
                 "instanceTypes": {
                     "target": "com.amazonaws.batch#StringList",
                     "traits": {
-                        "smithy.api#documentation": "<p>The instances types that can be launched. You can specify instance families to launch any\n   instance type within those families (for example, <code>c5</code> or <code>p3</code>), or you can\n   specify specific sizes within a family (such as <code>c5.8xlarge</code>). You can also choose\n    <code>optimal</code> to select instance types (from the C4, M4, and R4 instance families) that\n   match the demand of your job queues.</p>\n         <p>When updating a compute environment, changing this setting requires an infrastructure update\n   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\n    <i>Batch User Guide</i>.</p>\n         <note>\n            <p>This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.</p>\n         </note>\n         <note>\n            <p>When you create a compute environment, the instance types that you select for the compute environment must\n    share the same architecture. For example, you can't mix x86 and ARM instances in the same compute\n    environment.</p>\n         </note>\n         <note>\n            <p>Currently, <code>optimal</code> uses instance types from the C4, M4, and R4 instance\n    families. In Regions that don't have instance types from those instance families, instance types\n    from the C5, M5, and R5 instance families are used.</p>\n         </note>"
+                        "smithy.api#documentation": "<p>The instances types that can be launched. You can specify instance families to launch any\n   instance type within those families (for example, <code>c5</code> or <code>p3</code>), or you can\n   specify specific sizes within a family (such as <code>c5.8xlarge</code>). </p>\n         <p>Batch can select the instance type for you if you choose one of the following:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>optimal</code> to select instance types (from the <code>c4</code>, <code>m4</code>,\n    <code>r4</code>, <code>c5</code>, <code>m5</code>, and <code>r5</code>\n    instance families) that match the demand of your job queues. </p>\n            </li>\n            <li>\n               <p>\n                  <code>default_x86_64</code> to choose x86 based instance types (from the <code>m6i</code>,\n     <code>c6i</code>, <code>r6i</code>, and <code>c7i</code> instance families) that matches the resource demands of the job queue.</p>\n            </li>\n            <li>\n               <p>\n                  <code>default_arm64</code> to choose x86 based instance types (from the <code>m6g</code>,\n     <code>c6g</code>, <code>r6g</code>, and <code>c7g</code> instance families) that matches the resource demands of the job queue.</p>\n            </li>\n         </ul>\n         <note>\n            <p>Starting on 11/01/2025 the behavior of <code>optimal</code> is going to be changed to\n    match <code>default_x86_64</code>.\n    \n    During the change your instance families could be updated to a newer\n    generation.\n    You do not need to perform any actions for the upgrade to\n    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\n     receive automatic instance family updates</a>.</p>\n         </note>\n         <note>\n            <p>Instance family availability varies by\n    Amazon Web Services Region.\n    For example, some Amazon Web Services Regions may not have any fourth generation instance families\n    but have fifth and sixth generation instance families.</p>\n            <p>When using <code>default_x86_64</code> or <code>default_arm64</code>\n    instance bundles, Batch selects instance families based on a balance of\n    cost-effectiveness and performance. While newer generation instances often provide\n    better price-performance, Batch may choose an earlier generation instance family\n    if it provides the optimal combination of availability, cost, and performance for\n    your workload. For example, in an\n    Amazon Web Services Region\n    where both c6i and c7i instances are available, Batch might select c6i instances\n    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>\n            <p>Batch periodically updates your instances in default bundles to newer,\n    more cost-effective options. Updates happen automatically without requiring any\n    action from you. Your workloads continue running during updates with no interruption\n   </p>\n         </note>\n         <note>\n            <p>This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.</p>\n         </note>\n         <note>\n            <p>When you create a compute environment, the instance types that you select for the compute environment must\n    share the same architecture. For example, you can't mix x86 and ARM instances in the same compute\n    environment.</p>\n         </note>"
                     }
                 },
                 "ec2KeyPair": {
@@ -6946,7 +6946,7 @@
                 "targetInstanceTypes": {
                     "target": "com.amazonaws.batch#StringList",
                     "traits": {
-                        "smithy.api#documentation": "<p>The instance type or family that this override launch template should be applied to.</p>\n         <p>This parameter is required when defining a launch template override.</p>\n         <p>Information included in this parameter must meet the following requirements:</p>\n         <ul>\n            <li>\n               <p>Must be a valid Amazon EC2 instance type or family.</p>\n            </li>\n            <li>\n               <p>\n                  <code>optimal</code> isn't allowed.</p>\n            </li>\n            <li>\n               <p>\n                  <code>targetInstanceTypes</code> can target only instance types and families that are included within the <a href=\"https://docs.aws.amazon.com/batch/latest/APIReference/API_ComputeResource.html#Batch-Type-ComputeResource-instanceTypes\">\n                     <code>ComputeResource.instanceTypes</code>\n                  </a> set. <code>targetInstanceTypes</code> doesn't need to include all of the instances from the <code>instanceType</code> set, but at least a subset. For example, if <code>ComputeResource.instanceTypes</code> includes <code>[m5, g5]</code>, <code>targetInstanceTypes</code> can include <code>[m5.2xlarge]</code> and <code>[m5.large]</code> but not <code>[c5.large]</code>.</p>\n            </li>\n            <li>\n               <p>\n                  <code>targetInstanceTypes</code> included within the same launch template override or across launch template overrides can't overlap for the same compute environment. For example, you can't define one launch template override to target an instance family and another define an instance type within this same family.</p>\n            </li>\n         </ul>"
+                        "smithy.api#documentation": "<p>The instance type or family that this override launch template should be applied to.</p>\n         <p>This parameter is required when defining a launch template override.</p>\n         <p>Information included in this parameter must meet the following requirements:</p>\n         <ul>\n            <li>\n               <p>Must be a valid Amazon EC2 instance type or family.</p>\n            </li>\n            <li>\n               <p>The following Batch <code>InstanceTypes</code> are not allowed: <code>optimal</code>, <code>default_x86_64</code>, and <code>default_arm64</code>.</p>\n            </li>\n            <li>\n               <p>\n                  <code>targetInstanceTypes</code> can target only instance types and families that are included within the <a href=\"https://docs.aws.amazon.com/batch/latest/APIReference/API_ComputeResource.html#Batch-Type-ComputeResource-instanceTypes\">\n                     <code>ComputeResource.instanceTypes</code>\n                  </a> set. <code>targetInstanceTypes</code> doesn't need to include all of the instances from the <code>instanceType</code> set, but at least a subset. For example, if <code>ComputeResource.instanceTypes</code> includes <code>[m5, g5]</code>, <code>targetInstanceTypes</code> can include <code>[m5.2xlarge]</code> and <code>[m5.large]</code> but not <code>[c5.large]</code>.</p>\n            </li>\n            <li>\n               <p>\n                  <code>targetInstanceTypes</code> included within the same launch template override or across launch template overrides can't overlap for the same compute environment. For example, you can't define one launch template override to target an instance family and another define an instance type within this same family.</p>\n            </li>\n         </ul>"
                     }
                 },
                 "userdataType": {
@@ -7649,7 +7649,7 @@
                 "filters": {
                     "target": "com.amazonaws.batch#ListJobsFilterList",
                     "traits": {
-                        "smithy.api#documentation": "<p>The filters to apply to the service job list query. The filter names and values can be:</p>\n         <ul>\n            <li>\n               <p>name: <code>JOB_STATUS</code>\n               </p>\n               <p>values: <code>SUBMITTED | PENDING | RUNNABLE | STARTING | RUNNING | SUCCEEDED | FAILED | SCHEDULED</code>\n               </p>\n            </li>\n            <li>\n               <p>name: <code>JOB_NAME</code>\n               </p>\n               <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>\n            </li>\n         </ul>"
+                        "smithy.api#documentation": "<p>The filter to apply to the query. Only one filter can be used at a time. When the filter\n           is used, <code>jobStatus</code> is ignored. The results are sorted by the <code>createdAt</code> field,\n           with the most recent jobs being first.</p>\n         <dl>\n            <dt>JOB_NAME</dt>\n            <dd>\n               <p>The value of the filter is a case-insensitive match for the job name. If the value\n                       ends with an asterisk (*), the filter matches any job name that begins with the string\n                       before the '*'. This corresponds to the <code>jobName</code> value. For example,\n                       <code>test1</code> matches both <code>Test1</code> and <code>test1</code>, and\n                       <code>test1*</code> matches both <code>test1</code> and <code>Test10</code>. When the\n                       <code>JOB_NAME</code> filter is used, the results are grouped by the job name and\n                       version.</p>\n            </dd>\n            <dt>BEFORE_CREATED_AT</dt>\n            <dd>\n               <p>The value for the filter is the time that's before the job was created. This\n                       corresponds to the <code>createdAt</code> value. The value is a string representation of\n                       the number of milliseconds since 00:00:00 UTC (midnight) on January 1, 1970.</p>\n            </dd>\n            <dt>AFTER_CREATED_AT</dt>\n            <dd>\n               <p>The value for the filter is the time that's after the job was created. This\n                       corresponds to the <code>createdAt</code> value. The value is a string representation of\n                       the number of milliseconds since 00:00:00 UTC (midnight) on January 1, 1970.</p>\n            </dd>\n         </dl>"
                     }
                 }
             },
@@ -10370,7 +10370,7 @@
                 "clientToken": {
                     "target": "com.amazonaws.batch#ClientRequestToken",
                     "traits": {
-                        "smithy.api#documentation": "<p>If this parameter is specified and two update requests with identical payloads and \n          <code>clientToken</code>s are received, these requests are considered the same request and \n          the second request is rejected. A <code>clientToken</code> is valid for 8 hours or until\n          one hour after the consumable resource is deleted, whichever is less.</p>",
+                        "smithy.api#documentation": "<p>If this parameter is specified and two update requests with identical payloads and \n          <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>",
                         "smithy.api#idempotencyToken": {}
                     }
                 }