AWS's Bahrain region, anchored by the Zallaq and Askar sites, serves customers across the Middle East, Africa, and South Asia, and Amazon has not publicly confirmed or denied the strike.
Two independent satellite passes have converged on the same two Amazon Web Services facilities in Bahrain, both showing visible damage consistent with this month's claimed Iranian missile strikes.
Bloomberg obtained commercial satellite imagery of the Zallaq and Askar sites after Iran's Islamic Revolutionary Guard Corps (IRGC), via the state-affiliated Tasnim news agency, released its own before-and-after images claiming responsibility for the strikes. The European Space Agency's Sentinel-2 constellation, a public open-orbit imaging program, provided a separate lower-resolution pass over the same locations. Both image sets are consistent with significant damage at both sites. Neither independently confirms the IRGC's claim of total destruction.
The strikes close a months-long escalation arc that began in March, when AWS publicly reported Bahrain-region cloud disruptions tied to Iranian-linked drone activity. By April the targeting had moved from disruption to direct strikes on U.S. technology companies operating in the Gulf. The latest hits, claimed by the IRGC as retaliation for a U.S. attack on an alleged Iranian nuclear site, are the first publicly imaged at hyperscale cloud sites attributed to a state adversary.
AWS Bahrain is more than Amazon's retail plumbing. The Bahrain region sits in Amazon Web Services' Middle East footprint and serves customers across the Gulf, East Africa, and South Asia, including government workloads, regional financial infrastructure, and the cloud backends for companies whose services reach hundreds of millions of users. Damage to Zallaq and Askar, even if partial, is a hit to a piece of the open internet that a Fortune 100 company's regional customers depend on daily.
Amazon has not publicly confirmed or denied the strike. The AWS Health Status dashboard, the company's official incident channel, has stayed silent on the Bahrain event, and the company did not respond to requests for comment. The story has been corroborated across the tech and financial press. Gizmodo first reported the satellite convergence; Bloomberg acquired the imagery. The AWS silence is itself a data point: a Fortune 100 operator of critical infrastructure has not publicly verified what two independent satellite sources have already made visible.
The buildings were hit, and the satellite record is now permanent. Hyperscale cloud regions have become proxy targets when their operator is perceived as state-aligned, and open-orbit satellite imagery is now a real-time witness to the result. Other hyperscale operators run regional infrastructure in the same Gulf neighborhood. They have watched the damage appear on open-orbit imagery in near-real time, and they have watched the targeted operator decline to confirm it.