AWS Security ChangesHomeSearch

AWS pcs: AWS PCS doc history: MIG node boot/lifecycle recommendation added

Service: pcs · 2026-10-03 · Documentation low

File: pcs/latest/userguide/doc-history.md

Summary

The September 11, 2026 release-history entry was rewritten: the MIG topic note was moved and expanded to state that the MIG topic now lists what a MIG node needs on every boot and recommends a node lifecycle action that applies it and fails the node if MIG mode cannot be enabled. The rest of the entry (Slurm 26.05 support, GRES settings, JWT username claim deprecation, hardware topology, INVALID_REG troubleshooting) is unchanged.

Security assessment

The only substantive change in this doc-history line is the inserted sentence about the MIG topic listing per-boot requirements and recommending a node lifecycle action that fails the node if MIG mode cannot be enabled. That is a reliability/correctness (GPU partitioning) operational note, not a fix for a vulnerability, credential handling, or access control; the JWT claim deprecation and REST API authentication text is carried over unchanged from the prior revision.

Evidence

+September 11, 2026 | Support for Slurm 26.05, custom GRES settings, and hardware topology |  AWS PCS supports Slurm 26.05. Clusters running 25.11, 25.05, and 24.11 can update directly to 26.05. A single sample AMI now supports every Slurm version that is not EOL, and the AMI name no longer contains a Slurm version. For more information, see [Slurm versions in AWS PCS](./slurm-versions.html) and [Release notes for Slurm versions in AWS PCS](./slurm-versions_release-notes.html). The MIG topic now lists what a MIG node needs on every boot, and recommends a node lifecycle action that applies it and fails the node if MIG mode can't be enabled. For more information, see [Configuring Multi-Instance GPU (MIG) in AWS PCS](./mig-configuration.html). You can configure Slurm Generic Resource (GRES) records for a compute node group with the `gresCustomSettings` property, and declare the schedulable GRES with the `Gres` custom Slurm setting. AWS PCS also enables GRES autodetection by default on compute node groups that have GPUs. For more information, see [Configuring custom GRES settings in AWS PCS](./gres-custom-settings.html). The Slurm REST API reads the username from the `name` field within the `id` claim of a JWT. The top-level `sun`, `username`, and custom `userclaimfield` claims are deprecated on Slurm 26.05 and later. For more information, see [Authenticating with Slurm REST API in AWS PCS](./slurm-rest-api-authenticate.html). Added a topic that describes how Slurm models CPU topology and GPU affinity, what AWS PCS configures on each Slurm version, and how to configure the socket layout of a compute node group. A troubleshooting topic for `INVALID_REG` node registrations is also available. For more information, see [Configuring hardware topology in AWS PCS](./hardware-topology.html). Added a topic that describes how to partition NVIDIA GPUs into Multi-Instance GPU (MIG) instances and schedule them as GRES types on a compute node group, including the known limitations for powered-down nodes. For more information, see [Configuring Multi-Instance GPU (MIG) in AWS PCS](./mig-configuration.html). | 2026-09-09  

Diff

diff --git a/pcs/latest/userguide/doc-history.md b/pcs/latest/userguide/doc-history.md
index fcc5b5d..612960c 100644
--- a//pcs/latest/userguide/doc-history.md
+++ b//pcs/latest/userguide/doc-history.md
@@ -15 +15 @@ September 30, 2026 | AWS managed policy update |  AWS PCS updated the AWSPCSServ
-September 11, 2026 | Support for Slurm 26.05, custom GRES settings, and hardware topology |  AWS PCS supports Slurm 26.05. Clusters running 25.11, 25.05, and 24.11 can update directly to 26.05. A single sample AMI now supports every Slurm version that is not EOL, and the AMI name no longer contains a Slurm version. For more information, see [Slurm versions in AWS PCS](./slurm-versions.html) and [Release notes for Slurm versions in AWS PCS](./slurm-versions_release-notes.html). You can configure Slurm Generic Resource (GRES) records for a compute node group with the `gresCustomSettings` property, and declare the schedulable GRES with the `Gres` custom Slurm setting. AWS PCS also enables GRES autodetection by default on compute node groups that have GPUs. For more information, see [Configuring custom GRES settings in AWS PCS](./gres-custom-settings.html). The Slurm REST API reads the username from the `name` field within the `id` claim of a JWT. The top-level `sun`, `username`, and custom `userclaimfield` claims are deprecated on Slurm 26.05 and later. For more information, see [Authenticating with Slurm REST API in AWS PCS](./slurm-rest-api-authenticate.html). Added a topic that describes how Slurm models CPU topology and GPU affinity, what AWS PCS configures on each Slurm version, and how to configure the socket layout of a compute node group. A troubleshooting topic for `INVALID_REG` node registrations is also available. For more information, see [Configuring hardware topology in AWS PCS](./hardware-topology.html). Added a topic that describes how to partition NVIDIA GPUs into Multi-Instance GPU (MIG) instances and schedule them as GRES types on a compute node group, including the known limitations for powered-down nodes. For more information, see [Configuring Multi-Instance GPU (MIG) in AWS PCS](./mig-configuration.html). | 2026-09-09  
+September 11, 2026 | Support for Slurm 26.05, custom GRES settings, and hardware topology |  AWS PCS supports Slurm 26.05. Clusters running 25.11, 25.05, and 24.11 can update directly to 26.05. A single sample AMI now supports every Slurm version that is not EOL, and the AMI name no longer contains a Slurm version. For more information, see [Slurm versions in AWS PCS](./slurm-versions.html) and [Release notes for Slurm versions in AWS PCS](./slurm-versions_release-notes.html). The MIG topic now lists what a MIG node needs on every boot, and recommends a node lifecycle action that applies it and fails the node if MIG mode can't be enabled. For more information, see [Configuring Multi-Instance GPU (MIG) in AWS PCS](./mig-configuration.html). You can configure Slurm Generic Resource (GRES) records for a compute node group with the `gresCustomSettings` property, and declare the schedulable GRES with the `Gres` custom Slurm setting. AWS PCS also enables GRES autodetection by default on compute node groups that have GPUs. For more information, see [Configuring custom GRES settings in AWS PCS](./gres-custom-settings.html). The Slurm REST API reads the username from the `name` field within the `id` claim of a JWT. The top-level `sun`, `username`, and custom `userclaimfield` claims are deprecated on Slurm 26.05 and later. For more information, see [Authenticating with Slurm REST API in AWS PCS](./slurm-rest-api-authenticate.html). Added a topic that describes how Slurm models CPU topology and GPU affinity, what AWS PCS configures on each Slurm version, and how to configure the socket layout of a compute node group. A troubleshooting topic for `INVALID_REG` node registrations is also available. For more information, see [Configuring hardware topology in AWS PCS](./hardware-topology.html). Added a topic that describes how to partition NVIDIA GPUs into Multi-Instance GPU (MIG) instances and schedule them as GRES types on a compute node group, including the known limitations for powered-down nodes. For more information, see [Configuring Multi-Instance GPU (MIG) in AWS PCS](./mig-configuration.html). | 2026-09-09