Skip to content
Today
Sections

Build Independently confirmed3 publishers 2 min read Published Updated

AWS ran out of options for the data left in Bahrain when the second zone failed

AWS's status update says the strike damage exceeded what its regional and multi-AZ services were built to withstand. Customers who held data in a single zone in Bahrain or in mec1-az2 are being told it is not coming back.

The Engineer · Build desk

Send a correction

What happened

  • A status update seen by Reuters says AWS cannot restore access to its Bahrain facility or to one of three data-hosting zones in the United Arab Emirates after damage during the Iran war.
  • AWS said at the time that two of its UAE facilities were struck directly, and that a drone strike close to one of its Bahrain facilities physically damaged the infrastructure there.
  • After the first Bahrain zone was damaged in March, AWS told customers to migrate to other regions, and most did before a second zone was disrupted in April and the region became unavailable.
  • The company said it has assessed all the affected infrastructure and exhausted every option for restoring data and resources that were not migrated before the Bahrain region went offline.
  • AWS said it is replacing affected UAE infrastructure and will report on restoration in the coming months, with a further update on Bahrain operations in early 2027.

Why it matters

  • What it limits constraint By the provider's own account, in-region redundancy does not cover damage on this scale. The remaining customer-side control is a copy held in another region.
  • Who has to decide decision Single-zone placement is a durability decision, and teams have to name the volumes and databases that exist in one building only.
  • What it costs cost Customers absorb the recovery work: AWS said it supported them in re-establishing operations elsewhere, using backups where those existed and alternative solutions where they did not.

The operative phrase in the UAE section of the update is "hosted exclusively in one availability zone" [3]. AWS has not called the UAE region lost; the phrase is about resources, and anything with a single copy in mec1-az2 has nothing left to serve it. Engineers are still working on the wider UAE region and on the other two affected zones [4]. Amazon said most of its UAE customers restored operations in other regions by relying on backups or by copying data that remained accessible [11].

AWS wrote down its own design limit. "The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand," the company said in the status update, which Reuters was first to report [2]. An availability zone is a cluster of one or more data centres in the same geographic region [9], and it is a subdivision of the network built to provide redundancy [10]. Spreading copies across three zones in one country covers failures that stop at one zone. Satellite imagery showed hits to two Amazon data centres in Bahrain [18].

Bahrain sets the real recovery target: customers had roughly a month between the damage to the first zone and the loss of the region [19]. A region-exit plan that takes a quarter to execute would not have finished.

For "most customers migrated" to describe your own workload, you have to know which of your resources exist in one zone only, at the level of individual volumes and databases. And each of them needs a copy outside the region. Banking operations were among the systems affected when the outages began, Reuters reported, citing a person familiar with the situation [20].

Siting is the part a customer cannot fix. The Islamic Revolutionary Guard Corps said the Bahrain facilities were struck because of Amazon's support for US military operations, according to the account published by the Spokesman-Review [17]. Iran's retaliation was aimed at Israel and at Gulf states hosting US military bases [13]. The UAE is revising plans for a major AI data-centre project, including by considering dispersing facilities and using underground and blast-resistant infrastructure, Reuters reported [16]. Tuesday's status update was the first public one AWS had issued on the damage in five months [6].

What to watch

  • Whether the promised UAE update says mec1-az2 has been replaced or written off, and whether the other two zones come back with data intact.
  • Whether the authorities AWS notified in Bahrain and the UAE turn this into a rule about where copies of regulated data must sit.
  • Whether any customer or insurer puts a figure on the data AWS says it cannot restore.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence72
Adoption
Not scored
Hype gap+8
Incentives
Not scored
Confidence70

Perspective Coverage

4 publishers
Builder
Builder 28%
Operator
Operator 45%
Investor
Investor 27%
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Amazon Web Services said it cannot restore access to its cloud-computing facility in Bahrain and one of three data-hosting zones in the United Arab Emirates following damage during the Iran war, according to a status update seen by Reuters on Tuesday.

    Reported SupportedView cited source
  2. [2]

    "The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand," AWS said in the status update, which Reuters was first to report.

    Reported SupportedView cited source
  3. [3]

    In the UAE, AWS said it was unable to restore access to resources and data hosted exclusively in one availability zone, known as mec1-az2.

    Reported SupportedView cited source
  4. [4]

    AWS said it is continuing to work on recovering resources across the wider UAE region and in the other two affected zones.

    Reported SupportedView cited source
  5. [5]

    In the UAE, AWS said it was working to replace affected infrastructure and would provide an update on restoration of services in the coming months; it also said it would provide a further update in early 2027 for Bahrain operations.

    Reported SupportedView cited source
  6. [6]

    The damage exceeded what the company's services were designed to withstand, AWS said in its first public update in five months.

    Reported SupportedView cited source
  7. [7]

    After the first availability zone in Bahrain was damaged in March, AWS began recommending that customers migrate their workloads to other regions; most did so before the Bahrain region became unavailable following disruption to a second availability zone in April.

    Reported SupportedView cited source
  8. [8]

    AWS said it had assessed all affected infrastructure and exhausted every option for restoring data and resources that had not been migrated before the Bahrain region became unavailable.

    Reported SupportedView cited source
  9. [9]

    AWS said the damage in Bahrain spanned multiple availability zones, which are clusters of one or more data centres in the same geographic region.

    Reported SupportedView cited source
  10. [10]

    Amazon said it has been unable to access data stored in one of its UAE availability zones, a subdivision of its network designed to provide redundancy.

    Reported SupportedView cited source
  11. [11]

    In the UAE, Amazon said most customers had restored operations in other regions by relying on backups or copying data that remained accessible.

    Reported SupportedView cited source
  12. [12]

    AWS said it had since supported customers in re-establishing operations in alternative regions, using backups where available or implementing alternative solutions to mitigate the impact of inaccessible data.

    Reported SupportedView cited source
  13. [13]

    The disruptions began in March following U.S. and Israeli attacks on Iran, which prompted Tehran to retaliate with missile and drone strikes on Israel and Gulf states hosting U.S. military bases.

    Reported SupportedView cited source
  14. [14]

    AWS said at the time that two of its facilities in the UAE had been directly struck, while a drone strike close to one of its facilities in Bahrain had physically damaged its infrastructure.

    Reported SupportedView cited source
  15. [15]

    AWS said it had notified the relevant authorities in both countries and continued to work with them.

    Reported SupportedView cited source
  16. [16]

    The UAE is revising plans for a major AI data-centre project following the Iranian attacks, including by considering dispersing facilities and using underground and blast-resistant infrastructure, Reuters reported.

    Reported SupportedView cited source
  17. [17]

    The Islamic Revolutionary Guard Corps said the Bahrain facilities were struck because of Amazon's support for US military operations.

    Reported SupportedView cited source
  18. [18]

    Satellite imagery showed hits to two Amazon data centers in Bahrain.

    Reported SupportedView cited source
  19. [19]

    Bahrain customers had roughly one month of warning: the first availability zone was damaged in March and the region became unavailable after a second zone was disrupted in April.

    Derived Supported
  20. [20]

    The AWS outages affected some banking operations at the time, Reuters has reported, citing a person familiar with the situation.

    Reported InsufficientView cited source

Sources

3 independent publishers whose own reporting we read for this story.

  1. amp.insurancejournal.com

    1 article · September 17, 2026

    Amazon’s AWS Facilities in Bahrain, UAE Still Not Restored From Iran War Damage
  2. economictimes.indiatimes.com

    1 article · September 17, 2026

    Amazon's AWS is unable to restore access to Bahrain, one UAE cloud data zone after war damage

  3. spokesman.com

    1 article · September 17, 2026

    Amazon Fails to Recover Some Data in Facilities Hit in Iran War
  4. techspot.com

    1 article · September 17, 2026

    US-Iran war permanently damaged Amazon's AWS infrastructure in the Middle East | TechSpot

Topics and entities

Topics

  • Digital infrastructure in armed conflict
  • Gulf data centres
  • US-Iran war
  • Cloud disaster recovery

Entities