AWS Confirms Permanent Data Loss After Iranian Strikes Destroyed Middle East Data Centres
Six months on from Iranian drone strikes on Amazon's Middle East infrastructure, AWS has finally acknowledged what many suspected: some customer data is simply gone. Permanently. Not recoverable.
Amazon published a dashboard update on September 15 confirming it cannot restore access to data and resources hosted in war-damaged facilities across Bahrain and the United Arab Emirates. Reuters broke the story first, and the implications are significant for anyone who assumed cloud redundancy was an adequate shield against physical destruction at this scale.
In the UAE, the permanent data loss is concentrated in one of three availability zones, specifically mec1-az2. Amazon says it is still attempting to recover resources in the remaining two UAE zones, with replacement infrastructure underway and customers promised updates over the coming months.
Bahrain is a different story entirely, and a considerably worse one. Amazon confirmed it cannot restore access to data across all three availability zones in that region. The company's own dashboard update was unusually candid about why: "The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand."
That sentence deserves a moment. AWS multi-AZ architecture exists precisely to survive localised failures. Missile strikes, it turns out, are not a scenario the redundancy playbook was written for.
The timeline of destruction is worth laying out. Iranian drones first hit Amazon's Bahrain and UAE facilities on March 1, in the opening days of a war triggered by US-Israeli strikes on Iran the previous day. AWS urged customers to migrate workloads elsewhere and issued $150 million in credits. A second strike targeted Bahrain specifically on April 1. Then, on July 24, Iran's Islamic Revolutionary Guard Corps hit a remaining Bahrain data centre structure with missiles, damage later confirmed by satellite imagery.
Amazon had already suspended billing in both affected regions and has spent half a year attempting to piece things back together. For the mec1-az2 zone in the UAE, that effort has now been formally abandoned.
The broader conflict has meanwhile expanded into a regional mess, with attacks on Hormuz and Bab al-Mandeb shipping lanes feeding a global energy crunch. AWS, for its part, says it remains committed to its Bahrain customers long-term and will publish a further update in early 2027.
The episode is a fairly brutal reminder that cloud resilience has physical limits. Georedundancy works against hardware failures and power outages. It works less well when the hardware is being systematically destroyed across multiple sites over several months.