AWS Bahrain data‑center hit
AWS operations in Bahrain and the UAE were disrupted after facilities tied to Amazon’s cloud were attacked, temporarily impairing services for regional banks, governments, and enterprises — a new reminder that data centers are explicit targets in geopolitical conflicts. The outage raises urgent resilience questions for multi‑region SaaS deployments and disaster playbooks. (thetechportal.com)
Batelco’s Hamala headquarters was struck on April 1, and Bahrain’s Interior Ministry said civil‑defence crews were “extinguishing a fire in a facility of a company” after the attack. (datacenterdynamics.com) The Financial Times reported an Amazon Web Services data centre in Bahrain sustained damage on April 1, a claim Reuters carried after citing a person familiar with the matter. (finance.yahoo.com) On March 1 AWS said two availability zones in its Middle East (UAE) region were “directly struck” by drones and that a nearby strike had caused damage to a Bahrain site, with fire suppression and power cuts producing water and connectivity damage. (cnbc.com) AWS publicly advised customers to migrate workloads out of affected Middle East regions after the March attacks, and the company’s Health Dashboard logged ongoing connectivity issues and API error rates for the Middle East (UAE) and Middle East (Bahrain) regions during early March. (datacenterdynamics.com) Amazon applied a billing waiver for the ME‑CENTRAL‑1 (UAE) region covering March 2026 usage, an action AWS said would be applied automatically to affected accounts. (networkworld.com) Analysts tracking the April 1 strikes noted Iran launched multiple drones and ballistic missiles toward Bahrain that day; the Institute for the Study of War reported Iran launched 19 drones and four ballistic missiles at Bahrain on April 1, with at least one strike hitting a company building. (understandingwar.org)
