https://x.com/FGhoddoussi/status/2028293351431446895?s=20
Translated from Persian
First Cloud Infrastructure Casualty of War
Shanika Anselm-Perera
An Amazon (AWS) data center in the United Arab Emirates was targeted.
AWS confirmed that at approximately 4:30 a.m. PST on March 1, "objects" struck the company's facilities in the Availability Zone coded mec1-az2, causing sparks and a fire.
UAE firefighters cut power to the building, and the zone went offline.
Amazon (AWS) says other zones remain operational, and recovery will take several hours.
Read that sentence again: "Objects collided."
The most valuable corporate infrastructure on Earth is now absorbing physical (kinetic) damage from a state-level military conflict, and the world's largest cloud provider describes missile or drone remnants as "objects"—because there is no corporate communications playbook for such a scenario.
This is the first time in history that a major "hyperscaler" data center has been physically struck during a war.
Every cloud architecture slide in every conference room worldwide assumes physical security means perimeter fences and biometric locks. Not ballistic missile defense. Not drone interception capability. Not wartime fire suppression, especially when the adjacent building is absorbing munitions.
The *Jerusalem Post* reported that the Israeli military had been using these facilities.
If confirmed, Iran's targeting of dual-use cloud infrastructure turns every data center in the conflict's geographic vicinity from a civilian asset into a military target.
The distinction between cloud infrastructure and defense infrastructure has effectively vanished.
And geography matters intensely. AWS chose the UAE for its Middle East region precisely because Dubai and Abu Dhabi offered stability, connectivity, and proximity to enterprise customers across the Gulf [Persian]. That assumption evaporated Saturday morning—when Iranian drones struck the Burj Al Arab and Jebel Ali Port, setting ablaze a data center that was simultaneously running government workloads, banks, and military operations.
The concentration risk is staggering. AWS, Microsoft Azure, and Google Cloud have all concentrated their Middle East regions in the same geographic corridor that has now become an active war zone.
Oracle also has infrastructure in Dubai. Every organization running production workloads in these regions is now gaming out "disaster recovery" scenarios that were classified as "theoretical" just 72 hours ago.
The insurance implications alone will redesign cloud pricing for a decade.
Lloyd's of London was already revising war risk exclusions in the wake of the Ukraine war. Now a drone has inflicted physical damage on a $2 trillion corporate data center in a country that markets itself as the region's safest business hub.
AWS built multi-region redundancy for earthquakes, power outages, and network disruptions—not for Iranian retaliation against a joint U.S.-Israeli military campaign. The system architecture held because one zone went down while the others stayed up, but this presupposition failed: that geographic choice for cloud regions is a business decision, not a wartime calculation.
"Cybersecurity expert Lucas Oljinic" immediately called out this euphemistic, minimizing language. AWS didn't say "it was bombed." AWS said "objects collided." This linguistic gap is the whole story. The world's cloud infrastructure has just entered the battlefield, and this industry still lacks the vocabulary for it.
That vocabulary will make itself felt in prices by Monday.
x.com/i/status/20282
Link to this post in the Telegram channel "Between Dichotomies":Rate this translation:
