AWS parallelcluster: Warn against in-place PCUI stack updates
Summary
Adds an Important note that updating an existing PCUI stack in place with a newer template can break PCUI, so a new stack must be deployed; existing clusters are unaffected and custom domains can preserve the URL.
Security assessment
This is an operational/reliability guidance note about CloudFormation stack updates, with no authentication, encryption, or exposure implications.
Evidence
+You can't update an existing PCUI stack in place with a newer PCUI template. Such an update can complete successfully in CloudFormation and still leave the PCUI broken. To move to a newer PCUI version, you must deploy a new PCUI stack. Your existing clusters aren't affected. To keep the same PCUI URL, use a custom domain. For more information, see [Configure a custom domain](./tutorials_08_custom_domain-v3.html).
Diff
diff --git a/parallelcluster/latest/ug/install-pcui-v3.md b/parallelcluster/latest/ug/install-pcui-v3.md index ea0c12e..47f9936 100644 --- a//parallelcluster/latest/ug/install-pcui-v3.md +++ b//parallelcluster/latest/ug/install-pcui-v3.md @@ -48,0 +49,4 @@ You can only create and edit clusters or build images with the same AWS Parallel +###### Important + +You can't update an existing PCUI stack in place with a newer PCUI template. Such an update can complete successfully in CloudFormation and still leave the PCUI broken. To move to a newer PCUI version, you must deploy a new PCUI stack. Your existing clusters aren't affected. To keep the same PCUI URL, use a custom domain. For more information, see [Configure a custom domain](./tutorials_08_custom_domain-v3.html). +