Amazon Web Services has officially stated that certain customer data housed in its Middle East cloud infrastructure is permanently unrecoverable following destructive strikes earlier this year. The affected locations include data centers in Bahrain (region me-south-1) and an availability zone in the UAE (mec1-az2). Both sites suffered extensive damage from missile and drone attacks, and AWS admits that data stored exclusively in those areas—with no backups elsewhere—has been lost forever.
What Happened: Regional Sites Hit Hard
The incidents trace back to a series of retaliations after U.S. and Israeli strikes on Iran, prompting counterattacks targeting Gulf states that host U.S. military bases. In these assaults, two AWS data centers in the UAE were struck directly, while one near Bahrain incurred damage in close-proximity drone attacks.
In the UAE, the damage focused on mec1-az2, one of three “availability zones”—distinct physical sections meant to isolate issues. Objects struck the facility around 4:30 AM PST, igniting fires that overwhelmed all recovery efforts. Speaking about Bahrain, AWS said damage spread across several availability zones, overwhelming the region’s infrastructure. Because of the extent, access to resources and data in me-south-1 can no longer be restored.
Why It’s a Major Loss
AWS architecture is built with redundancy—designed to withstand a single availability zone’s failure. But it isn’t built for simultaneous hits across multiple zones or regions. The war damage went well beyond those safeguards. Where entire zones or regions suffer destruction with no offsite copies, the cloud provider can’t recover data—even with robust disaster recovery plans in standard operation.
Most customers were able to recover by migrating operations or restoring data from backups in unaffected regions. However, AWS acknowledged the loss of regions and zones where data existed only in the destroyed infrastructure. AWS has advised its customers to check whether any critical assets were housed solely in me-south-1 or mec1-az2.
To help affected users, AWS paused billing for the impacted regions, alerted governmental authorities in both Bahrain and the UAE, and committed to providing further updates—specifically on the UAE situation later in 2026, and on Bahrain early in 2027.
This marks the first known instance where military action against a major cloud provider led to permanent data loss. The revelation underscores a crucial truth: no matter how solid cloud architecture seems, complete resilience depends on multi-region backups and planning for worst-case scenarios. What to watch now is how AWS—and its users—adjust policies, redundancy guidelines, and risk models in high-conflict zones.
