docs(client-batch): This feature allows customers to use AWS Batch with Linux with ARM64 CPU Architecture with Fargate Spot compute support.

Author: awstools

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

@@ -2859,8 +2859,8 @@ export interface RuntimePlatform {
    *     compute environment is found.</p>
    *          </note>
    *          <note>
-   *             <p>Fargate Spot is not supported for <code>ARM64</code> and Windows-based containers on Fargate.
-   *     A job queue will be blocked if a Fargate <code>ARM64</code> or Windows job is submitted to a job
+   *             <p>Fargate Spot is not supported on Windows-based containers on Fargate.
+   *     A job queue will be blocked if a Windows job is submitted to a job
    *     queue with only Fargate Spot compute environments. However, you can attach both <code>FARGATE</code> and
    *      <code>FARGATE_SPOT</code> compute environments to the same job queue.</p>
    *          </note>
@@ -2869,14 +2869,14 @@ export interface RuntimePlatform {
   operatingSystemFamily?: string | undefined;
 
   /**
-   * <p> The vCPU architecture. The default value is <code>X86_64</code>. Valid values are
+   * <p>The vCPU architecture. The default value is <code>X86_64</code>. Valid values are
    *     <code>X86_64</code> and <code>ARM64</code>.</p>
    *          <note>
    *             <p>This parameter must be set to <code>X86_64</code> for Windows containers.</p>
    *          </note>
    *          <note>
-   *             <p>Fargate Spot is not supported for <code>ARM64</code> and Windows-based containers on
-   *     Fargate. A job queue will be blocked if a Fargate <code>ARM64</code> or Windows job is
+   *             <p>Fargate Spot is not supported on Windows-based containers on
+   *     Fargate. A job queue will be blocked if a Windows job is
    *     submitted to a job queue with only Fargate Spot compute environments. However, you can attach
    *     both <code>FARGATE</code> and <code>FARGATE_SPOT</code> compute environments to the same job
    *     queue.</p>

codegen/sdk-codegen/aws-models/batch.json

@@ -8488,13 +8488,13 @@
         "operatingSystemFamily": {
           "target": "com.amazonaws.batch#String",
           "traits": {
-            "smithy.api#documentation": "<p>The operating system for the compute environment. Valid values are:\n    <code>LINUX</code> (default), <code>WINDOWS_SERVER_2019_CORE</code>,\n    <code>WINDOWS_SERVER_2019_FULL</code>, <code>WINDOWS_SERVER_2022_CORE</code>, and\n    <code>WINDOWS_SERVER_2022_FULL</code>.</p>\n         <note>\n            <p>The following parameters can’t be set for Windows containers: <code>linuxParameters</code>,\n     <code>privileged</code>, <code>user</code>, <code>ulimits</code>,\n     <code>readonlyRootFilesystem</code>, and <code>efsVolumeConfiguration</code>.</p>\n         </note>\n         <note>\n            <p>The Batch Scheduler checks the compute environments that are attached to the job queue before \n    registering a task definition with Fargate. In this scenario, the job queue is where the job is \n    submitted. If the job requires a Windows container and the first compute environment is <code>LINUX</code>, \n    the compute environment is skipped and the next compute environment is checked until a Windows-based \n    compute environment is found.</p>\n         </note>\n         <note>\n            <p>Fargate Spot is not supported for <code>ARM64</code> and Windows-based containers on Fargate. \n    A job queue will be blocked if a Fargate <code>ARM64</code> or Windows job is submitted to a job \n    queue with only Fargate Spot compute environments. However, you can attach both <code>FARGATE</code> and\n     <code>FARGATE_SPOT</code> compute environments to the same job queue.</p>\n         </note>"
+            "smithy.api#documentation": "<p>The operating system for the compute environment. Valid values are:\n    <code>LINUX</code> (default), <code>WINDOWS_SERVER_2019_CORE</code>,\n    <code>WINDOWS_SERVER_2019_FULL</code>, <code>WINDOWS_SERVER_2022_CORE</code>, and\n    <code>WINDOWS_SERVER_2022_FULL</code>.</p>\n         <note>\n            <p>The following parameters can’t be set for Windows containers: <code>linuxParameters</code>,\n     <code>privileged</code>, <code>user</code>, <code>ulimits</code>,\n     <code>readonlyRootFilesystem</code>, and <code>efsVolumeConfiguration</code>.</p>\n         </note>\n         <note>\n            <p>The Batch Scheduler checks the compute environments that are attached to the job queue before \n    registering a task definition with Fargate. In this scenario, the job queue is where the job is \n    submitted. If the job requires a Windows container and the first compute environment is <code>LINUX</code>, \n    the compute environment is skipped and the next compute environment is checked until a Windows-based \n    compute environment is found.</p>\n         </note>\n         <note>\n            <p>Fargate Spot is not supported on Windows-based containers on Fargate. \n    A job queue will be blocked if a Windows job is submitted to a job \n    queue with only Fargate Spot compute environments. However, you can attach both <code>FARGATE</code> and\n     <code>FARGATE_SPOT</code> compute environments to the same job queue.</p>\n         </note>"
           }
         },
         "cpuArchitecture": {
           "target": "com.amazonaws.batch#String",
           "traits": {
-            "smithy.api#documentation": "<p> The vCPU architecture. The default value is <code>X86_64</code>. Valid values are\n    <code>X86_64</code> and <code>ARM64</code>.</p>\n         <note>\n            <p>This parameter must be set to <code>X86_64</code> for Windows containers.</p>\n         </note>\n         <note>\n            <p>Fargate Spot is not supported for <code>ARM64</code> and Windows-based containers on\n    Fargate. A job queue will be blocked if a Fargate <code>ARM64</code> or Windows job is\n    submitted to a job queue with only Fargate Spot compute environments. However, you can attach\n    both <code>FARGATE</code> and <code>FARGATE_SPOT</code> compute environments to the same job\n    queue.</p>\n         </note>"
+            "smithy.api#documentation": "<p>The vCPU architecture. The default value is <code>X86_64</code>. Valid values are\n    <code>X86_64</code> and <code>ARM64</code>.</p>\n         <note>\n            <p>This parameter must be set to <code>X86_64</code> for Windows containers.</p>\n         </note>\n         <note>\n            <p>Fargate Spot is not supported on Windows-based containers on\n    Fargate. A job queue will be blocked if a Windows job is\n    submitted to a job queue with only Fargate Spot compute environments. However, you can attach\n    both <code>FARGATE</code> and <code>FARGATE_SPOT</code> compute environments to the same job\n    queue.</p>\n         </note>"
           }
         }
       },