Iran Escalates Attacks on Amazon Data Centers Amid Widening Middle East Conflict
Key Takeaways
- ▸Iran explicitly claimed responsibility for attacking and 'destroying' Amazon data centers in Bahrain, releasing high-resolution satellite imagery as evidence
- ▸Second attack on AWS Middle East infrastructure in five months; earlier drone strikes on March 1 caused months of repairs and forced customer migration
- ▸Independent satellite verification confirms damage, providing rare transparency amid US government efforts to restrict commercial satellite imagery of the region
Summary
Iran's Islamic Revolutionary Guard Corps launched cruise missile strikes against Amazon data centers in Bahrain on July 21, marking the second major attack on AWS infrastructure in the Middle East within five months. Satellite imagery from Europe's Copernicus Sentinel-2 satellites confirmed damage to facilities in the coastal towns of Zallaq and Askar, corroborating claims made by Iran's state media. The attack forced AWS to maintain recommendations that affected customers migrate workloads to alternative cloud regions, with AWS status dashboards indicating the damaged facilities remain unable to reliably support operations since April 30.
The Amazon data center strikes are part of a broader escalation in the US-Iran conflict, with Iranian-backed Houthi forces simultaneously targeting Saudi Arabian oil infrastructure and Red Sea shipping lanes. On July 20, the Houthis declared a formal naval blockade aimed at disrupting oil exports through the Bab el-Mandeb Strait, following up with attacks on oil tankers, refineries, and the critical port of Yanbu on July 25. These coordinated attacks threaten Saudi Arabia's efforts to reroute oil exports away from disrupted Strait of Hormuz shipping lanes, with potential consequences for global energy markets.
- Houthi naval blockade declaration and attacks on Saudi oil infrastructure pose broader geopolitical and economic risks to global energy supplies
- AWS status dashboards remain unchanged since April 30, indicating ongoing operational challenges at affected data center facilities
