AWS pcs: Document Slurm Exclusive setting and ExclusiveUser deprecation

Service: pcs · 2026-09-27 · Documentation low

File: pcs/latest/userguide/slurm-custom-settings-queue.md

Summary

Adds documentation for the queue-level Exclusive setting and a note that Slurm deprecates ExclusiveUser from version 26.05 in favor of Exclusive, while AWS PCS continues to support it.

Security assessment

This is resource allocation / job scheduling configuration documentation (node exclusivity and oversubscription), with no authentication, credential, encryption, or exposure implications.

Evidence

Slurm deprecates `ExclusiveUser` from version 26.05 in favor of `Exclusive`. AWS PCS continues to support it, but we recommend that you migrate to `Exclusive`.

Diff

diff --git a/pcs/latest/userguide/slurm-custom-settings-queue.md b/pcs/latest/userguide/slurm-custom-settings-queue.md
index d089e3530..224a700f0 100644
--- a//pcs/latest/userguide/slurm-custom-settings-queue.md
+++ b//pcs/latest/userguide/slurm-custom-settings-queue.md
@@ -26,0 +27,6 @@ QOS values referenced in `AllowQos`, `DenyQos`, or `QOS` settings must already e
+  * [Exclusive](https://slurm.schedmd.com/slurm.conf.html#OPT_Exclusive)
+
+###### Note
+
+`Exclusive` replaces `ExclusiveUser` and `OverSubscribe=EXCLUSIVE`. `Exclusive=NODE` and `Exclusive=TOPO` imply `OverSubscribe=NO`.
+
@@ -28,0 +35,4 @@ QOS values referenced in `AllowQos`, `DenyQos`, or `QOS` settings must already e
+###### Note
+
+Slurm deprecates `ExclusiveUser` from version 26.05 in favor of `Exclusive`. AWS PCS continues to support it, but we recommend that you migrate to `Exclusive`.
+