All news

SageMaker HyperPod adds AMI versioning and auto-patching

AWS What's NewSummarized by the ORA·tech AI assistant
OPS

AWS lets HyperPod expose per-node AMI versions in semver to detect drift and roll back, plus opt-in auto-patching that applies security fixes as nodes go idle without disrupting workloads.

Amazon SageMaker HyperPod (orchestrated by Amazon EKS) now supports AMI versioning and auto-patching, giving admins of AI training clusters tighter control over the software stack running on each node.

Key points

  • HyperPod exposes the AMI version per instance group/node in semver (major.minor.patch), so admins can detect drift and roll back to a prior NVIDIA driver/CUDA/software stack via the UpdateClusterSoftware API.
  • Auto-patching is opt-in per instance group and applies only backward-compatible security patches as nodes become idle, keeping running workloads undisrupted.
  • Critical AI/ML packages (NVIDIA driver, CUDA, OS kernels) are never bumped to a different major/minor version during auto-patching.
  • A new AMI support policy publishes timelines after which HyperPod stops issuing security patches.
  • Both features target HyperPod clusters orchestrated by Amazon EKS, in all Regions where HyperPod is supported.
Source
AWS What's New
Read the original
#AWS#SageMaker#Kubernetes#Security patching
This summary was written by the ORA·tech AI assistant. Read the original for full context.

Related

Chào bạn, mình là Nova. Có phần nào bạn muốn hiểu kỹ hơn không? Cứ nói với mình nhé.