AWS Confirms Permanent Data Loss in Middle East Regions After Conflict Damage

Customers told data in damaged UAE and Bahrain availability zones cannot be restored

By LineZotpaper
Published
Read Time2 min
Amazon Web Services has informed customers that data stored exclusively in parts of its Middle East regions damaged during the conflict with Iran is unrecoverable, marking a rare admission that its multi-AZ redundancy design was insufficient against the scale of the attack.

In a status update covering the Middle East (UAE) me-central-1 and Middle East (Bahrain) me-south-1 regions, AWS said that damage in Bahrain exceeded what its regional and multi-AZ services are designed to withstand. For the UAE region, the company stated it was unable to restore access to resources and data hosted exclusively in the mec1-az2 availability zone, though it continues work on recovering regional and other zonal resources. For Bahrain, the assessment covers the entire region.

InfoQ reported in March that Iranian drone strikes had damaged three AWS data centers across the two regions, with two of the three UAE availability zones significantly impaired and one Bahrain facility hit. Iran's Islamic Revolutionary Guard Corps claimed a second attack on the Bahrain region in July. AWS earlier advised customers to replicate critical data to other regions and to migrate workloads out of the Middle East entirely.

Community reactions on Hacker News have centered less on the strikes than on what customers understood they were buying. A 2025 television interview with an AWS leader, which resurfaced quickly, included her response to a question about destruction of an unmarked data center: 'Yeah, you wouldn't notice. I mean, we might be a bit upset, but you wouldn't notice!' Commenters noted that such claims assume proper use of multi-geo zones and built-in redundancy, which not all customers implement.

AWS says it is replacing affected infrastructure, has notified relevant authorities, and will provide further detail on service restoration in the coming months, with an update on Bahrain expected in early 2027.

§

Analysis

Why This Matters

  • Demonstrates that cloud infrastructure is not immune to physical attacks and that even multi-AZ design has limits against coordinated strikes.
  • Forces customers to reassess disaster recovery assumptions and the implicit trust placed in cloud provider redundancy claims.
  • Could accelerate regulatory scrutiny of critical cloud infrastructure dependencies and push enterprises toward multi-cloud or hybrid strategies.

Background

AWS operates data centers in multiple geographic regions, each containing multiple availability zones (AZs) designed to be isolated from one another. This architecture is marketed to protect customers from single-point failures such as power outages or natural disasters. However, the infrastructure is still physically vulnerable to targeted military attacks. The conflict between Iran and Israel has escalated since early 2026, with Iran striking civilian and economic targets, including data centers in the UAE and Bahrain. AWS had previously advised customers to migrate workloads out of the Middle East after the initial March strikes.

Key Perspectives

AWS: Argues the damage exceeded the design parameters of its regional and multi-AZ services, and is working to replace infrastructure and restore service where possible. The company has notified relevant authorities. Affected Customers: Face permanent data loss for workloads that were not replicated across regions. Some express frustration that AWS’s earlier reassurances about redundancy created a false sense of security. Critics and Skeptics: Point to the resurfaced interview where an AWS leader said customers wouldn't notice if a data center was destroyed, calling that statement misleading. Commenters note that proper use of multiple geographic zones and application-level redundancy is not automatic.

What to Watch

  • Whether AWS provides compensation or migration assistance to affected customers.
  • The progress of infrastructure replacement and service restoration timelines, especially the early 2027 update on Bahrain.
  • Potential shifts in enterprise cloud policy, such as mandatory cross-region replication requirements or increased adoption of multi-cloud architectures.

Sources

Zotpaper

Written by software from the reporting listed above, scored by an automated standards desk, and published without a person reading it first. If something here is wrong, tell the editor and it will be put right.