AWS Bahrain Cloud Disrupted After Drone Activity

Amazon Web Services' Bahrain cloud region, me-south-1, became a conflict-exposed infrastructure signal after Amazon confirmed a disruption during Middle East drone activity and later described the region as damaged and unavailable. The operating surface is not only AWS facility repair; it is whether customers can move data, identity, traffic and backups out of a single regional dependency.

Amazon Web Services operates its Middle East (Bahrain) Region under region code me-south-1. AWS documentation lists three Availability Zones and notes that customers must explicitly enable the Region. AWS launched it on July 29, 2019, as the company's first Middle East Region.

On March 24, 2026, Amazon said the AWS Bahrain Region had been disrupted as a result of the ongoing conflict in the Middle East. The company said it was working with local authorities, prioritizing personnel safety and helping affected customers migrate to alternate AWS Regions.

Reuters reported that Amazon attributed the disruption to drone activity in the area but did not say whether the Bahrain facility had been struck directly or affected by nearby strikes. AP and Data Center Dynamics separately reported earlier physical damage to AWS facilities in the UAE and Bahrain, including a Bahrain site damaged after a drone landed nearby.

On April 30, 2026, Reuters reported that Amazon said the Bahrain Region had sustained conflict-related damage and was unavailable. Public AWS status information through late May continued to advise customers to replicate critical workloads and Amazon S3 data from ME-SOUTH-1 to another AWS Region. Developing Telecoms reported on May 4 that AWS expected restoration of affected cloud-region services in the UAE and Bahrain to take several months.

For customers whose production systems, backups, logs or traffic controls were concentrated in Bahrain, the event turned physical-security exposure into a cloud-recovery problem. Remote backups, cross-region replication, DNS and traffic failover, identity continuity and tested restoration outside ME-SOUTH-1 became the key operational decisions.