AWS sagemaker documentation change
Summary
Updated console and CLI command documentation links to include 'slurm' references
Security assessment
Link updates for documentation consistency, no security content changes
Diff
diff --git a/sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-access-through-terminal.md b/sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-access-through-terminal.md index ae27ca55f..d0e19298e 100644 --- a//sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-access-through-terminal.md +++ b//sagemaker/latest/dg/sagemaker-hyperpod-eks-operate-access-through-terminal.md @@ -7 +7 @@ -You can directly access the nodes of a SageMaker HyperPod cluster in service using the AWS CLI commands for AWS Systems Manager (SSM). Run `aws ssm start-session` with the host name of the node in format of `sagemaker-cluster:[cluster-id]_[instance-group-name]-[instance-id]`. You can retrieve the cluster ID, the instance ID, and the instance group name from the [SageMaker HyperPod console](./sagemaker-hyperpod-operate-console-ui.html#sagemaker-hyperpod-operate-console-ui-view-details-of-clusters) or by running `describe-cluster` and `list-cluster-nodes` from the [AWS CLI commands for SageMaker HyperPod](./sagemaker-hyperpod-operate-cli-command.html#sagemaker-hyperpod-operate-cli-command-list-cluster-nodes). For example, if your cluster ID is `aa11bbbbb222`, the cluster node name is `controller-group`, and the cluster node ID is `i-111222333444555aa`, the SSM `start-session` command should be the following. +You can directly access the nodes of a SageMaker HyperPod cluster in service using the AWS CLI commands for AWS Systems Manager (SSM). Run `aws ssm start-session` with the host name of the node in format of `sagemaker-cluster:[cluster-id]_[instance-group-name]-[instance-id]`. You can retrieve the cluster ID, the instance ID, and the instance group name from the [SageMaker HyperPod console](./sagemaker-hyperpod-operate-slurm-console-ui.html#sagemaker-hyperpod-operate-slurm-console-ui-view-details-of-clusters) or by running `describe-cluster` and `list-cluster-nodes` from the [AWS CLI commands for SageMaker HyperPod](./sagemaker-hyperpod-operate-slurm-cli-command.html#sagemaker-hyperpod-operate-slurm-cli-command-list-cluster-nodes). For example, if your cluster ID is `aa11bbbbb222`, the cluster node name is `controller-group`, and the cluster node ID is `i-111222333444555aa`, the SSM `start-session` command should be the following.