AWS parallelcluster documentation change
Summary
Grammar improvements in security recommendations and version update from 3.15.0 to 3.15.1
Security assessment
Grammar fixes ('suggest to use' → 'suggest using') don't alter security meaning. Version update lacks security context. SSH restriction advice remains unchanged.
Diff
diff --git a/parallelcluster/latest/ug/tutorials_05_multi-user-ad-step3.md b/parallelcluster/latest/ug/tutorials_05_multi-user-ad-step3.md index c462f56c8..06dd42ca1 100644 --- a//parallelcluster/latest/ug/tutorials_05_multi-user-ad-step3.md +++ b//parallelcluster/latest/ug/tutorials_05_multi-user-ad-step3.md @@ -42 +42 @@ We recommend that you choose the LDAPS configuration with certificate verificati -For better security posture, we suggest to use the `HeadNode` / `Ssh` / `AllowedIps` configuration to limit the SSH access to the head node. +For better security posture, we suggest using the `HeadNode` / `Ssh` / `AllowedIps` configuration to limit the SSH access to the head node. @@ -135 +135 @@ After you create the bootstrap file and before you upload it to your S3 bucket, -For better security posture, we suggest to use the HeadNode/Ssh/AllowedIps configuration to limit the SSH access to the head node. +For better security posture, we suggest using the HeadNode/Ssh/AllowedIps configuration to limit the SSH access to the head node. @@ -183 +183 @@ For better security posture, we suggest to use the HeadNode/Ssh/AllowedIps confi -For better security posture, we suggest to use the HeadNode/Ssh/AllowedIps configuration to limit the SSH access to the head node. +For better security posture, we suggest using the HeadNode/Ssh/AllowedIps configuration to limit the SSH access to the head node. @@ -225 +225 @@ Create your cluster with the following command. - "version": 3.15.0, + "version": 3.15.1,