Cloud Operations

The moment in this demonstration that deserves attention is a failure: the agent's first query returned the wrong results, so it consulted a mapping tool to learn what fields exist and rewrote the query with the correct names. That recovery is the capability, because production logging is never fully documented — field names drift and the schema in anyone's head is out of date. An agent that requires accurate documentation requires the thing nobody has. The scenario is well chosen, since with traffic at ten times normal and every service alerting, the difficulty is not detection but correlated noise. Where the session goes past observability is the business impact estimate, which multiplies observed errors by historical averages and produces a number for leadership whose assumptions are not visible — an unverifiable figure delivered alongside verifiable ones.

AWS re:Invent

The show of hands at the start tells you what this session is about: roughly half the room had generated cost reports in the standard format, and considerably fewer had analysed them. That gap is the whole problem, because producing the export is configuration while turning it into something anyone acts on is the work. The single most valuable element described is unglamorous — an invoice identifier column that lets reported figures match the invoice actually paid, which is the difference between a report and an accountable number. Every cost reporting effort dies at the reconciliation step, usually because aggregation cannot be tied back to a specific charge. The remainder is data preparation rather than analysis, and the detail about needing pattern matching to extract tag values reveals where the real difficulty sits.

AWS re:Invent

Twenty-nine minutes after asking whether anyone really wants to hand production keys to an agent, the demonstration disables tool confirmation entirely. That is not hypocrisy — approving every call would be unwatchable — but the gap between the stated concern and the working configuration is the one every team will meet. The scope makes it concrete: the example prompt blocks network addresses and creates snapshots, which are write operations on production initiated by a chain of reasoning that started as a sentence in English. The design response is decomposition, and the split between an investigating agent and an acting one is where a permission boundary can sit. The construction itself is genuinely simple, and the generated report of 859 critical findings is both the session's most useful artefact and the place the trust question returns in a form nobody can check by hand.

AWS re:Invent