AWS sagemaker documentation change
Summary
Documentation title update ('Using the AWS CLI' to 'Managing...'), link text correction ('Customize' to 'Customizing'), scaling procedure reference update ('Scale down' to 'Scaling down'), and UI section simplification ('Using the SageMaker HyperPod console UI' to 'Using the SageMaker console')
Security assessment
Changes focus on clarity and consistency in documentation. No security-related content added or modified, despite mentions of IAM roles which were not substantively changed in this diff.
Diff
diff --git a/sagemaker/latest/dg/sagemaker-hyperpod-operate-slurm-cli-command.md b/sagemaker/latest/dg/sagemaker-hyperpod-operate-slurm-cli-command.md index 81334b9e0..9754356a4 100644 --- a//sagemaker/latest/dg/sagemaker-hyperpod-operate-slurm-cli-command.md +++ b//sagemaker/latest/dg/sagemaker-hyperpod-operate-slurm-cli-command.md @@ -7 +7 @@ Create a new clusterDescribe a clusterList details of cluster nodesDescribe deta -# Using the AWS CLI +# Managing SageMaker HyperPod Slurm clusters using the AWS CLI @@ -42 +42 @@ Make sure that you set the S3 path to start with `s3://sagemaker-`. The [IAM rol - 2. Prepare a [CreateCluster](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreateCluster.html) API request file in JSON format. You should configure instance groups to match with the Slurm cluster you design in the `provisioning_parameters.json` file that'll be used during cluster creating as part of running a set of lifecycle scripts. To learn more, see [Customize SageMaker HyperPod clusters using lifecycle scripts](./sagemaker-hyperpod-lifecycle-best-practices-slurm.html). The following template has two instance groups to meet the minimum requirement for a Slurm cluster: one controller (head) node and one compute (worker) node. For `ExecutionRole`, provide the ARN of the IAM role you created with the managed `AmazonSageMakerClusterInstanceRolePolicy` from the section [IAM role for SageMaker HyperPod](./sagemaker-hyperpod-prerequisites-iam.html#sagemaker-hyperpod-prerequisites-iam-role-for-hyperpod). + 2. Prepare a [CreateCluster](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreateCluster.html) API request file in JSON format. You should configure instance groups to match with the Slurm cluster you design in the `provisioning_parameters.json` file that'll be used during cluster creating as part of running a set of lifecycle scripts. To learn more, see [Customizing SageMaker HyperPod clusters using lifecycle scripts](./sagemaker-hyperpod-lifecycle-best-practices-slurm.html). The following template has two instance groups to meet the minimum requirement for a Slurm cluster: one controller (head) node and one compute (worker) node. For `ExecutionRole`, provide the ARN of the IAM role you created with the managed `AmazonSageMakerClusterInstanceRolePolicy` from the section [IAM role for SageMaker HyperPod](./sagemaker-hyperpod-prerequisites-iam.html#sagemaker-hyperpod-prerequisites-iam-role-for-hyperpod). @@ -285 +285 @@ You can scale down the number of instances or delete instance groups in your Sag -You scale down by either using the `UpdateCluster` API operation to randomly terminate instances from your instance group down to a specified number, or by terminating specific instances using the `BatchDeleteClusterNodes` API operation. You can also completely remove entire instance groups using the `UpdateCluster` API. For more information about how to scale down using these methods, see [Scale down a SageMaker HyperPod cluster](./smcluster-scale-down.html). +You scale down by either using the `UpdateCluster` API operation to randomly terminate instances from your instance group down to a specified number, or by terminating specific instances using the `BatchDeleteClusterNodes` API operation. You can also completely remove entire instance groups using the `UpdateCluster` API. For more information about how to scale down using these methods, see [Scaling down a SageMaker HyperPod cluster](./smcluster-scale-down.html). @@ -304 +304 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Using the SageMaker HyperPod console UI +Using the SageMaker console @@ -306 +306 @@ Using the SageMaker HyperPod console UI -Customize SageMaker HyperPod clusters using lifecycle scripts +Lifecycle scripts