Home / The Industry Wire / The AWS Wire

Industry news, read from a vault · beta

The AWS Wire

Everything AWS announced, filtered by the stack you declare in data/stack.json: what is new, what is insecure, what is being retired, what costs more, and what tooling changed for the services you actually run. Everything else is still listed, as withheld, with the reason. Each story with where it came from and who else covered it, corrected where it is read, live from the wire's vault. A beta, with one named reader by their agreement.

The wires: The Industry WireThe AWS WireThe OWASP Wire · Day by dayThe charterFor the desks

What this is

Everything AWS announced, filtered by a declared stack: what is new, what is insecure, what is being retired, what costs more and what tooling changed for the services the named reader runs, with everything else still listed as withheld, with the reason. The stack is a file in the vault (data/stack.json: the services, their aliases and the deadlines that matter), and this page draws it: the deadlines at the top of the edition, each service with the items that touched it. For every story: where it came from, who else covered it, one exact quote with its source, and why it matters. The stories are found, grouped and written by agents, from a registry of sources with a licence tier each (the sources), and every story says what it is: ai-generated, unreviewed until a person has reviewed it. The current edition is of 2026-10-13: first edition: two weeks of AWS, filtered by your stack (Lambda, S3, API Gateway, CloudFront, boto3). Each edition adds what happened and keeps the earlier stories, so the page is the whole wire so far, not one edition of it.

Corrections propagate. When the desk fetches a primary source it could not reach, or finds a story wrong, it corrects the story in the vault and records the correction, dated, in the story’s own changes; this page draws them under the story, in blue, for as long as the vault keeps them, and the edition’s header carries the desk’s note of what was corrected. The vault’s release notes name the stories added and updated in each publish, and the page flags them Updated. A corrected story is corrected where it is read, which is the argument this site makes of every publication.

Read it as an inbox. The bar above the stories says what is new since your last visit, how much of it is for you and how much is not under the lens you read as, and what the wire’s desk says changed in the vault: its release notes, one per publish (data/releases.json), newest first since your last visit. At each story, one tap: Done, Read later, Follow up, Not for me, More like this or Wrong; the story leaves your inbox, and the filters bring it back. Your decisions and what you have seen are kept in this browser first and reach your own vault when you press Update the vault; until then the bar and the Vault button say what is only here. Each wire keeps its own inbox, its own visit and its own lens. How it works.

Read as someone. The same stories reach different readers. Choose a persona and the edition shows what reached them, through which concern, and what was withheld, with the reason. That join is recorded in the vault by the wire’s own code (pipeline/join.py), not computed here; the page shows the record. If you are reading this site as one of its personas, the lens follows it.

The stack. The vault carries the 5 services its named reader runs (data/stack.json: each with its aliases, what to watch it for, and 4 dated deadlines), and the join turns each service into a concern, so under that reader’s lens a story reaches them when it names a service they run and is withheld, with the reason, when it does not. The page draws the deadlines at the top of the edition with the days left, and each service with the items that touched it. To change what reaches the reader, the desk edits the file in the vault; nothing on this site changes.

Who should know. The reach page lists who this wire concerns and how to reach them, by organisation route only, under the contact rules this site publishes: what this site found on the organisations’ own contact pages, and what the vault carries. The charter says what every agent in the chain enforces; day by day shows every wire’s releases and stories by date.

Where it comes from. The data is not on this site. It is in an encrypted vault that the wire’s agents write to, and this page opens it in your browser with a published read key: v202bla5 on dev.send.sgraph.ai. A commit to the vault is on this page within two minutes, with no release of the site. Anyone can read the whole vault, and its history, with sgit clone sgit_public_read_ad5c3f9e1f4d7632db06cd27f6ee6a256063300c426f4a94e7de33cf5a53e892:v202bla5. How the wire works has the contract and the wire’s own documents, read from the same vault.