News For Dev-ops

One of the handy helpers in the Windows Implementation Library (WIL) is wil:: scope_ exit . We've used it to simulate the finally keyword in other languages by arranging for code to run when control leaves a scope. I've identified three places where exceptions can occur when using scope_ exit . auto cleanup = wil::scope_exit([captures] { action; }); One is at the construction of the lambda. What happens if an exception occurs during the initialization of the captures? This exception occurs even before scope_ exit is called, so there's nothing that scope_ exit can do. The exception propagates outward, and the action is never performed. Another is at the point the scope_ exit tries to move the lambda into cleanup . In a naïve implementation of scope_ exit , the exception would propagate outward without the action ever being performed. The third point is when the scope_ exit is destructed. In that case, it's an exception thrown from a destructor. Since destruc...

Learn what's new in Visual Studio Code 1.118 (Insiders) Read the full article Post Updated on April 29, 2026 at 06:00PM Thanks for reading from devamazonaws.blogspot.com

On March 31, 2026 , malicious versions of the widely used JavaScript HTTP client library Axios were briefly published to the npm registry as part of a supply chain attack. The affected versions — 1.14.1 and 0.30.4 — included a hidden malicious dependency that executed during installation and connected to attacker-controlled command-and-control (C2) infrastructure to retrieve a second-stage payload. Because modern development workflows frequently rely on automated dependency resolution during CI/CD builds, environments such as developer workstations and build agents—including those used in Azure Pipelines—may have been exposed if they resolved the compromised versions during installation or update. For a detailed technical analysis of the attack and recommended mitigations, please refer to the Microsoft Security Blog: Mitigating the Axios npm Supply Chain Compromise on the Microsoft Security Blog. Impact on Azure Pipelines This incident does not represent a compromise of Azure...

Amazon SageMaker HyperPod now automatically selects and continuously maintains the optimal network topology configuration for Slurm clusters based on the GPU instance types in the cluster. Network topology directly impacts distributed training performance — when jobs are placed on nodes that are topologically close, GPU-to-GPU communication is faster, NCCL collective operations are more efficient, and training throughput improves. HyperPod dynamically adapts the topology as the cluster evolves through scaling operations and node replacements, so job placement remains optimized throughout the cluster lifecycle without requiring manual updates to topology files or Slurm reconfiguration. HyperPod inspects the instance types across all instance groups at cluster creation, identifies the networking and interconnect characteristics of each instance type, and automatically selects the best-fit topology model. HyperPod supports tree topology for instance types with hierarchical interconnects...

AWS Transform now supports landing zone creation directly within migration workflows, delivering a secure, multi-account AWS environment tailored to your migration needs. By consolidating orchestration into AWS Transform, it automates the setup that previously required configuration across AWS Control Tower, AWS Organizations and AWS Identity and Access Management, accelerating migration readiness with a ready-to-deploy target environment. This new capability extends the end-to-end automation that AWS Transform provides across the migration lifecycle from discovery and migration planning to network and server migration, so that preparing the target environment is no longer a separate workstream. Whether starting from scratch or extending an existing AWS organization, AWS Transform aligns landing zone foundations with AWS best practices, recommending optimal account structures based on migration data and business requirements. Customers can customize Organizational Unit (OU) hierarchi...

Amazon Interactive Video Service (Amazon IVS) Low-Latency Streaming now supports server-side ad insertion (SSAI), enabling you to monetize your live streams with video ads. IVS SSAI integrates with AWS Elemental MediaTailor to stitch ads directly into the video stream on the server, delivering a seamless viewing experience while providing access to ad decisioning, audience targeting, and personalization capabilities.  IVS provides an API operation to insert ad breaks into your live stream, giving creators or operators control over when ads run. Ads are stitched into the stream on the server, reducing the impact of ad blockers and simplifying client-side integration. When a live stream is recorded to Amazon S3, IVS includes ad markers in the recording, enabling you to monetize on-demand content as well.  Amazon IVS is a managed live streaming solution designed to make low-latency or real-time video available to viewers around the world. Visit the AWS region table for a full...