feat(client-sagemaker): Updated field validation requirements for InstanceGroups.

Author: awstools

clients/client-sagemaker/src/commands/CreateClusterCommand.ts

@@ -37,7 +37,7 @@ export interface CreateClusterCommandOutput extends CreateClusterResponse, __Met
  * const client = new SageMakerClient(config);
  * const input = { // CreateClusterRequest
  *   ClusterName: "STRING_VALUE", // required
- *   InstanceGroups: [ // ClusterInstanceGroupSpecifications // required
+ *   InstanceGroups: [ // ClusterInstanceGroupSpecifications
  *     { // ClusterInstanceGroupSpecification
  *       InstanceCount: Number("int"), // required
  *       InstanceGroupName: "STRING_VALUE", // required

clients/client-sagemaker/src/commands/UpdateClusterCommand.ts

@@ -37,7 +37,7 @@ export interface UpdateClusterCommandOutput extends UpdateClusterResponse, __Met
  * const client = new SageMakerClient(config);
  * const input = { // UpdateClusterRequest
  *   ClusterName: "STRING_VALUE", // required
- *   InstanceGroups: [ // ClusterInstanceGroupSpecifications // required
+ *   InstanceGroups: [ // ClusterInstanceGroupSpecifications
  *     { // ClusterInstanceGroupSpecification
  *       InstanceCount: Number("int"), // required
  *       InstanceGroupName: "STRING_VALUE", // required

clients/client-sagemaker/src/models/models_1.ts

@@ -1167,7 +1167,7 @@ export interface CreateClusterRequest {
    * <p>The instance groups to be created in the SageMaker HyperPod cluster.</p>
    * @public
    */
-  InstanceGroups: ClusterInstanceGroupSpecification[] | undefined;
+  InstanceGroups?: ClusterInstanceGroupSpecification[] | undefined;
 
   /**
    * <p>Specifies the Amazon Virtual Private Cloud (VPC) that is associated with the Amazon SageMaker HyperPod cluster. You can control access to and from your resources by configuring your VPC. For more information, see <a href="https://docs.aws.amazon.com/sagemaker/latest/dg/infrastructure-give-access.html">Give SageMaker access to resources in your Amazon VPC</a>.</p> <note> <p>When your Amazon VPC and subnets support IPv6, network communications differ based on the cluster orchestration platform:</p> <ul> <li> <p>Slurm-orchestrated clusters automatically configure nodes with dual IPv6 and IPv4 addresses, allowing immediate IPv6 network communications.</p> </li> <li> <p>In Amazon EKS-orchestrated clusters, nodes receive dual-stack addressing, but pods can only use IPv6 when the Amazon EKS cluster is explicitly IPv6-enabled. For information about deploying an IPv6 Amazon EKS cluster, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/deploy-ipv6-cluster.html#_deploy_an_ipv6_cluster_with_eksctl">Amazon EKS IPv6 Cluster Deployment</a>.</p> </li> </ul> <p>Additional resources for IPv6 configuration:</p> <ul> <li> <p>For information about adding IPv6 support to your VPC, see to <a href="https://docs.aws.amazon.com/vpc/latest/userguide/vpc-migrate-ipv6.html">IPv6 Support for VPC</a>.</p> </li> <li> <p>For information about creating a new IPv6-compatible VPC, see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/create-vpc.html">Amazon VPC Creation Guide</a>.</p> </li> <li> <p>To configure SageMaker HyperPod with a custom Amazon VPC, see <a href="https://docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-hyperpod-prerequisites.html#sagemaker-hyperpod-prerequisites-optional-vpc">Custom Amazon VPC Setup for SageMaker HyperPod</a>.</p> </li> </ul> </note>

clients/client-sagemaker/src/models/models_4.ts

@@ -356,7 +356,7 @@ export interface ListClustersRequest {
   CreationTimeBefore?: Date | undefined;
 
   /**
-   * <p>Set the maximum number of SageMaker HyperPod clusters to list.</p>
+   * <p>Specifies the maximum number of clusters to evaluate for the operation (not necessarily the number of matching items). After SageMaker processes the number of clusters up to <code>MaxResults</code>, it stops the operation and returns the matching clusters up to that point. If all the matching clusters are desired, SageMaker will go through all the clusters until <code>NextToken</code> is empty.</p>
    * @public
    */
   MaxResults?: number | undefined;

clients/client-sagemaker/src/models/models_5.ts

@@ -612,7 +612,7 @@ export interface UpdateClusterRequest {
    * <p>Specify the instance groups to update.</p>
    * @public
    */
-  InstanceGroups: ClusterInstanceGroupSpecification[] | undefined;
+  InstanceGroups?: ClusterInstanceGroupSpecification[] | undefined;
 
   /**
    * <p>The node recovery mode to be applied to the SageMaker HyperPod cluster.</p>

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

@@ -10744,8 +10744,7 @@
           "target": "com.amazonaws.sagemaker#ClusterInstanceGroupSpecifications",
           "traits": {
             "smithy.api#clientOptional": {},
-            "smithy.api#documentation": "<p>The instance groups to be created in the SageMaker HyperPod cluster.</p>",
-            "smithy.api#required": {}
+            "smithy.api#documentation": "<p>The instance groups to be created in the SageMaker HyperPod cluster.</p>"
           }
         },
         "VpcConfig": {
@@ -40623,7 +40622,7 @@
         "MaxResults": {
           "target": "com.amazonaws.sagemaker#MaxResults",
           "traits": {
-            "smithy.api#documentation": "<p>Set the maximum number of SageMaker HyperPod clusters to list.</p>"
+            "smithy.api#documentation": "<p>Specifies the maximum number of clusters to evaluate for the operation (not necessarily the number of matching items). After SageMaker processes the number of clusters up to <code>MaxResults</code>, it stops the operation and returns the matching clusters up to that point. If all the matching clusters are desired, SageMaker will go through all the clusters until <code>NextToken</code> is empty.</p>"
           }
         },
         "NameContains": {
@@ -74254,8 +74253,7 @@
           "target": "com.amazonaws.sagemaker#ClusterInstanceGroupSpecifications",
           "traits": {
             "smithy.api#clientOptional": {},
-            "smithy.api#documentation": "<p>Specify the instance groups to update.</p>",
-            "smithy.api#required": {}
+            "smithy.api#documentation": "<p>Specify the instance groups to update.</p>"
           }
         },
         "NodeRecovery": {