{
  "type": "article",
  "title": "Iranian strikes permanently erase some Amazon Web Services customer data",
  "summary": "Amazon Web Services said in a September 15 dashboard update that Iranian strikes caused permanent customer data loss in part of its cloud infrastructure. Data in the mec1-az2 zone of the United Arab Emirates is irretrievable, and access has not been restored across all three zones in Bahrain.",
  "content": "Amazon Web Services has said that some customer data and cloud resources in war-damaged data centers cannot be recovered. In a dashboard update posted September 15, the company said customers could not regain access to resources and data in parts of its infrastructure, indicating the severe damage caused by Iranian strikes in the affected regions.\n\nRecovery prospects differ across the two regions\nThe clearest permanent loss is in mec1-az2, one of the United Arab Emirates region’s three availability zones. The customer information stored there can no longer be retrieved. An availability zone draws on at least one Amazon data center and may draw on several.\n\nWork is also continuing in the other two UAE zones, where AWS is trying to bring hosted services back. The update said teams are replacing damaged infrastructure and would give customers more information about service restoration in the coming months. In other words, two zones remain in the recovery process, while the data in mec1-az2 is gone for good.\n\nBahrain has a wider access failure\nThe damage in Bahrain was more widespread. Amazon said customers still could not reach resources or data in any of the region’s three availability zones. AWS explained, “The damage to our infrastructure spanned multiple availability zones and exceeded what our regional and multi-AZ services are designed to withstand.”\n\nThat means the destruction went beyond the failure limits built into regional and multi-zone cloud services. The update did not point to one isolated equipment problem; it connected the outage and loss to the physical damage from the strikes.\n\nThree rounds of attacks created the damage\nIranian drones hit Amazon data centers for the first time on March 1, as the war was beginning. The conflict opened with US-Israeli attacks on Iran on February 28. AWS promptly advised migration to other cloud regions and the use of off-site backups for inaccessible resources.\n\nIran struck Amazon data centers in Bahrain again on April 1. The update said April brought a disruption to a second availability zone in Bahrain. By then, most affected customers had acted on AWS guidance and moved their cloud computing workloads to other locations.\n\nOn July 24, missiles fired by Iran’s Islamic Revolutionary Guard Corps hit a remaining Amazon data center structure in Bahrain. Satellite imagery independently confirmed the damage. AWS said its long-term support for Bahrain customers will continue, with another update scheduled for early 2027.\n\nRecovery work continues alongside billing relief\nCustomer billing had already been suspended in the affected AWS regions covering Bahrain and the United Arab Emirates. For the past six months, the company has been working to bring operations back to normal. Replacing damaged infrastructure is part of that effort, with more restoration information for the UAE expected in the coming months.\n\nAfter the first Iranian strikes in March, AWS provided $150 million in credits to customers. The earlier advice to move resources and use off-site backups gave customers a route to restore workloads with copies elsewhere, but it could not recover data that existed only inside the damaged infrastructure.\n\nFor Bahrain, the next company update is planned for early 2027. The update did not give a restoration date for the three affected zones there.\n\nRegional conflict is feeding an energy crisis\nThe conflict that began with US-Israeli attacks on Iran has since widened into a broader regional confrontation. Attacks have hit shipping in the Strait of Hormuz. The Bab al-Mandeb Strait has seen similar attacks, and together they are driving a worsening global energy crisis. A rare encouraging side effect has been rapidly growing global interest in renewable electricity, such as rooftop solar panels.\n\nWhat this means for you\nFor affected cloud customers, the biggest practical consequence is uncertainty over recovery: some resources remain in the restoration process, but data in one UAE zone cannot be recovered.\n\n• UAE and Bahrain: Data in mec1-az2 is irretrievable, and access remains unavailable in all three Bahrain availability zones. Customers should map affected workloads and check remote backups for usable copies.\n• Migration: AWS advised moving resources to other cloud regions and using off-site backups for inaccessible resources. Workloads with copies elsewhere can be restored; data kept only in damaged infrastructure cannot.\n• Billing and credits: Customer billing was suspended in the affected Bahrain and UAE regions. AWS also issued $150 million in customer credits after the March strikes, so customers should review their account records.\n• Next updates: AWS promised more restoration information in the coming months and another Bahrain update in early 2027. Until then, customers should keep records of lost resources and migration activity.\n\nWhy this happened\nThe direct cause was physical damage from Iranian attacks on Amazon data centers, not a routine software failure. AWS said the damage crossed multiple availability zones and exceeded the tolerance built into regional and multi-zone services. No separate technical cause was identified.\n\n• First strike: Iranian drones hit Amazon data centers on March 1, during the opening days of the war. The conflict began with US-Israeli attacks on Iran on February 28, and AWS promptly advised migration and off-site backups.\n• Later strikes: A follow-up hit Bahrain on April 1 and disrupted a second availability zone; most affected customers had already moved workloads elsewhere. On July 24, Iran’s Islamic Revolutionary Guard Corps used missiles against a remaining Bahrain structure, with satellite imagery confirming the damage.\n• Why redundancy failed: AWS said the damage spread beyond the limits of regional and multi-AZ services. That explains the permanent loss in mec1-az2 and the wider access failure across Bahrain’s three zones.\n• Recovery limits: Amazon has worked for six months to restore normal operations and replace affected infrastructure. Billing was suspended in affected Bahrain and UAE regions; UAE information is expected in the coming months and Bahrain’s next update is planned for early 2027.\n\nQuestions & Answers\n\n1. Where was customer data lost?\nCustomer data in the mec1-az2 availability zone of the United Arab Emirates is irretrievable. Access has not been restored across all three availability zones in Bahrain.\n\n2. When did Amazon Web Services provide the update?\nThe update was posted September 15. It described the loss, the restoration work, and the company’s next steps.\n\n3. How many availability zones were in the United Arab Emirates region?\nThere were three availability zones in the United Arab Emirates region. Data in mec1-az2 is permanently lost, while work continues in the other two.\n\n4. How extensive is the problem in Bahrain?\nCustomers still cannot reach resources or data in any of Bahrain’s three availability zones. AWS said the damage exceeded the tolerance built into regional and multi-zone services.\n\n5. What were customers advised to do?\nAWS told customers to shift workloads to different cloud regions and use off-site backups when resources were inaccessible. It issued $150 million in customer credits after the initial March strikes.\n\n6. On which dates did the Iranian attacks occur?\nThe first drone attack was on March 1, the Bahrain follow-up was on April 1, and the missile strike was on July 24. Iran’s Islamic Revolutionary Guard Corps carried out the July 24 attack.\n\n7. Was customer billing still running?\nCustomer billing was suspended in the affected AWS regions in Bahrain and the United Arab Emirates. Amazon has worked for six months to bring operations back to normal.\n\n8. When is the next update?\nAWS promised more restoration information for the UAE in the coming months. It said the next Bahrain update will come in early 2027.\n\n9. How is the incident connected to the energy crisis?\nShipping in the Strait of Hormuz has been attacked. Similar attacks in the Bab al-Mandeb Strait have contributed to a global energy crisis, while interest in renewable power including rooftop solar panels has risen worldwide.",
  "url": "https://trendkia.com/en/business/iranian-hamalon-men-amazon-web-services-ka-kuchha-grahaka-deta-hamesha-ke-lie-kho-gaya-33085",
  "category": "Business",
  "publishedAt": "2026-09-18",
  "tags": [
    "Amazon Web Services",
    "Iranian strikes",
    "Bahrain data centers",
    "UAE cloud",
    "customer data loss",
    "cloud restoration"
  ],
  "language": "en",
  "site": "TrendKia"
}