AWS logged a multi-service operational issue on its Health Dashboard Thursday afternoon April 16, affecting unspecified services in an unspecified region, with details still emerging as of Friday morning. [1] The Dashboard is terse by design — Amazon discloses the incident, not the cause — and the entry would ordinarily pass without notice. This was not an ordinary day to post one.

Six weeks ago, three AWS data centers in the United Arab Emirates and Bahrain took Iranian drone damage during the opening phase of the Gulf war. [2] Banking apps went dark across the region. The repair bill, modeled imprecisely from the software outage that followed, ran into the low hundreds of millions. [2] AWS's multi-availability-zone architecture, designed to survive the failure of a rack or a building or a city, was never designed to survive a war zone.

Thursday's incident appears unrelated to the Middle East footprint. But the reading has changed. Where MSM waits for a consumer-facing outage — Snapchat down, Roblox down, Ring doorbells silent — before writing about AWS, the X infrastructure corner now reads every Health Dashboard entry against the wartime context. [1] A shrug during peacetime is a data point during war.

Amazon's next earnings call arrives April 30. The question Matt Garman will be asked is not whether the cloud is resilient. It is whether the cloud is resilient enough for the geography AWS actually operates in.

-- THEO KAPLAN, San Francisco