Internal memo: Iranian strikes have rendered two AWS zones “hard down” in Dubai and Bahrain and Amazon expects them to be “unavailable for an extended period”
Amazon tells its employees to deprioritize these regions as the Iran war deals meaningful damage to its infrastructure in the Gulf.
Context & Ripple Effects
AWS’s Gulf disruption has escalated from its March warning that operations were becoming unpredictable after direct strikes near UAE and Bahrain facilities to a Bahrain-region disruption later that month. The reported hard-down zones make clear that the risk is no longer limited to intermittent operating constraints.
The immediate damage report followed evidence that an Iranian strike had damaged AWS’s Bahrain operation. An internal instruction to deprioritize the affected regions signals that Amazon is allocating operational attention around a prolonged restoration rather than treating this as a short-lived incident.
First-order effects
- AWS customers whose applications depend on the affected Dubai and Bahrain availability zones face reduced local capacity and service-continuity pressure while the zones remain unavailable.
- Amazon must shift regional operations toward incident response and restoration, with employees directed away from lower-priority work in the affected locations.
Second-order effects
- Customers with workloads designed across other locations may accelerate failover or migration planning; those without that flexibility face sharper pressure to redesign their deployment choices.
- Rival cloud providers and regional infrastructure operators gain an opening to compete for workloads that need alternatives to disrupted AWS capacity, while existing AWS customers may reassess the value of geographic redundancy.
Third-order effects
- If attacks on cloud facilities persist, physical-location exposure becomes a more prominent constraint on cloud reliability, alongside the software and network safeguards customers typically rely on.
- The episode could push large cloud buyers to treat geopolitical resilience and recoverability as procurement criteria, potentially favoring multi-location or multi-provider architectures where the added cost is justified.
The trend: This is part of a broader shift in which cloud and AI infrastructure is being evaluated not just for scale and performance, but for its exposure to physical and geopolitical disruption.