AWS parallelcluster documentation change
Summary
Added guidance about when to use multiple queues vs multiple clusters, including security isolation requirements
Security assessment
The change documents security considerations for infrastructure isolation but does not address a specific security vulnerability. It adds general security best practice documentation about when to use clusters for isolation.
Diff
diff --git a/parallelcluster/latest/ug/configuration-of-multiple-queues-v3.md b/parallelcluster/latest/ug/configuration-of-multiple-queues-v3.md index 6143b5e88..85ee0ecd8 100644 --- a//parallelcluster/latest/ug/configuration-of-multiple-queues-v3.md +++ b//parallelcluster/latest/ug/configuration-of-multiple-queues-v3.md @@ -8,0 +9,2 @@ With AWS ParallelCluster version 3, you can configure multiple queues by setting +Multiple _queues_ within a single cluster are generally preferred over multiple clusters when the workloads share the same underlying infrastructure and resources (like shared storage, networking, or login nodes). If workloads have similar compute, storage, and networking needs, using multiple queues within a single cluster is more efficient because it allows for resource sharing and avoids unnecessary duplication. This approach simplifies management and reduces overhead, while still allowing for efficient job scheduling and resource allocation. On the other hand, multiple _clusters_ should be used when there are strong security, data, or operational isolation requirements between workloads. For example, if you need to manage and operate workloads independently, with different schedules, update cycles, or access policies, multiple clusters are more appropriate. +