Amazon Web Services (AWS) has told customers that some of their data stored in Bahrain and the United Arab Emirates is permanently gone, more than six months after Iranian drone strikes damaged its data centers in both countries. The admission arrived in a September 15 update to the AWS Health Dashboard, first reported by Reuters, and it marks Amazon’s first public word on the incidents since April.
Most cloud outages are measured in minutes and closed with a status-page note. This one has no recovery timeline for Bahrain and a partial one for the UAE, which turns a familiar operational story into something far more consequential for the regulated financial firms that kept their records in the region.
Gulf-licensed brokers, exchanges and payment firms that stored data in-region to satisfy local data-residency rules are precisely the customers who could not move it out, and Reuters has reported that the outage affected some banking operations. What was designed as compliance became exposure, a risk that has kept Amazon (AMZN) stock in focus even though the direct financial hit to the company stays small.
Amazon stock is down about 4% over the past month and roughly 14% off its high, even as AWS posted its fastest growth in 18 quarters. Source: TradingView.The Blunt Wording in Amazon’s Health Dashboard Notice
The language in the dashboard update is unusually direct for a cloud provider. “After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in this region,” Amazon wrote of its Bahrain region, as CNBC reported. The company reached the same conclusion for one of the three availability zones in its UAE region, known as mec1-az2, while it continues working to recover the other two affected zones, mec1-az1 and mec1-az3.
Amazon also described the limits of what it could do. “We assessed all affected infrastructure and exhausted every option for restoring data and resources that had not been migrated before the region became unavailable,” the company said, according to The National. Only data held exclusively in the damaged zones is unrecoverable, so customers who had already replicated their workloads elsewhere were spared. Those who relied on the region alone were not.
Why Multi-AZ Redundancy Did Not Survive a Military Strike
Amazon builds its regions from separate availability zones, isolated clusters of data centers with independent power, cooling and networking, so that a failure in one does not take down the others. That architecture is the backbone of the AWS reliability pitch, and it works against fires, floods and power cuts confined to a single site. It was not built for a military strike that damages several zones at once.
The physical scale of the damage is what broke the model. Amazon said the harm in Bahrain “spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand,” as Insurance Journal reported. Drone strikes on March 1 hit two UAE facilities directly and damaged a Bahrain site through a nearby blast, and a second Bahrain zone went down in April, taking the whole region offline.
Iran’s Islamic Revolutionary Guard Corps claimed responsibility, citing Amazon’s support for the US military, a claim that should be attributed to the group rather than treated as established fact. The lesson for anyone running critical systems is that in-region redundancy stops protecting you when the whole region is the target.
Investor Takeaway
Multi-availability-zone redundancy protects against local failures but not against an event that disables several zones at once, so the AWS Bahrain loss exposes a gap that only cross-region replication closes.
The Data-Residency Trap for Gulf-Regulated Financial Firms
This is where an operational failure becomes a regulatory problem. Financial firms licensed by the Central Bank of the UAE and the Central Bank of Bahrain often face data-residency and outsourcing requirements that push customer and transaction records to stay inside the country. A broker or payment company following those rules to the letter would have kept its data in the AWS Bahrain or UAE region, the exact place the strikes made unrecoverable, leaving compliance and resilience pulling in opposite directions.
The bind has no clean resolution under the current rules. Replicating data to another AWS region in Europe or Asia would have preserved it, but doing so may conflict with residency obligations that require the data to remain onshore. That tension is now a live question for Gulf regulators and for the firms they supervise, and it sharpens the appeal of the isolated sovereign-cloud offerings Amazon has built elsewhere for exactly these residency concerns. Until the rules address geographic redundancy directly, in-region storage remains both a legal requirement and a single point of failure.
What the AWS Outage Means for Amazon Stock and Cloud-Concentration Risk
Amazon has told affected customers to move their workloads to other AWS regions and warned that instability in the Middle East is likely to keep operations unpredictable. It said it expects to share more on the UAE “in the coming months” and will update Bahrain customers in “early 2027,” a timeline that leaves the region’s future unresolved for the better part of a year, as Tom’s Hardware reported. UAE officials are reportedly weighing dispersed, underground and blast-resistant data centers in response.
The financial impact on Amazon stock is negligible against a business this size, which is the awkward part. AWS just posted its fastest growth in 18 quarters and chief executive Andy Jassy raised 2026 capital spending toward $220 billion, so the Gulf loss is a rounding error on the income statement even as it dents the reliability promise the whole cloud pitch rests on.
Amazon (AMZN) stock trades near $250, down about 4% over the month, a move that reflects the broader tech tape more than this event, and the $330 bull versus $185 bear scenario range shows how little a regional outage shifts the long-term case for a company whose $3 trillion valuation rests on AWS. The real exposure is reputational and regulatory, and it lands on the customers who trusted a single region, not on Amazon stock.
Investor Takeaway
The reputational cost is the real one, because AWS sells reliability above all else, and an unrecoverable data loss is the rare event that undercuts that promise for enterprise buyers weighing cloud concentration.