Amazon Says Cloud Infrastructure In Bahrain, UAE 'Beyond Saving'
Amazon Web Services says damage from Iranian retaliatory strikes has left its Bahrain facility and one of three UAE data-hosting zones beyond restoration, Reuters reported. The outage raises a direct regional availability risk for customers and puts resilience and geopolitical exposure at the center of Amazon’s cloud story.
Reuters reported on September 15 that AWS cannot restore access to its cloud-computing facility in Bahrain or one of three data-hosting zones in the UAE after extensive damage from Iranian retaliatory strikes. AWS said the damage spanned multiple Availability Zones and exceeded what its regional and multi-AZ services are designed to withstand.
The report points to a disruption more severe than a routine service outage: infrastructure in Bahrain was described as beyond saving, while resources and data held exclusively within the affected UAE zone were also impacted. The account does not state how many customers, applications or data sets were affected, nor does it quantify the financial cost to AWS or Amazon.
The mechanism for Amazon is operational rather than immediately tied to a disclosed revenue figure. AWS availability zones underpin cloud hosting and regional redundancy, so permanent infrastructure loss can create replacement-capacity, customer-migration and resilience costs while exposing the limits of multi-zone protection in a conflict area. Amazon reported fiscal-year 2025 revenue of $716.9B and a 10.8% net margin, but those company figures do not isolate Bahrain or UAE exposure.
The reporting is attributed to Reuters and AWS status updates; ZeroHedge’s headline does not add an independent damage estimate. It also does not establish the duration of the outage, the restoration plan for the affected sites, or whether AWS expects a material effect on consolidated results.
The next decisive evidence would be AWS’s restoration updates, customer disclosures and Amazon’s next earnings or regulatory filing. Key questions are how quickly replacement capacity is brought online, whether customers can recover data from other regions, and whether Amazon discloses impairment, rebuilding or security costs.
The infrastructure loss moves the immediate operating risk to the downside for AMZN, with AWS resilience and regional replacement costs now in focus.
The immediate consequence is higher AWS infrastructure and continuity risk, but the report does not quantify customer losses, rebuilding costs or any effect on Amazon’s consolidated results. Amazon’s $716.9B fiscal-year 2025 revenue base and 10.8% net margin provide scale, not a basis for sizing the Bahrain and UAE exposure; the next AWS update or company filing is the evidence that decides whether this remains a contained regional disruption or becomes financially material.
The read weakens if AWS restores affected capacity quickly, customer data remains recoverable through other regions and Amazon reports no material rebuilding or impairment cost.
CoverageSource: ZeroHedge · Published here TUE, SEP 15 · 10:35 PM ET · the only report in this recordHow this is decided →
STOCK PHOTO · PANUMAS NIKHOMKHAIEarlier context and later coverage are dated relative to this report. Automatically linked reports may cover a broader event.
No later reports linked yet.
Follow this story to find new evidence in your Following desk.
Amazon’s fiscal-year 2025 revenue was $716.9B, so the regional outage may remain financially contained if replacement capacity and customer failover are achieved without material disclosure.
AWS said the damage spanned multiple Availability Zones and exceeded the resilience its regional and multi-AZ services were designed to withstand, making permanent capacity loss and customer disruption the stronger near-term risk.
Kept as written · your side, if you take one, is graded privately against licensed closes after 10 trading days · nothing here is advice · How the Wire is made →