This is a documentation only release that adds additional information for Amazon ECS Availability Zone rebalancing.

Documentation-only update to add AccountingStorageEnforce to SlurmCustomSetting.
Release IPv6 support with dualstack in SageMaker Notebooks, Tiered Storage Checkpointing Support in SageMaker HyperPod and P5.4xlarge instance type for SageMaker Hosting.

Author: aws-sdk-cpp-automation

VERSION

@@ -1 +1 @@
-1.11.641
+1.11.642

generated/src/aws-cpp-sdk-ecs/include/aws/ecs/model/ClusterSetting.h

@@ -54,8 +54,8 @@ namespace Model
 
     ///@{
     /**
-     * <p>The name of the cluster setting. The value is <code>containerInsights</code>
-     * .</p>
+     * <p>The name of the cluster setting. The value is
+     * <code>containerInsights</code>.</p>
      */
     inline ClusterSettingName GetName() const { return m_name; }
     inline bool NameHasBeenSet() const { return m_nameHasBeenSet; }

generated/src/aws-cpp-sdk-ecs/include/aws/ecs/model/CreateServiceRequest.h

@@ -106,7 +106,15 @@ namespace Model
      * <p>For more information, see <a
      * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html">Balancing
      * an Amazon ECS service across Availability Zones</a> in the <i> <i>Amazon Elastic
-     * Container Service Developer Guide</i> </i>.</p>
+     * Container Service Developer Guide</i> </i>.</p> <p>The default behavior of
+     * <code>AvailabilityZoneRebalancing</code> differs between create and update
+     * requests:</p> <ul> <li> <p>For create service requests, when when no value is
+     * specified for <code>AvailabilityZoneRebalancing</code>, Amazon ECS defaults the
+     * value to to <code>ENABLED</code>.</p> </li> <li> <p>For update service requests,
+     * when no value is specified for <code>AvailabilityZoneRebalancing</code>, Amazon
+     * ECS defaults to the existing service’s <code>AvailabilityZoneRebalancing</code>
+     * value. If the service never had an <code>AvailabilityZoneRebalancing</code>
+     * value set, Amazon ECS treats this as <code>DISABLED</code>.</p> </li> </ul>
      */
     inline AvailabilityZoneRebalancing GetAvailabilityZoneRebalancing() const { return m_availabilityZoneRebalancing; }
     inline bool AvailabilityZoneRebalancingHasBeenSet() const { return m_availabilityZoneRebalancingHasBeenSet; }
@@ -120,11 +128,11 @@ namespace Model
      * service. For more information, see <a
      * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html">Service
      * load balancing</a> in the <i>Amazon Elastic Container Service Developer
-     * Guide</i>.</p> <p>If the service uses the rolling update (<code>ECS</code>)
-     * deployment controller and using either an Application Load Balancer or Network
-     * Load Balancer, you must specify one or more target group ARNs to attach to the
-     * service. The service-linked role is required for services that use multiple
-     * target groups. For more information, see <a
+     * Guide</i>.</p> <p>If the service uses the <code>ECS</code> deployment controller
+     * and using either an Application Load Balancer or Network Load Balancer, you must
+     * specify one or more target group ARNs to attach to the service. The
+     * service-linked role is required for services that use multiple target groups.
+     * For more information, see <a
      * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using
      * service-linked roles for Amazon ECS</a> in the <i>Amazon Elastic Container
      * Service Developer Guide</i>.</p> <p>If the service uses the
@@ -374,17 +382,11 @@ namespace Model
 
     ///@{
     /**
-     * <p>The period of time, in seconds, that the Amazon ECS service scheduler ignores
-     * unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after
-     * a task has first started. If you don't specify a health check grace period
-     * value, the default value of <code>0</code> is used. If you don't use any of the
+     * <p>The period of time, in seconds, that the Amazon Amazon ECS service scheduler
+     * ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health
+     * checks after a task has first started. If you do not specify a health check
+     * grace period value, the default value of 0 is used. If you do not use any of the
      * health checks, then <code>healthCheckGracePeriodSeconds</code> is unused.</p>
-     * <p>If your service's tasks take a while to start and respond to health checks,
-     * you can specify a health check grace period of up to 2,147,483,647 seconds
-     * (about 69 years). During that time, the Amazon ECS service scheduler ignores
-     * health check status. This grace period can prevent the service scheduler from
-     * marking tasks as unhealthy and stopping them before they have time to come
-     * up.</p>
      */
     inline int GetHealthCheckGracePeriodSeconds() const { return m_healthCheckGracePeriodSeconds; }
     inline bool HealthCheckGracePeriodSecondsHasBeenSet() const { return m_healthCheckGracePeriodSecondsHasBeenSet; }

generated/src/aws-cpp-sdk-ecs/include/aws/ecs/model/DeploymentConfiguration.h

@@ -121,7 +121,7 @@ namespace Model
      * launch replacement tasks. For more information about how the scheduler replaces
      * unhealthy tasks, see <a
      * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Amazon
-     * ECS services</a> . </p> <p>For services that <i>do not</i> use a load balancer,
+     * ECS services</a>. </p> <p>For services that <i>do not</i> use a load balancer,
      * the following should be noted:</p> <ul> <li> <p>A service is considered healthy
      * if all essential containers within the tasks in the service pass their health
      * checks.</p> </li> <li> <p>If a task has no essential containers with a health

generated/src/aws-cpp-sdk-ecs/include/aws/ecs/model/Service.h

@@ -387,8 +387,8 @@ namespace Model
     ///@{
     /**
      * <p>The period of time, in seconds, that the Amazon ECS service scheduler ignores
-     * unhealthy Elastic Load Balancing target health checks after a task has first
-     * started.</p>
+     * unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after
+     * a task has first started.</p>
      */
     inline int GetHealthCheckGracePeriodSeconds() const { return m_healthCheckGracePeriodSeconds; }
     inline bool HealthCheckGracePeriodSecondsHasBeenSet() const { return m_healthCheckGracePeriodSecondsHasBeenSet; }
@@ -515,7 +515,15 @@ namespace Model
      * <p>For more information, see <a
      * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html">Balancing
      * an Amazon ECS service across Availability Zones</a> in the <i> <i>Amazon Elastic
-     * Container Service Developer Guide</i> </i>.</p>
+     * Container Service Developer Guide</i> </i>.</p> <p>The default behavior of
+     * <code>AvailabilityZoneRebalancing</code> differs between create and update
+     * requests:</p> <ul> <li> <p>For create service requests, when when no value is
+     * specified for <code>AvailabilityZoneRebalancing</code>, Amazon ECS defaults the
+     * value to to <code>ENABLED</code>.</p> </li> <li> <p>For update service requests,
+     * when no value is specified for <code>AvailabilityZoneRebalancing</code>, Amazon
+     * ECS defaults to the existing service’s <code>AvailabilityZoneRebalancing</code>
+     * value. If the service never had an <code>AvailabilityZoneRebalancing</code>
+     * value set, Amazon ECS treats this as <code>DISABLED</code>.</p> </li> </ul>
      */
     inline AvailabilityZoneRebalancing GetAvailabilityZoneRebalancing() const { return m_availabilityZoneRebalancing; }
     inline bool AvailabilityZoneRebalancingHasBeenSet() const { return m_availabilityZoneRebalancingHasBeenSet; }

generated/src/aws-cpp-sdk-ecs/include/aws/ecs/model/UpdateServiceRequest.h

@@ -154,8 +154,16 @@ namespace Model
      * <p>For more information, see <a
      * href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html">Balancing
      * an Amazon ECS service across Availability Zones</a> in the <i> <i>Amazon Elastic
-     * Container Service Developer Guide</i> </i>.</p> <p>This parameter doesn't
-     * trigger a new service deployment.</p>
+     * Container Service Developer Guide</i> </i>.</p> <p>The default behavior of
+     * <code>AvailabilityZoneRebalancing</code> differs between create and update
+     * requests:</p> <ul> <li> <p>For create service requests, when when no value is
+     * specified for <code>AvailabilityZoneRebalancing</code>, Amazon ECS defaults the
+     * value to to <code>ENABLED</code>.</p> </li> <li> <p>For update service requests,
+     * when no value is specified for <code>AvailabilityZoneRebalancing</code>, Amazon
+     * ECS defaults to the existing service’s <code>AvailabilityZoneRebalancing</code>
+     * value. If the service never had an <code>AvailabilityZoneRebalancing</code>
+     * value set, Amazon ECS treats this as <code>DISABLED</code>.</p> </li> </ul>
+     * <p>This parameter doesn't trigger a new service deployment.</p>
      */
     inline AvailabilityZoneRebalancing GetAvailabilityZoneRebalancing() const { return m_availabilityZoneRebalancing; }
     inline bool AvailabilityZoneRebalancingHasBeenSet() const { return m_availabilityZoneRebalancingHasBeenSet; }

generated/src/aws-cpp-sdk-pcs/include/aws/pcs/PCSClient.h

@@ -16,29 +16,27 @@ namespace Aws
 namespace PCS
 {
   /**
-   * <p>Amazon Web Services Parallel Computing Service (Amazon Web Services PCS) is a
-   * managed service that makes it easier for you to run and scale your high
-   * performance computing (HPC) workloads, and build scientific and engineering
-   * models on Amazon Web Services using Slurm. For more information, see the <a
-   * href="https://docs.aws.amazon.com/pcs/latest/userguide">Amazon Web Services
-   * Parallel Computing Service User Guide</a>.</p> <p>This reference describes the
-   * actions and data types of the service management API. You can use the Amazon Web
-   * Services SDKs to call the API actions in software, or use the Command Line
-   * Interface (CLI) to call the API actions manually. These API actions manage the
-   * service through an Amazon Web Services account.</p> <p>The API actions operate
-   * on Amazon Web Services PCS resources. A <i>resource</i> is an entity in Amazon
-   * Web Services that you can work with. Amazon Web Services services create
-   * resources when you use the features of the service. Examples of Amazon Web
-   * Services PCS resources include clusters, compute node groups, and queues. For
-   * more information about resources in Amazon Web Services, see <a
+   * <p>Parallel Computing Service (PCS) is a managed service that makes it easier
+   * for you to run and scale your high performance computing (HPC) workloads, and
+   * build scientific and engineering models on Amazon Web Services using Slurm. For
+   * more information, see the <a
+   * href="https://docs.aws.amazon.com/pcs/latest/userguide">Parallel Computing
+   * Service User Guide</a>.</p> <p>This reference describes the actions and data
+   * types of the service management API. You can use the Amazon Web Services SDKs to
+   * call the API actions in software, or use the Command Line Interface (CLI) to
+   * call the API actions manually. These API actions manage the service through an
+   * Amazon Web Services account.</p> <p>The API actions operate on PCS resources. A
+   * <i>resource</i> is an entity in Amazon Web Services that you can work with.
+   * Amazon Web Services services create resources when you use the features of the
+   * service. Examples of PCS resources include clusters, compute node groups, and
+   * queues. For more information about resources in Amazon Web Services, see <a
    * href="https://docs.aws.amazon.com/resource-explorer/latest/userguide/getting-started-terms-and-concepts.html#term-resource">Resource</a>
-   * in the <i>Resource Explorer User Guide</i>. </p> <p>An Amazon Web Services PCS
-   * <i>compute node</i> is an Amazon EC2 instance. You don't launch compute nodes
-   * directly. Amazon Web Services PCS uses configuration information that you
-   * provide to launch compute nodes in your Amazon Web Services account. You receive
-   * billing charges for your running compute nodes. Amazon Web Services PCS
-   * automatically terminates your compute nodes when you delete the Amazon Web
-   * Services PCS resources related to those compute nodes.</p>
+   * in the <i>Resource Explorer User Guide</i>. </p> <p>An PCS <i>compute node</i>
+   * is an Amazon EC2 instance. You don't launch compute nodes directly. PCS uses
+   * configuration information that you provide to launch compute nodes in your
+   * Amazon Web Services account. You receive billing charges for your running
+   * compute nodes. PCS automatically terminates your compute nodes when you delete
+   * the PCS resources related to those compute nodes.</p>
    */
   class AWS_PCS_API PCSClient : public Aws::Client::AWSJsonClient, public Aws::Client::ClientWithAsyncTemplateMethods<PCSClient>
   {
@@ -99,16 +97,16 @@ namespace PCS
         virtual ~PCSClient();
 
         /**
-         * <p>Creates a cluster in your account. Amazon Web Services PCS creates the
-         * cluster controller in a service-owned account. The cluster controller
-         * communicates with the cluster resources in your account. The subnets and
-         * security groups for the cluster must already exist before you use this API
-         * action.</p>  <p>It takes time for Amazon Web Services PCS to create the
-         * cluster. The cluster is in a <code>Creating</code> state until it is ready to
-         * use. There can only be 1 cluster in a <code>Creating</code> state per Amazon Web
-         * Services Region per Amazon Web Services account. <code>CreateCluster</code>
-         * fails with a <code>ServiceQuotaExceededException</code> if there is already a
-         * cluster in a <code>Creating</code> state.</p> <p><h3>See Also:</h3>   <a
+         * <p>Creates a cluster in your account. PCS creates the cluster controller in a
+         * service-owned account. The cluster controller communicates with the cluster
+         * resources in your account. The subnets and security groups for the cluster must
+         * already exist before you use this API action.</p>  <p>It takes time for
+         * PCS to create the cluster. The cluster is in a <code>Creating</code> state until
+         * it is ready to use. There can only be 1 cluster in a <code>Creating</code> state
+         * per Amazon Web Services Region per Amazon Web Services account.
+         * <code>CreateCluster</code> fails with a
+         * <code>ServiceQuotaExceededException</code> if there is already a cluster in a
+         * <code>Creating</code> state.</p> <p><h3>See Also:</h3>   <a
          * href="http://docs.aws.amazon.com/goto/WebAPI/pcs-2023-02-10/CreateCluster">AWS
          * API Reference</a></p>
          */
@@ -134,14 +132,13 @@ namespace PCS
 
         /**
          * <p>Creates a managed set of compute nodes. You associate a compute node group
-         * with a cluster through 1 or more Amazon Web Services PCS queues or as part of
-         * the login fleet. A compute node group includes the definition of the compute
-         * properties and lifecycle management. Amazon Web Services PCS uses the
-         * information you provide to this API action to launch compute nodes in your
-         * account. You can only specify subnets in the same Amazon VPC as your cluster.
-         * You receive billing charges for the compute nodes that Amazon Web Services PCS
-         * launches in your account. You must already have a launch template before you
-         * call this API. For more information, see <a
+         * with a cluster through 1 or more PCS queues or as part of the login fleet. A
+         * compute node group includes the definition of the compute properties and
+         * lifecycle management. PCS uses the information you provide to this API action to
+         * launch compute nodes in your account. You can only specify subnets in the same
+         * Amazon VPC as your cluster. You receive billing charges for the compute nodes
+         * that PCS launches in your account. You must already have a launch template
+         * before you call this API. For more information, see <a
          * href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html">Launch
          * an instance from a launch template</a> in the <i>Amazon Elastic Compute Cloud
          * User Guide for Linux Instances</i>.</p><p><h3>See Also:</h3>   <a
@@ -250,8 +247,8 @@ namespace PCS
 
         /**
          * <p>Deletes a job queue. If the compute node group associated with this queue
-         * isn't associated with any other queues, Amazon Web Services PCS terminates all
-         * the compute nodes for this queue.</p><p><h3>See Also:</h3>   <a
+         * isn't associated with any other queues, PCS terminates all the compute nodes for
+         * this queue.</p><p><h3>See Also:</h3>   <a
          * href="http://docs.aws.amazon.com/goto/WebAPI/pcs-2023-02-10/DeleteQueue">AWS API
          * Reference</a></p>
          */
@@ -435,8 +432,7 @@ namespace PCS
         }
 
         /**
-         * <p>Returns a list of all tags on an Amazon Web Services PCS
-         * resource.</p><p><h3>See Also:</h3>   <a
+         * <p>Returns a list of all tags on an PCS resource.</p><p><h3>See Also:</h3>   <a
          * href="http://docs.aws.amazon.com/goto/WebAPI/pcs-2023-02-10/ListTagsForResource">AWS
          * API Reference</a></p>
          */
@@ -462,8 +458,8 @@ namespace PCS
 
         /**
          * <p> <p>This API action isn't intended for you to use.</p>
-         *  <p>Amazon Web Services PCS uses this API action to register the
-         * compute nodes it launches in your account.</p></p><p><h3>See Also:</h3>   <a
+         *  <p>PCS uses this API action to register the compute nodes it
+         * launches in your account.</p></p><p><h3>See Also:</h3>   <a
          * href="http://docs.aws.amazon.com/goto/WebAPI/pcs-2023-02-10/RegisterComputeNodeGroupInstance">AWS
          * API Reference</a></p>
          */
@@ -488,11 +484,11 @@ namespace PCS
         }
 
         /**
-         * <p>Adds or edits tags on an Amazon Web Services PCS resource. Each tag consists
-         * of a tag key and a tag value. The tag key and tag value are case-sensitive
-         * strings. The tag value can be an empty (null) string. To add a tag, specify a
-         * new tag key and a tag value. To edit a tag, specify an existing tag key and a
-         * new tag value.</p><p><h3>See Also:</h3>   <a
+         * <p>Adds or edits tags on an PCS resource. Each tag consists of a tag key and a
+         * tag value. The tag key and tag value are case-sensitive strings. The tag value
+         * can be an empty (null) string. To add a tag, specify a new tag key and a tag
+         * value. To edit a tag, specify an existing tag key and a new tag
+         * value.</p><p><h3>See Also:</h3>   <a
          * href="http://docs.aws.amazon.com/goto/WebAPI/pcs-2023-02-10/TagResource">AWS API
          * Reference</a></p>
          */
@@ -517,9 +513,9 @@ namespace PCS
         }
 
         /**
-         * <p>Deletes tags from an Amazon Web Services PCS resource. To delete a tag,
-         * specify the tag key and the Amazon Resource Name (ARN) of the Amazon Web
-         * Services PCS resource.</p><p><h3>See Also:</h3>   <a
+         * <p>Deletes tags from an PCS resource. To delete a tag, specify the tag key and
+         * the Amazon Resource Name (ARN) of the PCS resource.</p><p><h3>See Also:</h3>  
+         * <a
          * href="http://docs.aws.amazon.com/goto/WebAPI/pcs-2023-02-10/UntagResource">AWS
          * API Reference</a></p>
          */

generated/src/aws-cpp-sdk-pcs/include/aws/pcs/model/ComputeNodeGroup.h

@@ -142,9 +142,9 @@ namespace Model
 
     ///@{
     /**
-     * <p>The ID of the Amazon Machine Image (AMI) that Amazon Web Services PCS uses to
-     * launch instances. If not provided, Amazon Web Services PCS uses the AMI ID
-     * specified in the custom launch template.</p>
+     * <p>The ID of the Amazon Machine Image (AMI) that PCS uses to launch instances.
+     * If not provided, PCS uses the AMI ID specified in the custom launch
+     * template.</p>
      */
     inline const Aws::String& GetAmiId() const { return m_amiId; }
     inline bool AmiIdHasBeenSet() const { return m_amiIdHasBeenSet; }