AWS sagemaker documentation change
Summary
Replaced detailed step-by-step cluster creation instructions with a reference to a separate getting started guide
Security assessment
The change removes procedural content and links to external documentation instead. There is no evidence of security vulnerability fixes or security feature additions. The removed content included standard operational guidance about VPC configuration and IAM roles, but these changes appear to be documentation reorganization rather than security-related updates.
Diff
diff --git a/sagemaker/latest/dg/sagemaker-hyperpod-operate-slurm-console-ui.md b/sagemaker/latest/dg/sagemaker-hyperpod-operate-slurm-console-ui.md index 80d3cb9a0..da0dbf10b 100644 --- a//sagemaker/latest/dg/sagemaker-hyperpod-operate-slurm-console-ui.md +++ b//sagemaker/latest/dg/sagemaker-hyperpod-operate-slurm-console-ui.md @@ -28,48 +28 @@ The following topics provide guidance on how to manage SageMaker HyperPod throug -See the following instructions on creating a new SageMaker HyperPod cluster through the SageMaker HyperPod console UI. - - 1. Open the Amazon SageMaker AI console at [https://console.aws.amazon.com/sagemaker/](https://console.aws.amazon.com/sagemaker/). - - 2. Choose **HyperPod Clusters** in the left navigation pane and then **Cluster Management**. - - 3. In the SageMaker HyperPod landing page, choose **Create HyperPod cluster**. - - 4. From the drop-down menu of **Create HyperPod cluster** , choose **Orchestrated by Slurm**. - - 5. In **Step 1: Cluster settings** , set up basic information for the cluster. - - 1. For **Cluster name** , specify a name for the new cluster. - - 2. For **Tags** , add key and value pairs to the new cluster and manage the cluster as an AWS resource. To learn more, see [Tagging your AWS resources](https://docs.aws.amazon.com/tag-editor/latest/userguide/tagging.html). - - 6. In **Step 2: Advanced configuration** , configure optional network settings within the cluster and in-and-out of the cluster. Select your own VPC if you already have one that gives SageMaker AI access to your resources under the VPC. If you want to create a new VPC, see [Create a default VPC](https://docs.aws.amazon.com/vpc/latest/userguide/default-vpc.html#create-default-vpc) or [Create a VPC](https://docs.aws.amazon.com/vpc/latest/userguide/create-vpc.html) in the _Amazon Virtual Private Cloud User Guide_. If you don't make any selections, SageMaker automatically uses the default VPC associated with your account. - -###### Note - -If you want to use your own VPC, you should add additional permissions to the IAM role for SageMaker HyperPod clusters. To learn more, see [Setting up SageMaker HyperPod with a custom Amazon VPC](./sagemaker-hyperpod-prerequisites.html#sagemaker-hyperpod-prerequisites-optional-vpc). - - 7. In **Step 3: Instance groups** , choose **Create instance group**. Each instance group can be configured differently, and you can create a heterogeneous cluster that consists of multiple instance groups with various instance types. In the **Create an instance group** configuration pop-up window, fill the instance group configuration information. - - 1. For **Instance group name** , specify a name for the instance group. - - 2. For **Select instance type** , choose the instance for the instance group. - - 3. For **Quantity** , specify an integer not exceeding the instance quota for cluster usage. To view your current quotas or request a quota increase, see [SageMaker HyperPod quotas](./sagemaker-hyperpod-prerequisites.html#sagemaker-hyperpod-prerequisites-quotas). - - 4. For **S3 path to lifecycle script files** , enter the Amazon S3 path in which your lifecycle scripts are stored or use the **Browse S3** option. - - 5. For **Directory path to your on-create lifecycle script** , enter the file name of the lifecycle script under **S3 path to lifecycle script files**. - - 6. For IAM role, choose the IAM role you have created for SageMaker HyperPod resources, following the section [AWS Identity and Access Management for SageMaker HyperPod](./sagemaker-hyperpod-prerequisites-iam.html). - - 7. Under **Advanced configuration** , you can set up the following optional configurations. - - 1. (Optional) For **Threads per core** , specify `1` for disabling multi-threading and `2` for enabling multi-threading. To find which instance type supports multi-threading, see the reference table of [CPU cores and threads per CPU core per instance type](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/cpu-options-supported-instances-values.html) in the _Amazon EC2 User Guide_. - - 2. (Optional) For **Additional instance storage configs** , 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](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volumes.html) section in the _Amazon Elastic Block Store User Guide_. - - 8. In **Step 4: Review and create** , review the configuration you have set from **Step 1** to **Step 3** and finish submitting the cluster creation request. - - 9. After the status of the cluster turns to `InService`, you can start logging into the cluster nodes. To access the cluster nodes and start running ML workloads, see [Jobs on SageMaker HyperPod clusters](./sagemaker-hyperpod-run-jobs-slurm.html). - - - +See the instructions in [Getting started with SageMaker HyperPod using the SageMaker AI console](./smcluster-getting-started-slurm-console.html) to create a new SageMaker HyperPod cluster through the SageMaker HyperPod console UI.