AWS parallelcluster documentation change
Summary
Updated the update policy for tags from 'not allowed' to 'can be changed during an update' and added a note about limitations for tag updates starting with version 3.15.0.
Security assessment
The change relaxes the update policy for tags, allowing them to be modified during cluster updates. There is no mention of a security issue being fixed. The note about limitations (EBS volume on HeadNode and running nodes) is operational, not security-related. This is a feature enhancement for tag management.
Diff
diff --git a/parallelcluster/latest/ug/Tags-v3.md b/parallelcluster/latest/ug/Tags-v3.md index 6f0d68712..5c5a31ff9 100644 --- a//parallelcluster/latest/ug/Tags-v3.md +++ b//parallelcluster/latest/ug/Tags-v3.md @@ -16 +16 @@ Tags properties -[Update policy: If this setting is changed, the update is not allowed.](./using-pcluster-update-cluster-v3.html#update-policy-fail-v3) +[Update policy: This setting can be changed during an update.](./using-pcluster-update-cluster-v3.html#update-policy-setting-supported-v3) @@ -25 +25 @@ Defines the name of the tag. -[Update policy: If this setting is changed, the update is not allowed.](./using-pcluster-update-cluster-v3.html#update-policy-fail-v3) +[Update policy: This setting can be changed during an update.](./using-pcluster-update-cluster-v3.html#update-policy-setting-supported-v3) @@ -32 +32,12 @@ Defines the value of the tag. -[Update policy: If this setting is changed, the update is not allowed.](./using-pcluster-update-cluster-v3.html#update-policy-fail-v3) +[Update policy: This setting can be changed during an update.](./using-pcluster-update-cluster-v3.html#update-policy-setting-supported-v3) + +###### Note + +Starting with AWS ParallelCluster 3.15.0, Tag updates are supported with the following limitations: + + * EBS Volume on HeadNode - Will only retain the tags from when the cluster was created; updating tags on this EBS volume is not supported. + + * Running Nodes - Tag updates will not be applied to running compute or login nodes. + + +