Glonce

AWS says Bahrain, UAE data centers hit by war can't be restored

infrastructureThe Glonce editorsHacker News🔥64Glonce rating64Impact60Novelty45Relevance80Surprise50Players80Credibility75

AWS confirmed in a Health Dashboard status update on September 15-16, 2026, that it cannot restore access to its Bahrain cloud region or to one of the three availability zones in its UAE region, identified as mec1-az2. AWS said the damage to its infrastructure spanned multiple availability zones and exceeded what its regional and multi-AZ services are designed to withstand.

The damage traces back to March 2026, when the United States and Israel struck Iran and Tehran retaliated with missile and drone strikes against Israel and Gulf states hosting U.S. military bases. Two UAE data centers were hit directly by drones, and a drone strike near a Bahrain facility caused physical infrastructure damage. After that first Bahrain zone went down, AWS told customers to migrate their workloads elsewhere, and most did. A second Bahrain availability zone was then disrupted in April 2026, taking the entire Bahrain region offline.

AWS said it has since assessed all the affected infrastructure and exhausted every option for restoring data and resources that customers had not migrated out before the Bahrain region became unavailable. The company says it is helping affected customers re-establish operations in other regions, using backup copies or other workarounds; whether any given customer's data survives depends on whether they had a backup stored outside Bahrain or outside the mec1-az2 zone before the strikes.

AWS has not put a date on full recovery. It has promised a further update on the UAE zones, where it is still working to restore the other two availability zones, within the coming months, and a further update on Bahrain in early 2027. No dollar figure for the damage or the data lost has been disclosed, no customer count has been given, and AWS has not named an individual spokesperson behind the statement.

Key facts

  • AWS cannot restore its entire Bahrain cloud region or the mec1-az2 availability zone in its UAE region after war damage.
  • Two UAE data centers were struck directly by drones in March 2026; a separate drone strike near a Bahrain facility also caused physical damage.
  • A second Bahrain availability zone was knocked out in April 2026, after the first was already damaged in March, taking the whole Bahrain region offline.
  • AWS says it has exhausted every option to restore data that customers had not already migrated out of Bahrain before it went dark.
  • AWS has committed only to vague timing for further updates: the coming months for the UAE, early 2027 for Bahrain, with no dollar cost or customer count given.

Why it matters

This is a confirmed case of a major public cloud provider permanently losing customer data and infrastructure to war damage, not a routine outage. It undercuts a basic assumption behind multi-availability-zone cloud design, that failures in separate zones stay independent of each other: AWS itself said the damage here spanned multiple zones and exceeded what its regional and multi-AZ services were built to survive.

Who it affects

Anyone who hosted data, workloads or backups exclusively in AWS's Bahrain region, or in the UAE's mec1-az2 zone, without a copy stored elsewhere. That includes businesses and any government or enterprise customers using AWS's Middle East infrastructure. More broadly, it affects Gulf states positioning themselves as AI and cloud hubs, whose data center buildout now has to account for regional conflict as a real infrastructure risk rather than a tail scenario.

How to use it

There is no product here to use, but the practical takeaway is direct: recovery for any affected customer depends entirely on whether they had a backup outside the damaged region or zone before the strikes. AWS had already told Bahrain customers to migrate workloads out after the first zone was hit in March 2026, and most did before the region went fully offline in April, which is the difference between losing data and merely losing access to a region.

How solid is it

The item's own WSJ source article could not be fetched (paywalled, HTTP 401), so this account is built from four independently fetched, corroborating reports (Times of Israel, Insurance Journal, Investing.com and Streamlinefeed) that quote the same AWS status-update language verbatim, including the mec1-az2 zone identifier and the 'exceeded what our regional and multi-AZ services are designed to withstand' line. The core facts, the unrecoverable Bahrain region, the unrecoverable UAE zone, and the March/April strike timeline, match across all four. One outlet's claim that Iran's Revolutionary Guard Corps specifically claimed responsibility for targeting Amazon over its military support is not corroborated by the other three sources and is not used here.

Risks and caveats

No source gives a dollar figure for the physical damage or the data lost, or a count of how many customers were affected. No individual AWS spokesperson or executive is named; every AWS statement traces back to an unnamed status-update or Health Dashboard post. No firm restoration date exists for either region, only 'coming months' for the UAE and 'early 2027' for Bahrain. And none of the corroborated reporting says Iran deliberately targeted AWS or Amazon specifically; the strikes are described as retaliation against Israel and against Gulf states hosting U.S. military bases, with the AWS facilities as collateral damage rather than the stated target.

“The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand.”

— AWS, Health Dashboard status update