AWS Bahrain Outage
Drone strikes tied to the US–Iran regional conflict knocked the AWS Bahrain region offline and forced customers to shift workloads to other regions—exposing geopolitical risk in cloud resilience. The outage tested Amazon’s incident response and underlines the need for multi-region failover and DR playbooks. (cnbc.com)
Amazon posted a March 24, 2026 update saying the AWS Middle East (Bahrain) region has been “disrupted,” that the company is working closely with local authorities and prioritizing personnel safety, and that a large number of customers have already been moved to other Regions. (aboutamazon.com) Amazon confirmed on March 3, 2026 that two AWS facilities in the United Arab Emirates were directly struck by drones and that a separate facility in Bahrain sustained damage from a nearby strike during the first wave of attacks. (bloomberg.com) Bloomberg reported that, after the March 1–3 strikes, two of the three regional data‑center hubs in the affected UAE region remained “significantly impaired” and that AWS warned recovery could be prolonged. (bloomberg.com) Industry trackers counted widespread service impact beginning March 1, 2026, with at least 109 AWS services reportedly knocked out or degraded in the UAE region and analysts saying the attacks disabled two availability zones there while Bahrain’s region lost at least one AZ. (cybersecuritynews.com) Financial institutions publicly affected included Abu Dhabi Commercial Bank and several UAE lenders that reported temporary outages to mobile and internet banking during the early‑March disruption. (gulfnews.com) Trade outlets noted elevated error rates on AWS’s status dashboard during the incidents and quoted AWS urging customers to migrate workloads to alternate Regions while recovery continues. (crn.com)
