Imagery confirmed missile damage to two Amazon data centers in Bahrain earlier this summer
A fifty-thousand-dollar missile found a half-billion-dollar building, and every promise of uptime written since is now priced against that exchange rate.
The pictures arrived four months late. On July 28, Bloomberg published satellite imagery showing damage at two Amazon data centers in Bahrain, one near Zallaq and one near Askar, corroborating an Iranian Revolutionary Guard Corps claim from days earlier that its missiles had destroyed the sites (Bloomberg, Jul 28). The lower-resolution frames from the European Space Agency's Sentinel-2 constellation show the same scarring (Gizmodo, Jul 28). Amazon itself has said nothing. The silence is the story now as much as the craters are: the world's largest cloud operator took a direct state-on-state military hit and has chosen not to publicly confirm it.
What can be confirmed comes from paper instead of photographs. The AWS service dashboard posted an April 30 update stating that the company's UAE and Bahrain regions "suffered damage as a result of the conflict in the Middle East" and cannot support customer applications, with repairs expected to take several months (Ars Technica, May 1). The same update suspended billing in both regions, after Amazon had already waived all usage charges for March at an estimated cost of $150 million (Ars Technica, May 1). An internal document obtained by Business Insider described fourteen EC2 server racks knocked offline at one site, five more affected, flooding from fire-suppression systems, and failed cooling (Business Insider, via Ars Technica, May 1). Buildings do not file press releases. Their operators' invoices do.
The actors are arranged around the wreckage with clean, opposed incentives. Iran's Revolutionary Guard wants American power in the Gulf degraded without striking American soil, so it hit the buildings where the Pentagon's logistics and intelligence processing physically sit; AWS hosts CENTCOM systems across the Gulf, and the CIA's classified cloud contract splits workloads among Amazon, Microsoft, Google, Oracle and IBM through exactly this kind of facility (Shatterbelt analysis, Mar 26). Amazon wants the Pentagon contracts worth billions and the Gulf consumer market too, and until February those goals did not conflict. Bahrain and the UAE want to be the digital capitals of the region; their sovereign wealth funds underwrote the buildout. The Gulf customer, from Dubai ride-hailing app Careem to regional banks, just wanted the ninety-nine point nine nine percent uptime the contracts promised.
The cloud always had an address. Now it has a blast radius.
Separate the trigger from the pressure. The trigger was July's missile salvo and the imagery that confirmed it. The slow pressure is five years of concentration: two AWS regions in the Gulf, one Azure region in the UAE, one Google region in Doha, all built for latency and tax advantage inside Iranian missile range, all sharing power grids, desalinated cooling water and submarine cable landings (Shatterbelt, Mar 26). Seventeen submarine cables run through the Red Sea carrying most traffic between Europe, Asia and Africa, and Iran closed the Strait of Hormuz during the same weeks, putting both of the world's data corridors inside an active conflict zone at once (Greymantle Risk Advisory, Mar 23). The war began on February 28 with American and Israeli strikes on Iran; the first drone hits on Amazon facilities followed within days (Ars Technica, May 1). Iran struck the Bahrain facility again on March 24, twenty-four days after the first hit, the same target twice in under a month (Shatterbelt, Mar 26).
History offers one bounded model. In 1999, NATO bombed the Radiotelevizija Srbije headquarters in Belgrade, a civilian broadcast building that also carried state command communications, and killed sixteen staff inside. The lesson then is the lesson here: when a building serves both commerce and command, the military treats the second use as the only one that matters, and the civilians sharing the roof pay first. What is different this time is scale and ownership. Serbian state television belonged to the state it fought for. Amazon belongs to shareholders, and Iran made the targeting choice explicit by publishing a list on March 11 naming Google, Microsoft, Palantir, IBM, Nvidia and Oracle as potential targets (Shatterbelt, Mar 26). A state army put listed American companies on a target board. That had no precedent.
The counterargument deserves its say. States have always spared the financial and communications plumbing that both sides need; even at Cold War heights, nobody bombed SWIFT or the transatlantic cables, because mutual hostage-taking kept the wires up. Iran may be making the same calculation in reverse, hitting Amazon hard enough to signal while leaving Gulf banking rails repairable, which is roughly what happened: ATMs and payment systems across the UAE froze after the March strikes but came back (Shatterbelt, Mar 26). If Tehran's goal were paralysis rather than pressure, the damage would look far worse than the imagery shows. The read that Iran is pricing Amazon's presence rather than erasing it fits the evidence better than the alternative.
Follow who pays. Amazon pays twice: the $150 million in waived charges already booked, then months of unbilled capacity while the buildings are rebuilt, a recovery window long enough that the company itself told customers to migrate out of the regions permanently (Ars Technica, May 1). Careem moved itself overnight to other data centers and survived (Ars Technica, May 1). The customers who never configured backups in a second country did not, and their business-interruption policies almost certainly exclude acts of war, the standard exclusion that Lloyd's and the big reinsurers are now re-examining for Gulf digital assets (Shatterbelt, Mar 26). Meanwhile London-based developer Pure Data Centre Group has paused Middle East investment until the conflict subsides (Ars Technica, May 1), the first visible defection from the Gulf buildout. The profits migrate with the workloads, to Ireland, Frankfurt and Singapore data centers whose landlords never appear in a missile trajectory analysis.
Sam Winter-Levy of the Carnegie Endowment called the strikes "a harbinger of what's to come" in the Financial Times, and the mechanism behind his phrase is simple: dual-use worked only while nobody shot at it (Financial Times, via Greymantle, Mar 23). Once one belligerent treats commercial cloud as a military target, every military on earth must assume its own contractors' buildings are aimed at, and every cloud buyer must assume the region they chose for latency reasons can go dark for half a year with no insurance check coming. That assumption reprices data centers everywhere, not just in the Gulf.
Watch what confirms this. If AWS extends its suspension beyond summer, if other hyperscalers quietly stop quoting new Gulf capacity, and if Gulf sovereign funds begin demanding hardened, dispersed facilities as a condition of hosting, the migration is real and permanent. Watch what breaks it: a fast, fully billed restoration of both regions, fresh Gulf capacity commitments from Microsoft or Google, and customers moving back. That outcome would mean the March and July strikes were a spike, not a regime change, and the Gulf stays the region's digital capital.
The consequence lands on people with names and addresses: a Bahraini operations engineer keeping a dead building cool enough not to corrode, a Dubai founder whose company died because its database lived in one zone, a claims adjuster reading a war exclusion aloud to a client who thought the cloud meant nowhere. The cloud always had an address. Now it has a blast radius.