AWS confirms permanent data loss in Bahrain and one UAE zone after drone strikes

AWS confirmed that six months on from the March 2026 strikes it is unable to restore access to the Bahrain region and the UAE mec1-az2 zone, and that some customer data is permanently lost. The company said the physical damage exceeded the resilience its multi-AZ design was built to absorb, and it expects a UAE update in coming months and a Bahrain update in early 2027.

The admission is striking because multi-availability-zone redundancy is the foundational promise AWS sells for durability — the scenario of simultaneous, unrecoverable loss across a region's infrastructure due to kinetic attack falls outside standard cloud failure models. It forces enterprises to confront geopolitical and physical-security risk in cloud architecture decisions, not just software fault tolerance.

An r/aws thread (289 upvotes) captured customer unease while noting hopes that Amazon's $220B spending plan continues. The incident raises hard questions about cross-region backup responsibility: AWS's shared-responsibility model puts data replication on customers, so firms that kept data solely in-region bear the loss — but many assumed AZ redundancy sufficed. Expect renewed scrutiny of multi-region strategies, insurance implications, and whether hyperscalers should disclose physical-security postures for regions in conflict-adjacent geographies. The permanence is the key new fact: this is no longer an outage but an acknowledged unrecoverable loss.