Amazon AWS Availability Zones in Bahrain and Dubai Go Hard Down After Iran Strikes,

Amazon’s internal response to the Gulf disruptions reveals a stark operational reality: both the Dubai (DXB) and Bahrain (BAH) regions now run with one of their three availability zones “hard down” and a second zone “impaired but functioning,” according to an internal AWS memo obtained by Big Technology. The memo instructs engineers to “deprioritize” the affected regions and to scale services to the “minimal footprint required to support customer migration,” underscoring that normal redundancy and resiliency cannot be expected for the foreseeable future. The communication also notes that capacity is being “freed and reserved” to aid customers who must relocate workloads, a move that signals Amazon’s acknowledgment that the damage is not merely transient but likely to persist for an extended period.

The physical damage cited by the memo aligns with reports of multiple strikes on Amazon’s Gulf data centers. Big Technology reports that the Bahrain facility suffered several attacks, including a Wednesday strike that ignited a fire, while the UAE sites endured “multiple hits.” These incidents appear to be part of a broader Iranian campaign that has, for six weeks now, targeted U.S. tech infrastructure in the region. The Iranian Revolutionary Guard Corps (IRGC) has publicly threatened other American cloud providers—Microsoft, Google, and Apple—suggesting that Amazon’s challenges may foreshadow a wider disruption of Western cloud services across the Middle East.

Amazon’s public-facing stance, as reflected in a recent blog post referenced by the company’s spokesperson, emphasizes customer migration rather than restoration timelines. The blog states that “a large number [of customers] already successfully operating their applications from other parts of the world,” and reiterates the request that “those with workloads in the affected regions continue to migrate to other locations.” Crucially, the internal memo makes no promise about when DXB and BAH will return to normal operations, leaving enterprises with limited guidance on long‑term planning. For businesses that have built critical workloads on the Gulf zones—particularly those seeking low‑latency connectivity to the Arabian Peninsula—this uncertainty translates into potential revenue exposure and the need to re‑architect applications for alternative regions such as Europe, South Asia, or the newly expanding Middle‑East (ME) West region in Saudi Arabia.

From a market perspective, the outage highlights the geopolitical risk premium embedded in cloud infrastructure decisions. Analysts have long warned that reliance on a single provider in politically volatile locales can amplify supply‑chain fragility; the current situation provides a concrete case study. With Amazon’s Gulf zones now operating at reduced capacity, competitors may find an opening to pitch more resilient multi‑region architectures, especially to multinational firms that must meet data‑sovereignty mandates while avoiding single‑point failures. Moreover, the IRGC’s explicit threats to other U.S. tech giants could catalyze a broader shift toward regional diversification, prompting customers to spread workloads across multiple cloud providers—a trend that could erode Amazon’s market share in the Middle East if it does not accelerate its own redundancy investments.

Finally, the episode serves as a reminder that cloud providers are increasingly becoming strategic assets in geopolitical contests. The fact that Iran has chosen to target Amazon’s physical infrastructure—rather than merely cyber‑attacks—suggests a calculus that views data centers as both economic levers and symbols of U.S. technological influence. As the conflict enters its sixth week, the lack of a clear timeline for restoration, combined with the internal directive to “deprioritize” the Gulf zones, signals that Amazon expects a prolonged period of instability. Enterprises with exposure to these zones must therefore reassess risk models, factor in potential latency penalties from migration, and consider contractual safeguards that address force‑majeure events of this nature.