AWS Has No Timeline for Bahrain. That Is the Statement.

The AWS Health Dashboard currently reads: the Middle East (Bahrain) Region has suffered damage due to the conflict in the Middle East and is currently unavailable. Not degraded. Not impaired. Unavailable.

That message has been live, in some form, since March.

Iran's Islamic Revolutionary Guard Corps said it fired several cruise missiles at Amazon data infrastructure in Bahrain on July 21, 2026, during Wave 24 of Operation Nasr 2. The IRGC's statement on July 24 claimed its forces destroyed an Amazon data center in Bahrain. AWS has not confirmed or denied any of it.

The consensus says: this is a wartime disruption, cloud providers are resilient, customers with proper failover are fine. The consensus is not looking at the dashboard.

What Actually Happened to me-south-1

At approximately 04:30 UTC on March 1, Iranian drone strikes hit three Amazon Web Services data center facilities — two directly in the UAE and a third in Bahrain — in what Uptime Institute confirmed as the first verified military attack on hyperscale cloud infrastructure in history. Those strikes caused structural damage, disrupted power delivery, and in some cases required fire suppression activities that resulted in water damage.

An Iranian drone struck an Amazon data center in Bahrain again on April 1. Then the July 21 cruise missile claim. Then another on July 24. AWS has yet to confirm whether its site was targeted, and no updates have been added to its status page regarding the Bahrain region, which has been severely disrupted for months.

As of late April 2026, thirty-one AWS services in the two regions remained listed as disrupted. Billing operations in the region are currently suspended while AWS restores normal operations, a process expected to take several months.

Translation of AWS's April status update — "we continue to make progress on recovery efforts across multiple workstreams" — means: we cannot tell you when Bahrain is coming back.

AWS's own status language put it plainly: "the ongoing conflict in the region means that the broader operating environment in the Middle East remains unpredictable," and the company recommended customers with Middle East workloads consider migrating to alternate regions.

That is not SLA language. That is evacuation language.

The Silence Is the Tell

If the facility is physically destroyed, saying so is a geopolitical statement about Iranian military effectiveness. If it is coming back, they need a date — and they have none. If customers need to leave permanently, admitting that creates liability for every SLA written against me-south-1.

AWS-hosted providers including Snowflake and Red Hat subsequently urged affected customers to fail over or move workloads to other regions. AWS waived all usage-related charges for March 2026 in its me-central-1 region in the UAE following the attacks. A hyperscaler waiving billing is an admission that the product is not there.

The threat environment is not improving. On March 31, the IRGC formally declared eighteen U.S. technology companies "legitimate military targets" — Amazon, Microsoft, Google, Apple, Meta, HP, Tesla, Oracle, Boeing, Cisco, and IBM among them. The IRGC declared that "for every assassination and terrorist act in Iran, one facility or unit belonging to these companies will face destruction."

This is a doctrine, not a one-time strike.

What You Owe Your Own System

If you have workloads in me-south-1 and built your RTO around multi-AZ inside that region, you built resilience against hardware failure, not against a coordinated military targeting campaign that has executed across four strike waves since March.

The Middle East region opened in Bahrain in July 2019 as Amazon's first cloud region in the Middle East. There is no geographically proximate AWS fallback for GCC compliance requirements. The recommendation to migrate to "the United States, Europe, or Asia Pacific" is not a DR option for a Bahraini bank or Gulf energy operator with data residency obligations.

The IRGC has claimed strikes in March, April, and twice in July. AWS has issued no public statement on kinetic damage at any point. If the facility were operational, the company would have said so. The five-month silence is the most honest communication AWS has made.

If me-south-1 is still down in Q4, AWS has effectively ceded the Middle East market. Google Cloud (UAE) and regional sovereign cloud vendors become the only credible alternatives for operators who cannot tolerate a war zone as their primary region.

What to watch: (1) Any AWS official statement naming a rebuild timeline — absence past 60 days from the July strikes is de facto abandonment. (2) Customer announcements of me-south-1 data migration from GCC financial institutions and energy operators. (3) Whether the IRGC names a third or fourth strike on the same site, confirming persistent targeting. (4) GCC government pressure for sovereign cloud infrastructure as a direct policy response to this incident.