AWS sagemaker documentation change
Summary
Updated configuration steps for HyperPod cluster creation, added Restricted Instance Group (RIG) configuration details for Amazon Nova customization, removed logging file reference from script description
Security assessment
Added documentation for Restricted Instance Groups (RIG) which appears to be a security-related feature for model customization isolation. No direct evidence of addressing a specific security vulnerability, but introduces security controls for specialized workloads.
Diff
diff --git a/sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-console-ui-create-cluster.md b/sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-console-ui-create-cluster.md index 75d035390..417d9b08d 100644 --- a//sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-console-ui-create-cluster.md +++ b//sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-console-ui-create-cluster.md @@ -39 +39 @@ The VPC subnet you choose for HyperPod has to be private. - 10. In **Step 2: Advanced configuration** , configure network settings within the cluster and in-and-out of the cluster. For orchestration of SageMaker HyperPod cluster with Amazon EKS, the VPC is automatically set to the one configured with the EKS cluster you selected. + 10. In **Step 2: Specify networking** , configure network settings within the cluster and in-and-out of the cluster. For orchestration of SageMaker HyperPod cluster with Amazon EKS, the VPC is automatically set to the one configured with the EKS cluster you selected. @@ -43 +43 @@ The VPC subnet you choose for HyperPod has to be private. -Create an instance group pop-up page, configure a new instance group following the UI guidance. +On **Create an instance group** pop-up page, choose **Standard** to configure a new instance group following the UI guidance. @@ -53 +53 @@ Create an instance group pop-up page, configure a new instance group following t -For a quick start, download the sample script [`on_create.sh`](https://github.com/aws-samples/awsome-distributed-training/blob/main/1.architectures/7.sagemaker-hyperpod-eks/LifecycleScripts/base-config/on_create.sh) from the AWSome Distributed Training GitHub repository, and upload it to the S3 bucket. This script sets up the logging file `/var/log/provision/provisioning.log` required for CloudWatch to gather logs from Pod containers. You can also include additional setup instructions, a series of setup scripts, or commands to be executed during the HyperPod cluster provisioning stage. +For a quick start, download the sample script [`on_create.sh`](https://github.com/aws-samples/awsome-distributed-training/blob/main/1.architectures/7.sagemaker-hyperpod-eks/LifecycleScripts/base-config/on_create.sh) from the AWSome Distributed Training GitHub repository, and upload it to the S3 bucket. You can also include additional setup instructions, a series of setup scripts, or commands to be executed during the HyperPod cluster provisioning stage. @@ -67 +67,35 @@ For a quick start, download the sample script [`on_create.sh`](https://github.co - 12. For **Deep health check** , select the advanced health checks you want to run on the instances. To learn more, see [Deep health checks](./sagemaker-hyperpod-eks-resiliency-deep-health-checks.html). + 9. For **Deep health check** , select the advanced health checks you want to run on the instances. To learn more, see [Deep health checks](./sagemaker-hyperpod-eks-resiliency-deep-health-checks.html). + + 12. In **Step 3: Configure 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. + +On **Create an instance group** pop-up page, choose **Restricted Instance Group (RIG)** to configure a new restricted instance group following the UI guidance. RIG is only required when you want to create a cluster for Amazon Nova model customization. For more information, see [Amazon Nova customization on Amazon SageMaker HyperPod](./nova-hp.html). + + 1. For **Instance group name** , specify a name for the restricted instance group. + + 2. For **Select instance type** , choose the instance for the restricted instance group. + + 3. For **Quantity** , specify an integer not exceeding the instance quota for cluster usage. + + 4. For **Instance group IAM role** , choose the IAM role you have created for SageMaker HyperPod resources, following the section [IAM role for SageMaker HyperPod](./sagemaker-hyperpod-prerequisites-iam.html#sagemaker-hyperpod-prerequisites-iam-role-for-hyperpod). + + 5. Under **Environment Config - FSx for Lustre** , you can set up the following optional configurations. + + 1. For **Throughput per unit of storage** , choose the unit of storage you need. + + 2. For **Storage capacity** , enter the value you need. + + 6. For **Cluster resiliency - deep health checks of accelerated computing instances - optional** , choose the options(s) based on your use case. To learn more, see [Deep health checks](./sagemaker-hyperpod-eks-resiliency-deep-health-checks.html). + + 7. For **Advanced configuration** : + + 1. In **Threads per core** , choose the number you need. + + 2. In **Additional storage volume per instance size (GB) - optional** , specify the size of an additional Elastic Block Store (EBS) volume to attach to each instance in your instance group. + + 3. In **Override cluster-level subnet and security group settings** , choose to toggle this setting you need. + + 1. For **Subnet** , choose private subnets in an availability zone supported by SageMaker AI. To create new subnets, go to the Amazon VPC console. + + 2. For **Security group(s)** , choose security groups that are either attached to the Amazon EKS cluster or whose inbound traffic is permitted by the security group associated with the Amazon EKS cluster. To create new security groups, go to the Amazon VPC console. + + 8. Choose **Save**.