AWS drone strikes: why backups belong in another region
Drone strikes took out two of the three zones in AWS's UAE region in March, and AWS told customers to back up and move. One region was not enough.
Published · 3 min read

On Sunday 1 March 2026, a day after the United States and Israel launched strikes on Iran, objects struck one of Amazon Web Services' data centres in the United Arab Emirates, and power problems soon spread to a second of the three availability zones in its UAE region. On 2 March AWS said drones were to blame: two UAE facilities had been directly struck, and a strike close to a facility in Bahrain had damaged its infrastructure. AWS told customers in the region to back up their data and consider moving their workloads to other AWS regions, advice that came down, then and for months afterwards, to having a copy somewhere else. Spreading a system across one region's zones, the usual way to stay up, had not been enough.
With two of the three zones impaired, customers of S3, AWS's storage service, saw high failure rates moving data in and out, because S3 is designed to withstand the loss of one zone in a region, not two, The Register reported. Snowflake blamed disruption to its own service in the region on the outage. By 2 May, according to heise, AWS's status page said its UAE infrastructure could not reliably support customer applications and that restoration would take several more months. AWS urged customers to move what they could to other regions and restore the rest from remote backups, and it had suspended billing in the region.
Zones protect against a building, not a region
A cloud region is a group of data centres divided into availability zones, and spreading a system across the zones protects it when one building fails. It does nothing when the whole region is affected, whether by war, as here, or by a flood, a grid failure or a fault in the provider's own systems. The same holds one level up. A backup kept with the same provider, in the same account, shares that account's fate if it is suspended, locked or emptied by mistake.
What it means for the systems I build
The systems I build run in the client's own accounts and hosting, so the client holds the keys, and the decision about where the copies live belongs to them too. AWS is part of the stack I work with, and the question is the same whoever the provider is. For any system I would want three answers in writing: the region it runs in, where its backups go, and how long a restore somewhere else takes, measured on a real restore rather than estimated. It is the same habit as taking a go-live date from a rehearsal rather than from a calendar.
Five checks for where your copies live
- Find out which region each of your systems runs in, and which region holds its backups. If the answer is the same for both, that was probably never decided.
- Keep at least one backup in a different region, or with a different provider, under credentials the main system does not hold, so one compromised or suspended account cannot remove every copy.
- Restore from that copy, somewhere else, and time it. Until you have, you do not know whether it works, or how long you would be down.
- Agree in advance who decides to move, and at what point. AWS was telling customers to consider moving within the first two days of this outage.
- If a supplier runs a system for you, ask for these answers in writing, with the date of the last restore test.
If nobody in your office can say where the backups are kept, the fit check is a sensible first step.
Sources
- The Register, AWS says drones hit two of its datacenters in UAE, urges users to move resources to different regions, 2 March 2026
- The Star (Reuters), Amazon's cloud unit says drone strikes damaged UAE and Bahrain facilities, 3 March 2026
- heise online, After drone attack: AWS warns Middle East customers of long downtime, 2 May 2026
Enrique Lacambra III builds internal business systems from Cainta, Rizal.
Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.
