AWS Erases March from UAE Region Billing After Iranian Drone Strikes

AWS has taken the extraordinary step of waiving all charges and erasing billing data for its Middle East (Bahrain) region for the entire month of March 2026, following Iranian drone strikes that physically destroyed two of three availability zones on March 1st.

The email notification to customers was remarkably terse: "AWS is waiving all usage-related charges in the ME-CENTRAL-1 Region for March 2026. This waiver applies automatically to your account(s), and no action is required from you." There was no explanation of the Iranian drone strikes that took out critical infrastructure, no mention of the 109 services that went down, and no acknowledgment that customers spent weeks unable to terminate EC2 instances because the control plane was completely offline.

What makes this situation particularly unusual is that AWS isn't just waiving charges—they're deleting the billing data entirely. "You will not see any March 2026 usage for the ME-CENTRAL-1 Region in your Cost and Usage Report or Cost Explorer once processing is complete," the email stated.

The Billing Data Problem

For most organizations, the AWS bill serves as more than just an invoice—it's the canonical record of what infrastructure exists, where it's running, and how long it's been there. The Cost and Usage Report (CUR) is often the closest thing companies have to a single source of truth that accurately describes their cloud footprint.

Compliance teams rely on this data. Auditors request it. FinOps teams build their entire practice on it. When security teams want to know if resources were running in specific regions, they check the CUR. After March 31st, that answer will be a clean, empty month.

Why This Happened

The physical destruction of data center infrastructure by military action is something that falls outside normal disaster recovery planning. Availability zones are designed to handle hardware failures, power outages, fiber cuts, and cooling system issues—not state actors deciding a data center shouldn't exist anymore.

"Nobody's fault-tree analysis includes 'building hit by military drone,'" notes the analysis. "No disaster recovery runbook in the world has a section titled 'Regional Armed Conflict.'"

The Technical Reality

There are likely two reasons for the data deletion. First, the metering and billing infrastructure itself went offline when the physical hardware was destroyed. When servers lose power or physical cohesion, you can't generate usage reports for resources that were running on them.

Second, there's a pragmatic operational consideration. Customers couldn't terminate resources through the AWS console because termination commands require acknowledgement. EC2 instances were stuck in stopped states for weeks. Elastic IPs were trapped on dead hardware. Processing normal billing with thousands of support tickets for each failed resource would have created an operational nightmare.

The Precedent

The waiver itself is the correct outcome—customers shouldn't pay for resources they couldn't control in a region that was physically destroyed. But the mechanism now exists: AWS can zero out an entire month of usage data across a region, and the result is indistinguishable from that month never happening.

"The bill, the one canonical source of truth, simply won't show it," the analysis warns. "Today the reason is a war, and it's a good reason. But precedents don't come with permanent context attached."

The question now becomes: what happens the next time a month of data goes missing? Will there be an explanation? Will there be a reason you'd accept? After March 31st, the data won't be saying anything either way.

This situation highlights the complex relationship between cloud infrastructure reliability, physical security, and the financial records that organizations depend upon for compliance, auditing, and operational management.