AWS sagemaker: Update example cluster name in SSM target command
Summary
Changes the example SSM session target cluster identifier from 'my-hyperpod-cluster' to 'aa11bbbbb222' in the Slurm CLI getting-started guide.
Security assessment
Cosmetic example value change in a connection command; no security implication.
Evidence
+ --target sagemaker-cluster:aa11bbbbb222_my-login-group-i-0abc123def456789b \
Diff
diff --git a/sagemaker/latest/dg/smcluster-getting-started-slurm-cli.md b/sagemaker/latest/dg/smcluster-getting-started-slurm-cli.md index c92b1cf07..c5337c62f 100644 --- a//sagemaker/latest/dg/smcluster-getting-started-slurm-cli.md +++ b//sagemaker/latest/dg/smcluster-getting-started-slurm-cli.md @@ -569 +569 @@ After the cluster status turns to `InService` (typically 10 to 15 minutes), conn - --target sagemaker-cluster:my-hyperpod-cluster_my-login-group-i-0abc123def456789b \ + --target sagemaker-cluster:aa11bbbbb222_my-login-group-i-0abc123def456789b \