Simon Willison argues that pay-by-usage services should enforce hard budget caps by default—stopping service when spending hits a limit rather than just sending warnings—because coding agents make it too easy to accidentally rack up massive bills. AWS and Google Cloud recently launched these features, but they need to become standard across the industry.

• Soft budget caps (warning emails) fail in practice because automated agents and unattended services can incur thousands in charges overnight before anyone notices the alert.
• AWS and Google Cloud both launched hard spending limits recently (September and July 2026), pausing projects when monthly budgets are exceeded, but adoption and availability remain limited.
• The feature should be mandatory by default with an explicit opt-in checkbox to remove caps, shifting the burden of risk from users who fear bankruptcy to those willing to accept it.
• Many developers avoid AWS for personal projects specifically because of runaway cost fears, so hard caps would unlock adoption from risk-averse users.

DuckLabs, the company behind the popular DuckDB analytics database, is being acquired by AWS in early September. The core open-source projects will remain free under the MIT license and governed by the nonprofit DuckDB Foundation, but the team gains AWS's infrastructure and reach to scale the technology further.

• DuckDB hits over 1 million downloads daily and the founders realized their bootstrapped model couldn't support the project's growth trajectory without becoming a bottleneck
• All core Duck Stack components (DuckDB, DuckLake, Quack) stay open-source under MIT license with the DuckDB Foundation maintaining stewardship
• AWS has committed long-term support and the DuckLabs team of 30+ people will remain together in Amsterdam, focusing on technical work rather than sales operations

AWS introduced the Nitro Isolation Engine on its new M9g and M9gd Graviton5 instances and used Isabelle/HOL to prove that it enforces strict VM isolation. They modeled the engine in a subset of Rust (μRust), wrote Separation Logic specifications, and proved functional correctness, memory safety, and noninterference to guarantee confidentiality and integrity.

• AWS deployed a formally verified hypervisor component (Nitro Isolation Engine) into production commercial cloud infrastructure for the first time, on new M9g/M9gd Graviton5 instances.
• They produced 330,000 lines of machine-checked Isabelle/HOL proofs, matching seL4's verification scale, covering functional correctness, memory safety, and noninterference.
• The proof approach modeled the engine in a custom μRust subset (no traits/dynamic dispatch) with Separation Logic specs and a weakest-precondition calculus via their open-source AutoCorrode library.
• Every guest-state-touching operation must pass through this engine, which checks requests against the formal spec to mathematically guarantee VM confidentiality and integrity.

Amazon S3 now lets you attach multiple named annotations—structured JSON or plain text—directly to objects and manage them independently via the GetObjectAnnotation and ListObjectAnnotations APIs. This feature scales to petabytes, works across storage classes, and avoids separate metadata systems.

• S3 now supports multiple independently-managed named annotations (JSON or text) per object via new GetObjectAnnotation and ListObjectAnnotations APIs.
• Annotations are billed at standard S3 rates regardless of the parent object's storage class, so archiving to Glacier doesn't cut annotation costs.
• Designed to eliminate the need for a separate metadata database by keeping context like media specs, AI summaries, or compliance data attached directly to the object.

AWS introduced Amazon Bio Discovery, an AI-driven platform that lets researchers run complex drug-design workflows without coding. It provides a library of biological foundation models, an AI agent for workflow setup and analysis, and links to lab partners for synthesis and testing, cutting months of work down to weeks.

• AWS launched Amazon Bio Discovery, a no-code AI platform letting scientists run drug-design workflows using foundation models plus an AI agent, cutting months of research into weeks.
• In a Memorial Sloan Kettering/Twist Bioscience collaboration, nearly 300,000 AI-designed antibodies were narrowed to 100,000 for physical lab testing.
• Bayer, Broad Institute and Voyager Therapeutics are early adopters, and 19 of the top 20 global pharma companies already use AWS cloud services.
• AWS is separately partnering with Boston Consulting Group and Merck on an AI tool to improve clinical trial site selection.

Signal president Meredith Whittaker highlighted the reliance of the encrypted messaging app on Amazon Web Services (AWS) following a recent outage that affected multiple companies. She emphasized the lack of alternatives in the cloud infrastructure industry, pointing out that only a few major players dominate the space, which poses risks for global communication services. Whittaker hopes the incident can serve as a wake-up call regarding the concentration of power in the tech industry.

• Signal's dependence on AWS isn't a choice—only a few companies (AWS, Azure, Google Cloud) dominate cloud infrastructure, leaving no real alternatives for global-scale services.
• Whittaker pushes back on criticism (e.g., from Elon Musk) by reframing the issue: the real problem is the lack of competitors to these dominant cloud providers, not Signal's decision to use them.
• Signal only partially relies on AWS and encrypts user conversations so AWS itself cannot access them.
• The outage exposed the fragility of concentrating critical infrastructure among a few big providers, disrupting Signal and many other major services simultaneously.