Amazon SageMaker AI announces training session APIs for serverless model customization

Amazon SageMaker AI serverless model customization now supports training session APIs, giving customers full control over their post-training algorithm without provisioning or managing GPU infrastructure. Managed techniques, including SFT, DPO, and other reinforcement learning methods, let customers pick a technique and a model and have SageMaker AI run the training. With training session APIs, teams get to write the training loop, whether that’s reproducing SFT or DPO on their own terms or implementing a custom loss, a new RL reward signal, a data curriculum, or an algorithm straight from the latest research. Operations such as forward_backward(), optim_step(), and sample() become API calls against a live, stateful session, so customers compose whatever training procedure their technique requires while SageMaker AI handles GPU allocation, model and LoRA loading, distributed execution, fault recovery, checkpoint storage, and security. Customers can call these operations directly from their own Python code to drive reinforcement learning, supervised fine-tuning, or custom training objectives against a live session, with checkpointing and resume built in. Billing is per token processed, so local computation like reward scoring isn’t billed as GPU time. SageMaker AI is also releasing the SageMaker training sessions cookbook, a set of ready-to-run SFT and RL recipes customers can use as blueprints for their own training loops.
Training session APIs are generally available today in US East (N. Virginia), US West (Oregon), and Asia Pacific (Mumbai). To get started, install the SageMaker Python SDK and clone the cookbook, or launch a notebook in SageMaker Studio and connect a coding agent. To learn more, visit the documentation and the Amazon SageMaker AI webpage.
Quelle: aws.amazon.com

AWS CloudFormation now simplifies stack update rollback operations

AWS CloudFormation now makes it simpler to complete an update rollback and get back to deploying. An update rollback returns your stack to a known good state. Starting today, if some resources cannot roll back automatically, force rollback enables you to complete the rollback it in a single operation. It works across every CloudFormation workflow, from the AWS CLI, and SDKs to AWS CDK and AI agents.
With force rollback, CloudFormation completes the update rollback and returns your stack to a deployable state in a single operation, instead of requiring you to identify, list, and retry the operation for each affected resource. Any resource that still needs attention, such as one affected a change outside CloudFormation, is recorded for you to review and resolve it before your next deployment.
To get started, run continue update rollback with the force rollback option, then create a drift-aware change set to review any configuration differences before your next deployment. To learn more, see  Continue rolling back an update  in the AWS CloudFormation User Guide.
Force rollback is available in all Regions at no additional cost. Refer to the  AWS Region table  for service availability details.
Quelle: aws.amazon.com