Why were AWS zones in Bahrain and Dubai hard down?

Iranian strikes knock out AWS zones in Bahrain and Dubai

An internal memo and related reporting indicate that Iranian strikes affected key Amazon Web Services infrastructure in the Middle East. Two AWS availability zones—one in Bahrain and another in Dubai—were described as “hard down,” with Amazon expecting them to be unavailable for an extended period.

The immediate impact of the outage is that portions of those regions can be effectively offline, reducing cloud capacity for customers whose workloads depend on services located in the impacted zones. Because availability zones are designed to provide redundancy inside a region, losing multiple zones can be especially disruptive for applications that rely on multi-AZ deployments or specific zone-level routing.

This matters beyond local downtime because it underscores how geopolitical events can quickly propagate into global technology operations. Even if data and services are “cloud-based,” they still depend on physical infrastructure, network connectivity, and regional power and security conditions.

Key operational implications include:

• Reduced availability for hosted workloads using affected zones
• Potential migration or failover pressure on remaining zones and regions
• Business continuity concerns for enterprises with strict uptime requirements

The reporting also emphasizes that the unavailability is expected to last beyond the initial incident window, which increases the likelihood that customers will need to take longer-term mitigation steps rather than expecting fast restoration.

Overall, the event is another example of how cloud reliability can be shaped by factors outside a provider’s control—making disaster planning and multi-region architectures even more important for risk management.