# Amazon — Introducing managed cluster extensions for observability and user management in Amazon SageMaker HyperPod Slurm

- Company: Amazon (amazon.com)
- Announced: 2026-11-20T23:07:03+00:00
- Category: capability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://aws.amazon.com/blogs/machine-learning/introducing-managed-cluster-extensions-for-observability-and-user-management-in-amazon-sagemaker-hyperpod-slurm/
- Record: https://forck.live/items/39468-introducing-managed-cluster-extensions-for-observability-and-user-management
- Subject: Bedrock / Nova

Amazon SageMaker HyperPod added cluster extensions, AWS-managed software packages that administrators install, configure, update and remove through APIs or the SageMaker AI console. The first two extensions cover observability and user management, including directory integration, and address the drift that comes from lifecycle scripts, which run only when a node is provisioned. HyperPod validates an extension's settings against its schema at submission, so a misspelled setting is rejected before anything reaches a node. Extensions are applied to every node, including nodes added by scale-up or replacement, and each reports its status and per-node health. The company says customers keep full access to every node, including the controller node, and can still SSH in, configure nodes directly and run their own lifecycle scripts. HyperPod recommends extensions for managed software capabilities and custom AMIs or lifecycle scripts for organization-specific software.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/introducing-managed-cluster-extensions-for-observability-and-user-management-in-amazon-sagemaker-hyperpod-slurm/:

> Keeping a shared Slurm cluster for foundation model development in sync entails keeping several separately maintained pieces of configuration matched to what’s running on the nodes. The cluster’s shape lives on multiple configuration files, its software in custom scripts, its network topology in files that must be edited as nodes change, and its users in a roster that an administrator must maintain and rerun. Over time these pieces drift away from what’s actually running, and nothing tells you when they do.
> 
> We believe cluster configurations should be managed the way you manage the rest of your AWS infrastructure. You declare what you want through an API or the console, AWS validates it before it’s applied, the cluster is kept in that state continuously, and you can see whether it’s working. During 2026, Amazon SageMaker HyperPod brought that approach to Slurm clusters, with API-driven Slurm configuration, AMI-based configuration, continuous provisioning, automatic topology management, and deep health checks.

---

Record: https://forck.live/items/39468-introducing-managed-cluster-extensions-for-observability-and-user-management
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
