AI Weekly Malaysia

Simon Willison argues that pay-by-usage APIs and services need default hard budget caps — the kind that cut off usage and return errors once a monthly limit is hit — rather than soft caps that only send a warning email. He points to AWS, which on 16 September launched a new experience where a project that reaches its monthly spend limit is paused for the rest of the month, and notes Google Cloud shipped similar 'Spend Caps' in July. Willison wants hard caps to be the default, with an explicit opt-in checkbox to remove them for people who accept the risk of a runaway bill.

Why: If you let coding agents or personal agents spin up paid APIs, hosted apps, or storage/compute on your behalf, check today whether your provider's cap is hard or soft — a warning email at midnight does not stop the meter. AWS's new spend limit pauses the project for the month, which protects your wallet but breaks your app, and the settings page warns the feature is only being released to a limited number of customers, so existing accounts likely cannot rely on it yet; Google Cloud's Spend Caps can be set per service within a project. Decide per project which you want: a hard stop, or an uncapped account you actively monitor.

AWS released Strands Decider 2B, an open-source 'decision model' inspired by TypeSafe's Jev, the same week OpenAI announced a comparable offering. Built on the torso of Qen3.5-2B, it doesn't generate text — it picks between pre-decided options and returns a calibrated confidence score, and it's small enough to run locally. Amazon distinguished engineer Marc Brooker built an early version after seeing Jev; it briefly topped the Jevbench ranking for models of its size before AWS cleaned it up and shipped it via Strands Labs.

Why: If your agent workflow uses a full LLM call just to answer 'what do I do next?', a 2B local decider with confidence scores can replace that step with lower latency and no per-call API bill — and because the answer domain is closed, you can gate actions on the confidence value instead of parsing free text. Worth benchmarking on your own routing steps before assuming it beats your current prompt.

AWS CEO Matt Garman said Amazon has stopped using NDAs in its dealings with government agencies, as part of a blog post pushing back on data center opposition while Amazon seeks approval to build new data centers. The post cites New York's one-year moratorium on permits for large data centers and claims more than 100 data center moratoriums are being considered across the US. Garman also argues data centers are not major water users, saying direct data center water consumption is 0.5% of all US industrial water usage, less than golf courses and almond farming.

Why: The concrete change is Amazon's NDA policy for government agencies, so builders should not expect any immediate AWS product, region, or pricing change from this post. The actionable signal is the 100+ proposed US data center moratoriums: if they advance, they could affect where and how fast cloud/AI capacity expands, which matters to teams making multi-year compute or data-residency plans. The article provides no Malaysia-specific detail, so treat it as a global cloud-infrastructure policy signal rather than a local announcement.

Tom's Hardware reports that Amazon and Synopsys signed a multi-year, billion-dollar IP agreement aimed at accelerating AI chip design, with Synopsys adopting Amazon Bedrock to deploy AI agents on AWS compute and storage. Beyond the deal size and the Bedrock adoption, the item as retrieved contains no pricing, timeline, named products, or technical detail — the page text is almost entirely site navigation and subscription prompts. Treat this as a deal announcement, not a technical write-up.

Why: The only concrete claim is that a major EDA/IP vendor will run its AI agents on Amazon Bedrock rather than a self-hosted or multi-cloud stack. If you already build agent workflows on Bedrock, that is a mild validation signal for the runtime; if you are evaluating agent platforms for a design, verification, or CAD-adjacent tool, it hints that AWS-native agent infra is where a large incumbent is placing its bet. Nothing here changes what you should build this week — there is no pricing, no API, no release date, and no benchmark to act on.