AWS launched a new sign-up experience that lets new customers create an account with Google, GitHub, Apple, Amazon, or email and land in a configured SageMaker Studio in 2-3 steps. New users get $100 in Free Tier credits spanning Studio notebooks, model customization, training, and endpoint deployments, with no credit card required for most customers. This removes the last friction point — account creation — following earlier changes like 20-second Studio provisioning and Hugging Face deep links.
AWS and Hugging Face announced a new integration that lets developers deploy models from Hugging Face to Amazon SageMaker Studio with a single click, eliminating the previous multi-step process of setting up domains, IAM permissions, and GPU quotas. The move aims to reduce friction for developers moving from model discovery to enterprise deployment.
AWS and Hugging Face announced a new integration that lets developers deploy models from Hugging Face to Amazon SageMaker Studio with a single click, eliminating the previous multi-step process of setting up domains, IAM permissions, and GPU quotas. The move aims to reduce friction for developers moving from model discovery to enterprise deployment.
Amazon reviewed SageMaker JumpStart's 2026 expansion: over 100 new models onboarded from 30 distinct providers between January and September 2026. The catalog now spans multimodal, image/video generation, speech, OCR, retrieval, and compact quantized models, with new Model Hub, one-click deployment configurations, and Hugging Face deep link integration reducing deployment friction.
Amazon reviewed SageMaker JumpStart's 2026 expansion: over 100 new models onboarded from 30 distinct providers between January and September 2026. The catalog now spans multimodal, image/video generation, speech, OCR, retrieval, and compact quantized models, with new Model Hub, one-click deployment configurations, and Hugging Face deep link integration reducing deployment friction.
AWS introduced the ability to create and manage Amazon SageMaker Spaces on SageMaker HyperPod EKS clusters directly from the SageMaker Studio UI. Data scientists can launch JupyterLab and Code Editor environments via a new IDE and Notebooks tab, replacing the previous CLI/kubectl-only workflow. The Spaces add-on itself remains free; users pay for underlying cluster compute and SSH-over-SSM connectivity.
AWS introduced the ability to create and manage Amazon SageMaker Spaces on SageMaker HyperPod EKS clusters directly from the SageMaker Studio UI. Data scientists can launch JupyterLab and Code Editor environments via a new IDE and Notebooks tab, replacing the previous CLI/kubectl-only workflow. The Spaces add-on itself remains free; users pay for underlying cluster compute and SSH-over-SSM connectivity.
An AWS post demonstrates deploying Hugging Face models to SageMaker AI using six open-source agent skills from the Hugging Face Skills repo, working with Kiro and Claude Code. Unguided agents chose outdated TGI containers and produced failed or silently broken deployments; the skills select vLLM from the AWS DLC catalog and add autoscaling, alarms, and teardown.
An AWS post demonstrates deploying Hugging Face models to SageMaker AI using six open-source agent skills from the Hugging Face Skills repo, working with Kiro and Claude Code. Unguided agents chose outdated TGI containers and produced failed or silently broken deployments; the skills select vLLM from the AWS DLC catalog and add autoscaling, alarms, and teardown.
AWS published guidance on administering Amazon SageMaker HyperPod clusters shared by multiple teams through SageMaker Unified Studio. It lays out a four-layer control model—organization, project, cluster, and workload—for governing identity, capacity allocation, and observability. The guidance matters to platform teams running shared accelerator clusters for training and fine-tuning.
AWS published guidance on administering Amazon SageMaker HyperPod clusters shared by multiple teams through SageMaker Unified Studio. It lays out a four-layer control model—organization, project, cluster, and workload—for governing identity, capacity allocation, and observability. The guidance matters to platform teams running shared accelerator clusters for training and fine-tuning.