AWS Data Loss: War Damage in Ukraine Permanently Deletes Cloud Data

Key Takeaways

• Amazon Web Services (AWS) has confirmed permanent data loss for some customers in its Middle East data centers due to war damage.
• The affected regions include Bahrain (me-south-1) and one availability zone in the UAE (mec1-az2), following Iranian drone and missile strikes.
• This incident marks a significant event: the first acknowledged irreversible data loss at a major global cloud provider directly caused by military conflict.
• The damage overwhelmed AWS’s multi-availability zone redundancy, highlighting the critical importance of customer-managed off-site backups.

AWS Confirms Permanent Cloud Data Loss Following War Damage in Middle East

Amazon Web Services (AWS) has officially acknowledged the permanent loss of certain customer data residing in its Middle East data centers, impacted by recent military actions. This marks an unprecedented event, as it appears to be the first instance where armed conflict has led to irreversible data destruction within a major global cloud computing infrastructure.

Impacted Regions and Unrecoverable Data

Six months after a series of Iranian drone and missile strikes targeted critical infrastructure in the region, AWS has confirmed that information stored in specific facilities in Bahrain and the United Arab Emirates is irretrievably lost. An update on the AWS Health Dashboard, dated September 15, stated the cloud provider’s inability to “restore access to the resources and data” exclusively hosted in the compromised locations.

Initial reporting by Reuters indicated that the strikes caused catastrophic and unrecoverable damage to the underlying physical infrastructure. This recent communication represents AWS’s first public update on these incidents since April and provides the clearest admission to date regarding the permanent nature of some data losses.

Details of the Damage

In the UAE, the damage was primarily concentrated within one of the region’s three availability zones, specifically the mec1-az2 zone. Customer data housed solely within this zone is now permanently unrecoverable. Each availability zone is supported by one or more physical Amazon data centers. AWS has indicated ongoing efforts to restore regional resources and bring the other two affected zones, mec1-az1 and mec1-az3, back online.

According to the dashboard, projectiles struck the mec1-az2 data center around 4:30 AM PST, igniting fires and creating sparks that ultimately overwhelmed all recovery attempts.

The destruction was even more extensive in Bahrain, where AWS reported a complete inability to restore access to resources and data across the entire me-south-1 region.

“The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand,” the company stated. This admission is particularly significant because AWS’s architectural design typically incorporates redundancy to tolerate the failure of a single availability zone, but not simultaneous, coordinated attacks across multiple sites.

Background to the Attacks

The disruptions commenced in March following U.S. and Israeli military actions against Iran, which prompted retaliatory missile and drone strikes from Tehran on Gulf states hosting U.S. military assets. Two AWS facilities in the UAE sustained direct hits. Concurrently, a drone strike near a Bahrain facility caused physical damage to its infrastructure. The first Bahrain zone became inoperable in March, followed by a second in April, rendering the entire me-south-1 region unavailable.

What You Should Do

• Audit Cloud Asset Locations: Immediately review your cloud infrastructure to identify any assets, applications, or data that were exclusively hosted in the me-south-1 region (Bahrain) or the mec1-az2 availability zone (UAE).
• Verify Backup and Recovery Strategies: Ensure your organization has robust, geographically dispersed backup and disaster recovery plans in place that extend beyond a single cloud region or provider. Data stored solely within a single cloud footprint, without external copies, is vulnerable to such catastrophic events.
• Understand the Shared Responsibility Model: Reiterate the importance of the shared responsibility model. While cloud providers secure the cloud infrastructure itself, customers are responsible for the security and resilience of their data in the cloud, including implementing appropriate backup and recovery solutions.
• Stay Informed: Monitor official AWS Health Dashboard updates for any further information regarding these incidents, particularly for the promised updates on the UAE in the coming months and Bahrain in early 2027.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.