Getting started with SageMaker HyperPod using the SageMaker AI console

For Instance group type, choose a type for your instance group. For this tutorial, choose Controller (head) for my-controller-group, Login for my-login-group, and Compute (worker) for worker-group-1.

For Name, specify a name for the instance group. For this tutorial, create three instance groups named my-controller-group, my-login-group, and worker-group-1.

For Instance capacity, choose either on-demand capacity or a training plan to reserve your compute resources.

For Instance type, choose the instance for the instance group. For this tutorial, select ml.c5.xlarge for my-controller-group, ml.m5.4xlarge for my-login-group, and ml.trn1.32xlarge for worker-group-1.

For Instance quantity, specify an integer not exceeding the instance quota for cluster usage. For this tutorial, enter 1 for all three groups.

For Target Availability Zone, choose the Availability Zone where your instances will be provisioned. The Availability Zone should correspond to the location of your accelerated compute capacity.

For Additional storage volume per instance (GB) - optional, specify an integer between 1 and 16384 to set the size of an additional Elastic Block Store (EBS) volume in gigabytes (GB). The EBS volume is attached to each instance of the instance group. The default mount path for the additional EBS volume is /opt/sagemaker. After the cluster is successfully created, you can SSH into the cluster instances (nodes) and verify if the EBS volume is mounted correctly by running the df -h command. Attaching an additional EBS volume provides stable, off-instance, and independently persisting storage, as described in the Amazon EBS volumes section in the Amazon Elastic Block Store User Guide.

Choose Add instance group.

For VPC, choose your own VPC if you already have one that gives SageMaker AI access to your VPC. To create a new VPC, follow the instructions at Create a VPC in the Amazon Virtual Private Cloud User Guide. You can leave it as None to use the default SageMaker AI VPC.

For VPC IPv4 CIDR block, enter the starting IP of your VPC.

For Availability Zones, choose the Availability Zones (AZ) where HyperPod will create subnets for your cluster. Choose AZs that match the location of your accelerated compute capacity.

For Security groups, create a security group or choose up to five security groups configured with rules to allow inter-resource communication within the VPC.

For Instance group type, choose a type for your instance group. For this tutorial, choose Controller (head) for my-controller-group, Login for my-login-group, and Compute (worker) for worker-group-1.

For Name, specify a name for the instance group. For this tutorial, create three instance groups named my-controller-group, my-login-group, and worker-group-1.

For Instance capacity, choose either on-demand capacity or a training plan to reserve your compute resources.

For Instance type, choose the instance for the instance group. For this tutorial, select ml.c5.xlarge for my-controller-group, ml.m5.4xlarge for my-login-group, and ml.trn1.32xlarge for worker-group-1.

For Instance quantity, specify an integer not exceeding the instance quota for cluster usage. For this tutorial, enter 1 for all three groups.

For Target Availability Zone, choose the Availability Zone where your instances will be provisioned. The Availability Zone should correspond to the location of your accelerated compute capacity.

For Additional storage volume per instance (GB) - optional, specify an integer between 1 and 16384 to set the size of an additional Elastic Block Store (EBS) volume in gigabytes (GB). The EBS volume is attached to each instance of the instance group. The default mount path for the additional EBS volume is /opt/sagemaker. After the cluster is successfully created, you can SSH into the cluster instances (nodes) and verify if the EBS volume is mounted correctly by running the df -h command. Attaching an additional EBS volume provides stable, off-instance, and independently persisting storage, as described in the Amazon EBS volumes section in the Amazon Elastic Block Store User Guide.

For Slurm partition name (Compute groups only), enter the Slurm partition name for this compute instance group. Partitions act as logical queues that organize how jobs are scheduled across different sets of nodes.

Choose Add instance group.

For Lifecycle scripts, choose one of the following options to control how nodes are provisioned in your cluster:

The following table summarizes the three options:

For Extension script file in S3 - optional (appears when you choose None under Lifecycle scripts), enter the Amazon S3 URI of your extension script. The extension script allows you to provision additional optional capabilities, such as observability, System Security Services Daemon (SSSD), and Amazon S3 bucket mounting, on top of default configurations without managing the entire set of lifecycle scripts.

Enter the full Amazon S3 URI to the entry point script, for example:

s3://DOC-EXAMPLE-BUCKET/extensions/run_extensions.sh

HyperPod downloads the entire folder where the entry point script resides. Structure your Amazon S3 folder so that all supporting files are in the same directory as the entry point script.

For S3 bucket for lifecycle scripts (appears when you choose Use default lifecycle scripts or Use custom lifecycle scripts), choose to create a new bucket or use an existing bucket to store the lifecycle scripts.

For File system, choose an existing FSx for Lustre file system, to create a new FSx for Lustre file system, or don't provision an FSx for Lustre file system.

For Throughput per unit of storage, choose the throughput that will be available per TiB of provisioned storage.

For Storage capacity, enter a capacity value in TB.

For Data compression type, choose LZ4 to enable data compression.

For Lustre version, view the value that's recommended for the new file systems.