Amazon Web Services has told customers it cannot restore data held only in parts of its Middle East regions damaged during the conflict with Iran. In a status update this week covering Middle East (UAE) me-central-1 and Middle East (Bahrain) me-south-1, the company said the damage in Bahrain exceeded what its regional and multi-AZ services are designed to withstand.
For the UAE region, AWS wrote:
After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 availability zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-az1 and mec1-az3).
For Bahrain, the assessment covers the whole region:
The damage to our infrastructure spanned multiple availability zones and exceeded what our regional and multi-AZ services are designed to withstand. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in this 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. At the time AWS advised customers to replicate critical data to other regions and, shortly after, to migrate workloads out of the Middle East entirely. Iran's Islamic Revolutionary Guard Corps claimed a second attack on the Bahrain region in July.
AWS says it is replacing the affected infrastructure, has notified relevant authorities, and will update on service restoration in the coming months, with further detail on Bahrain in early 2027. It opened the Bahrain region in 2019 and the UAE region in 2022.
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 resurfaced quickly. Asked what would happen if someone identified an unmarked AWS data center and destroyed it, and whether the system was redundant enough that customers would not notice, she answered:
Yeah, you wouldn't notice. I mean, we might be a bit upset, but you wouldn't notice!
Commenter krick described the position that leaves customers in:
Claims like that are pretty common, they make sense and they should be true, so even though I don't really know AWS redundancy planning in enough detail, I used to trust them. It's really worrying when they outright say it will be ok, and then a week later it turns out to be not ok.
Commenter houssc supplied the missing qualifier:
The caveat is always "if you're using the service correctly" which is not necessarily free. Meaning taking advantage of multiple geo zones, building in redundancy to your stack, etc.
Commenter jacquesm extended that into the misconception he sees most often, that teams believe they are doing it right because they are using AWS:
They don't realize that AWS is a toolbox, not a 'ready made solution for redundancy against all catastrophes you are possibly exposed to'.
The documentation supports that reading. S3 Standard and its related storage classes redundantly store objects across a minimum of three availability zones within a region, and AWS states durability of 99.999999999% per year. Both are regional properties. Commenters pulled AWS disaster recovery guidance showing the company has long told customers to copy backups to another region, including the line that all DR strategies require data sources to be backed up within the region and then copied to a recovery region.
Where the thread divided was on who should have known. Commenter albert_e argued the knowledge is not hidden, since even the most foundational AWS certification teaches the shared responsibility model and where the customer's obligations begin.
Others held the vendors responsible for the impression. Commenter mhitza argued that cloud providers pushed the idea onto executives through marketing and conference channels, comparing it to how AI narratives have reached executives over the past two years. Commenter lelanthran put the practical version as a question:
Who is a CEO going to believe? Amazon, Microsoft and the entire IT infra division or that lone SRE who disagrees with them?
Commenter dijit offered a structural explanation. Distributed storage trades performance against correctness, and outsourcing means someone else makes that trade, weighted toward what customers notice:
You won't notice that theres a third commit server off-site (unless that site is bombed), but you will notice slower writes.
The sharpest thread concerned customers who could not have replicated elsewhere. AWS says the unrecoverable data was hosted exclusively in the affected zones and region, and one commenter connected that phrasing to data residency obligations that require information to remain within national borders. Encrypted backups sent abroad do not obviously solve it, since the decryption keys would also need to sit outside the jurisdiction to be useful after a regional loss.
That tension was visible in March. A senior cloud architect at T-Systems International warned then that moving workloads during a crisis might restore service while pushing sensitive data outside national borders, and that data residency is law rather than best practice.
Gregor Hohpe, co-author of Enterprise Integration Patterns, argued in March that the exposure is geographic rather than contractual:
The risk is regional, not tied to a provider. The folks who took out ME-CENTRAL can just as easily take out Azure or any other data center.
Six months on, that framing has a concrete outcome attached. Multi-AZ architecture distributes a workload across facilities within roughly 100 kilometers of each other, which protects against the failure modes AWS lists, including power outages, lightning strikes, tornadoes and earthquakes. It does not protect against an attacker who can reach several of those facilities in the same night.
The question that follows is narrower than a multi-region strategy. AWS's phrasing is that the unrecoverable data was hosted exclusively in the affected zones and region, so the practical test for any team is whether anything currently sits in one region with no copy elsewhere, and whether regulatory or contractual obligations permit a copy to leave the jurisdiction at all. Where they do not, the residual exposure is not a gap in the architecture but a constraint on it, and one that belongs in a risk register rather than a runbook.
AWS says it remains committed to supporting customers in the UAE and Bahrain. Customers needing assistance are directed to AWS Support.