ClusterInstanceGroupSpecification
¶
Source code in docs_src/capo_sagemaker/types/cluster_instance_group_specification.py
auto_patch_config
instance-attribute
¶
auto_patch_config: NotRequired[ClusterAutoPatchConfig]
The configuration for automatic OS security patching. If present, the system automatically applies PATCH AMI updates to this instance group.
capacity_requirements
instance-attribute
¶
capacity_requirements: NotRequired[ClusterCapacityRequirements]
Specifies the capacity requirements for the instance group.
execution_role
instance-attribute
¶
execution_role: NotRequired[RoleArn]
Specifies an IAM execution role to be assumed by the instance group.
image_id
instance-attribute
¶
image_id: NotRequired[ImageId]
When configuring your HyperPod cluster, you can specify an image ID using one of the following options:
-
HyperPodPublicAmiId: Use a HyperPod public AMI -
CustomAmiId: Use your custom AMI -
default: Use the default latest system image. For clusters with continuous scaling node provisioning mode, new instance groups inherit the AMI from the earliest existing instance group
If you choose to use a custom AMI (CustomAmiId), ensure it meets the following requirements:
-
Encryption: The custom AMI must be unencrypted.
-
Ownership: The custom AMI must be owned by the same Amazon Web Services account that is creating the HyperPod cluster.
-
Volume support: Only the primary AMI snapshot volume is supported; additional AMI volumes are not supported.
When updating the instance group's AMI through the UpdateClusterSoftware operation, if an instance group uses a custom AMI, you must provide an ImageId or use the default as input. Note that if you don't specify an instance group in your UpdateClusterSoftware request, then all of the instance groups are patched with the specified image.
image_release_version
instance-attribute
¶
image_release_version: NotRequired[ImageReleaseVersion]
The version of the HyperPod-managed AMI to use for the instance group. Uses semantic versioning in the format MAJOR.MINOR.PATCH (for example, 1.2.3). If omitted, the latest available version is used.
instance_count
instance-attribute
¶
instance_count: NotRequired[ClusterInstanceCount]
Specifies the number of instances to add to the instance group of a SageMaker HyperPod cluster.
instance_group_name
instance-attribute
¶
instance_group_name: NotRequired[ClusterInstanceGroupName]
Specifies the name of the instance group.
instance_requirements
instance-attribute
¶
instance_requirements: NotRequired[ClusterInstanceRequirements]
The instance requirements for the instance group, including the instance types to use. Use this to create a flexible instance group that supports multiple instance types. The InstanceType and InstanceRequirements properties are mutually exclusive.
instance_storage_configs
instance-attribute
¶
instance_storage_configs: NotRequired[ClusterInstanceStorageConfigs]
Specifies the additional storage configurations for the instances in the SageMaker HyperPod cluster instance group.
instance_type
instance-attribute
¶
instance_type: NotRequired[ClusterInstanceType]
Specifies the instance type of the instance group.
kubernetes_config
instance-attribute
¶
kubernetes_config: NotRequired[ClusterKubernetesConfig]
Specifies the Kubernetes configuration for the instance group. You describe what you want the labels and taints to look like, and the cluster works to reconcile the actual state with the declared state for nodes in this instance group.
life_cycle_config
instance-attribute
¶
life_cycle_config: NotRequired[ClusterLifeCycleConfig]
Specifies the LifeCycle configuration for the instance group.
min_instance_count
instance-attribute
¶
min_instance_count: NotRequired[ClusterInstanceCount]
Defines the minimum number of instances required for an instance group to become InService. If this threshold isn't met within 3 hours, the instance group rolls back to its previous state - zero instances for new instance groups, or previous settings for existing instance groups. MinInstanceCount only affects the initial transition to InService and does not guarantee maintaining this minimum afterward.
network_interface
instance-attribute
¶
network_interface: NotRequired[ClusterNetworkInterface]
The network interface configuration for the instance group.
on_start_deep_health_checks
instance-attribute
¶
on_start_deep_health_checks: NotRequired[OnStartDeepHealthChecks]
A flag indicating whether deep health checks should be performed when the cluster instance group is created or updated.
override_vpc_config
instance-attribute
¶
override_vpc_config: NotRequired[VpcConfig]
To configure multi-AZ deployments, customize the Amazon VPC configuration at the instance group level. You can specify different subnets and security groups across different AZs in the instance group specification to override a SageMaker HyperPod cluster's default Amazon VPC configuration. For more information about deploying a cluster in multiple AZs, see Setting up SageMaker HyperPod clusters across multiple AZs.
When your Amazon VPC and subnets support IPv6, network communications differ based on the cluster orchestration platform:
-
Slurm-orchestrated clusters automatically configure nodes with dual IPv6 and IPv4 addresses, allowing immediate IPv6 network communications.
-
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 Amazon EKS IPv6 Cluster Deployment.
Additional resources for IPv6 configuration:
-
For information about adding IPv6 support to your VPC, see to IPv6 Support for VPC.
-
For information about creating a new IPv6-compatible VPC, see Amazon VPC Creation Guide.
-
To configure SageMaker HyperPod with a custom Amazon VPC, see Custom Amazon VPC Setup for SageMaker HyperPod.
scheduled_update_config
instance-attribute
¶
scheduled_update_config: NotRequired[ScheduledUpdateConfig]
The configuration object of the schedule that SageMaker uses to update the AMI.
slurm_config
instance-attribute
¶
slurm_config: NotRequired[ClusterSlurmConfig]
Specifies the Slurm configuration for the instance group.
threads_per_core
instance-attribute
¶
threads_per_core: NotRequired[ClusterThreadsPerCore]
Specifies the value for Threads per core. For instance types that support multithreading, you can specify 1 for disabling multithreading and 2 for enabling multithreading. For instance types that doesn't support multithreading, specify 1. For more information, see the reference table of CPU cores and threads per CPU core per instance type in the Amazon Elastic Compute Cloud User Guide.
training_plan_arn
instance-attribute
¶
training_plan_arn: NotRequired[TrainingPlanArn]
The Amazon Resource Name (ARN); of the training plan to use for this cluster instance group.
For more information about how to reserve GPU capacity for your SageMaker HyperPod clusters using Amazon SageMaker Training Plan, see CreateTrainingPlan .