Updates SDK to v2.1526.0

.changes/2.1526.0.json

@@ -0,0 +1,7 @@
+[
+    {
+        "type": "feature",
+        "category": "EMR",
+        "description": "Add support for customers to modify cluster attribute auto-terminate post cluster launch"
+    }
+]

CHANGELOG.md

@@ -1,7 +1,10 @@
 # Changelog for AWS SDK for JavaScript
-<!--LATEST=2.1525.0-->
+<!--LATEST=2.1526.0-->
 <!--ENTRYINSERT-->
 
+## 2.1526.0
+* feature: EMR: Add support for customers to modify cluster attribute auto-terminate post cluster launch
+
 ## 2.1525.0
 * feature: BedrockAgent: Adding Claude 2.1 support to Bedrock Agents
 * feature: Glue: This release adds additional configurations for Query Session Context on the following APIs: GetUnfilteredTableMetadata, GetUnfilteredPartitionMetadata, GetUnfilteredPartitionsMetadata.

README.md

@@ -69,7 +69,7 @@ require('aws-sdk/lib/maintenance_mode_message').suppress = true;
 To use the SDK in the browser, simply add the following script tag to your
 HTML pages:
 
-    <script src="https://sdk.amazonaws.com/js/aws-sdk-2.1525.0.min.js"></script>
+    <script src="https://sdk.amazonaws.com/js/aws-sdk-2.1526.0.min.js"></script>
 
 You can also build a custom browser SDK with your specified set of AWS services.
 This can allow you to reduce the SDK's size, specify different API versions of

apis/elasticmapreduce-2009-03-31.min.json

@@ -1882,6 +1882,23 @@
         }
       }
     },
+    "SetKeepJobFlowAliveWhenNoSteps": {
+      "input": {
+        "type": "structure",
+        "required": [
+          "JobFlowIds",
+          "KeepJobFlowAliveWhenNoSteps"
+        ],
+        "members": {
+          "JobFlowIds": {
+            "shape": "S1t"
+          },
+          "KeepJobFlowAliveWhenNoSteps": {
+            "type": "boolean"
+          }
+        }
+      }
+    },
     "SetTerminationProtection": {
       "input": {
         "type": "structure",

apis/elasticmapreduce-2009-03-31.normal.json

@@ -954,6 +954,22 @@
       ],
       "documentation": "<p>RunJobFlow creates and starts running a new cluster (job flow). The cluster runs the steps specified. After the steps complete, the cluster stops and the HDFS partition is lost. To prevent loss of data, configure the last step of the job flow to store results in Amazon S3. If the <a>JobFlowInstancesConfig</a> <code>KeepJobFlowAliveWhenNoSteps</code> parameter is set to <code>TRUE</code>, the cluster transitions to the WAITING state rather than shutting down after the steps have completed. </p> <p>For additional protection, you can set the <a>JobFlowInstancesConfig</a> <code>TerminationProtected</code> parameter to <code>TRUE</code> to lock the cluster and prevent it from being terminated by API call, user intervention, or in the event of a job flow error.</p> <p>A maximum of 256 steps are allowed in each job flow.</p> <p>If your cluster is long-running (such as a Hive data warehouse) or complex, you may require more than 256 steps to process your data. You can bypass the 256-step limitation in various ways, including using the SSH shell to connect to the master node and submitting queries directly to the software running on the master node, such as Hive and Hadoop.</p> <p>For long-running clusters, we recommend that you periodically store your results.</p> <note> <p>The instance fleets configuration is available only in Amazon EMR releases 4.8.0 and later, excluding 5.0.x versions. The RunJobFlow request can contain InstanceFleets parameters or InstanceGroups parameters, but not both.</p> </note>"
     },
+    "SetKeepJobFlowAliveWhenNoSteps": {
+      "name": "SetKeepJobFlowAliveWhenNoSteps",
+      "http": {
+        "method": "POST",
+        "requestUri": "/"
+      },
+      "input": {
+        "shape": "SetKeepJobFlowAliveWhenNoStepsInput"
+      },
+      "errors": [
+        {
+          "shape": "InternalServerError"
+        }
+      ],
+      "documentation": "<p>You can use the <code>SetKeepJobFlowAliveWhenNoSteps</code> to configure a cluster (job flow) to terminate after the step execution, i.e., all your steps are executed. If you want a transient cluster that shuts down after the last of the current executing steps are completed, you can configure <code>SetKeepJobFlowAliveWhenNoSteps</code> to false. If you want a long running cluster, configure <code>SetKeepJobFlowAliveWhenNoSteps</code> to true.</p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/emr/latest/ManagementGuide/UsingEMR_TerminationProtection.html\">Managing Cluster Termination</a> in the <i>Amazon EMR Management Guide</i>.</p>"
+    },
     "SetTerminationProtection": {
       "name": "SetTerminationProtection",
       "http": {
@@ -5348,6 +5364,23 @@
         "shape": "SessionMappingSummary"
       }
     },
+    "SetKeepJobFlowAliveWhenNoStepsInput": {
+      "type": "structure",
+      "required": [
+        "JobFlowIds",
+        "KeepJobFlowAliveWhenNoSteps"
+      ],
+      "members": {
+        "JobFlowIds": {
+          "shape": "XmlStringList",
+          "documentation": "<p>A list of strings that uniquely identify the clusters to protect. This identifier is returned by <a href=\"https://docs.aws.amazon.com/emr/latest/APIReference/API_RunJobFlow.html\">RunJobFlow</a> and can also be obtained from <a href=\"https://docs.aws.amazon.com/emr/latest/APIReference/API_DescribeJobFlows.html\">DescribeJobFlows</a>.</p>"
+        },
+        "KeepJobFlowAliveWhenNoSteps": {
+          "shape": "Boolean",
+          "documentation": "<p>A Boolean that indicates whether to terminate the cluster after all steps are executed.</p>"
+        }
+      }
+    },
     "SetTerminationProtectionInput": {
       "type": "structure",
       "required": [

clients/emr.d.ts

@@ -388,6 +388,14 @@ declare class EMR extends Service {
    * RunJobFlow creates and starts running a new cluster (job flow). The cluster runs the steps specified. After the steps complete, the cluster stops and the HDFS partition is lost. To prevent loss of data, configure the last step of the job flow to store results in Amazon S3. If the JobFlowInstancesConfig KeepJobFlowAliveWhenNoSteps parameter is set to TRUE, the cluster transitions to the WAITING state rather than shutting down after the steps have completed.  For additional protection, you can set the JobFlowInstancesConfig TerminationProtected parameter to TRUE to lock the cluster and prevent it from being terminated by API call, user intervention, or in the event of a job flow error. A maximum of 256 steps are allowed in each job flow. If your cluster is long-running (such as a Hive data warehouse) or complex, you may require more than 256 steps to process your data. You can bypass the 256-step limitation in various ways, including using the SSH shell to connect to the master node and submitting queries directly to the software running on the master node, such as Hive and Hadoop. For long-running clusters, we recommend that you periodically store your results.  The instance fleets configuration is available only in Amazon EMR releases 4.8.0 and later, excluding 5.0.x versions. The RunJobFlow request can contain InstanceFleets parameters or InstanceGroups parameters, but not both. 
    */
   runJobFlow(callback?: (err: AWSError, data: EMR.Types.RunJobFlowOutput) => void): Request<EMR.Types.RunJobFlowOutput, AWSError>;
+  /**
+   * You can use the SetKeepJobFlowAliveWhenNoSteps to configure a cluster (job flow) to terminate after the step execution, i.e., all your steps are executed. If you want a transient cluster that shuts down after the last of the current executing steps are completed, you can configure SetKeepJobFlowAliveWhenNoSteps to false. If you want a long running cluster, configure SetKeepJobFlowAliveWhenNoSteps to true. For more information, see Managing Cluster Termination in the Amazon EMR Management Guide.
+   */
+  setKeepJobFlowAliveWhenNoSteps(params: EMR.Types.SetKeepJobFlowAliveWhenNoStepsInput, callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
+  /**
+   * You can use the SetKeepJobFlowAliveWhenNoSteps to configure a cluster (job flow) to terminate after the step execution, i.e., all your steps are executed. If you want a transient cluster that shuts down after the last of the current executing steps are completed, you can configure SetKeepJobFlowAliveWhenNoSteps to false. If you want a long running cluster, configure SetKeepJobFlowAliveWhenNoSteps to true. For more information, see Managing Cluster Termination in the Amazon EMR Management Guide.
+   */
+  setKeepJobFlowAliveWhenNoSteps(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
   /**
    * SetTerminationProtection locks a cluster (job flow) so the Amazon EC2 instances in the cluster cannot be terminated by user intervention, an API call, or in the event of a job-flow error. The cluster still terminates upon successful completion of the job flow. Calling SetTerminationProtection on a cluster is similar to calling the Amazon EC2 DisableAPITermination API on all Amazon EC2 instances in a cluster.  SetTerminationProtection is used to prevent accidental termination of a cluster and to ensure that in the event of an error, the instances persist so that you can recover any data stored in their ephemeral instance storage.  To terminate a cluster that has been locked by setting SetTerminationProtection to true, you must first unlock the job flow by a subsequent call to SetTerminationProtection in which you set the value to false.   For more information, seeManaging Cluster Termination in the Amazon EMR Management Guide. 
    */
@@ -3333,6 +3341,16 @@ declare namespace EMR {
     CreationTime?: _Date;
   }
   export type SessionMappingSummaryList = SessionMappingSummary[];
+  export interface SetKeepJobFlowAliveWhenNoStepsInput {
+    /**
+     * A list of strings that uniquely identify the clusters to protect. This identifier is returned by RunJobFlow and can also be obtained from DescribeJobFlows.
+     */
+    JobFlowIds: XmlStringList;
+    /**
+     * A Boolean that indicates whether to terminate the cluster after all steps are executed.
+     */
+    KeepJobFlowAliveWhenNoSteps: Boolean;
+  }
   export interface SetTerminationProtectionInput {
     /**
      *  A list of strings that uniquely identify the clusters to protect. This identifier is returned by RunJobFlow and can also be obtained from DescribeJobFlows .