AWS parallelcluster documentation change
Summary
Clarifications in bootstrap documentation including IMDSv2 references and shared responsibility wording
Security assessment
Changes include minor phrasing improvements and link text updates. While IMDSv2 is a security feature, the modifications only clarify existing documentation rather than adding new security content. The shared responsibility model reference remains unchanged in substance.
Diff
diff --git a/parallelcluster/latest/ug/custom-bootstrap-actions-v3.md b/parallelcluster/latest/ug/custom-bootstrap-actions-v3.md index b793bbe59..6644d3835 100644 --- a//parallelcluster/latest/ug/custom-bootstrap-actions-v3.md +++ b//parallelcluster/latest/ug/custom-bootstrap-actions-v3.md @@ -15 +15 @@ In most cases, this code is stored in Amazon Simple Storage Service (Amazon S3) -Starting with AWS ParallelCluster version 3.7.0, the cluster [Imds](./Imds-cluster-v3.html#Imds-cluster-v3.title) / [ImdsSupport](./Imds-cluster-v3.html#yaml-cluster-Imds-ImdsSupport) setting default is `v2.0`. +Starting with AWS ParallelCluster version 3.7.0, the cluster [Imds](./Imds-cluster-v3.html#Imds-cluster-v3.title) / [ImdsSupport](./Imds-cluster-v3.html#yaml-cluster-Imds-ImdsSupport) default setting is `v2.0`. @@ -21 +21 @@ When you create a new cluster to upgrade to version 3.7.0 and later versions, ei -You are responsible for configuring the custom scripts and arguments as described in the [Shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/). Verify that your custom bootstrap scripts and arguments are from sources that you trust to have full access to your cluster nodes. +It is your responsibility to configure the custom scripts and arguments as described in the [Shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/). Verify that your custom bootstrap scripts and arguments are from sources that you trust to have full access to your cluster nodes. @@ -33 +33 @@ If you configure [DirectoryService](./DirectoryService-v3.html) and a [HeadNode] -`OnNodeConfigured` actions are called after the node bootstrap processes are complete. `OnNodeConfigured` actions serve the last actions to occur before an instance is considered fully configured and complete. Some `OnNodeConfigured` actions include changing scheduler settings, modifying storage, and modifying packages. You can pass argument to scripts by specifying them during configuration. +`OnNodeConfigured` actions are called after the node bootstrap processes are complete. `OnNodeConfigured` actions serve the last actions to occur before an instance is considered fully configured and complete. Some `OnNodeConfigured` actions include changing scheduler settings, modifying storage, and modifying packages. You can pass arguments to scripts by specifying them during configuration. @@ -61 +61 @@ Before AWS ParallelCluster version 3.0, it was not possible to specify different - * [Example of updating a custom bootstrap script for IMDSv2](./custom-bootstrap-actions-example-imdsv2-v3.html) + * [Example of how to update a custom bootstrap script for IMDSv2](./custom-bootstrap-actions-example-imdsv2-v3.html) @@ -63 +63 @@ Before AWS ParallelCluster version 3.0, it was not possible to specify different - * [Example of updating a configuration for IMDSv1](./custom-bootstrap-actions-example-imdsv1-v3.html) + * [Example of how to update a configuration for IMDSv1](./custom-bootstrap-actions-example-imdsv1-v3.html)