Skip to content

SYSTEM Cited by 1 source

Amazon me-south-1 (Bahrain)

Amazon me-south-1 is Amazon Web Services' Bahrain cloud region, launched 2019-07-29. It was AWS's first Middle-East region, preceding me-central-1 (UAE) by three years and serving as the initial cloud landing zone for Gulf-region workloads.

As of Q1 2026, me-south-1 was hit twice by kinetic events tied to the ongoing regional conflict — first as collateral damage to a strike on an adjacent facility on March 1-2, 2026, then by additional drone activity on March 23, 2026.

Facility profile

  • Region code: me-south-1
  • Country: Bahrain
  • Parent region family: me- (Middle East)
  • Sibling region: systems/amazon-me-central-1 (UAE)
  • Launched: 2019-07-29 (first AWS Middle-East region)

2026-03-01/02 incident — collateral damage

During the confirmed drone strikes that hit me-central-1 on March 1-2 2026, Amazon also confirmed that a me-south-1 facility in Bahrain was "taken offline after being damaged by a nearby strike."

The damage pattern was different from the UAE strikes (which were direct hits); the Bahrain facility was affected by proximate explosive or concussion damage from a nearby strike rather than direct impact.

Impact per AWS Health Dashboard: the same category of "structural damage, disrupted power delivery... fire suppression activities that resulted in additional water damage" as the me-central-1 facilities.

Third-party observability from Cloudflare Cloud Observatory:

2026-03-23 incident — second me-south-1 disruption

An additional disruption hit me-south-1 on March 23, 2026 following further drone activity — the third separately disclosed kinetic or near-kinetic impact event on AWS Middle-East facilities in three weeks.

Unlike the March 1-2 event (confirmed strikes on the facility adjacent to me-south-1), the March 23 event was attributed by AWS to "further drone activity" without specific structural damage framing published. Disruption was publicly reported ("AWS says AWS Bahrain region disrupted following drone activity").

Why the incident matters

me-south-1's two-event exposure makes it a stronger signal than me-central-1 alone: the Middle-East conflict produces recurring kinetic risk, not a one-shot threat. The implications for architecture:

  • Single-event tolerance is not enough. A customer workload that survived March 1-2 via backup still had to handle March 23 two weeks later.
  • Conflict-era regions should be treated as degraded-default for the duration of the conflict. Pre-position workloads out of conflict regions at the start of conflict, not after the second event.
  • Both me-central-1 and me-south-1 share a conflict geography. Failing over from me-central-1 to me-south-1 is not meaningful geopolitical diversity.

See concepts/kinetic-attack-on-cloud-infrastructure for the full threat model and patterns/cloud-region-migration-during-conflict for the operational pattern.

Seen in

  • sources/2026-04-28-cloudflare-q1-2026-internet-disruption-summary — canonical wiki instance. me-south-1 was affected on March 1-2 2026 (collateral damage to a facility adjacent to a struck me-central-1 facility) and again on March 23 2026 (further drone activity). Cloudflare Cloud Observatory showed elevated connection failure rates through the incident windows.
Last updated · 433 distilled / 1,256 read