A failure occurred in the US following Amazon in the cloud service of Amazon, and customer data completely lost
by
In Japan, August 23, 2019 (Friday), Amazon's cloud service `` Amazon Web Service (AWS) '' caused a large-scale failure , and many services and websites were affected . Following this, it was found that a similar failure occurred in the United States on August 31 (Saturday), resulting in a loss of customer data.
AWS celebrates Labor Day weekend by roasting customer data in US-East-1 BBQ • The Register
https://www.theregister.co.uk/2019/09/04/aws_power_outage_data_loss/
On August 23, 2019 of AWS Tokyo Region for the failure that occurred in the Amazon is, that it is 'due to a management system failure of the air-conditioning equipment' announcement . After the failure, it was reported that the cooling system, which should have been redundant, did not operate normally due to a bug, and it was found that the room temperature rose in some parts of the data center, causing a server outage. It is.
Following this, on August 31st, a failure occurred in AWS's US East (N. Virginia) region. There was damage that part of the data of the Amazon Elastic Block Store (EBS) cloud storage used by AWS was lost.
Andy Hunt, a programmer who used AWS, tweeted on September 4th on Twitter “I found out that the EBS server was down due to a power failure in AWS”. Mr. Hunt stated that all the data stored in EBS was lost.
Amazon AWS had a power failure, their backup generators failed, which killed their EBS serversl, which took all of our data with it.Then it took them four days to figure this out and tell us about it.
— Andy Hunt (@PragmaticAndy) September 3, 2019
Reminder: The cloud is just a computer in Reston with a bad power supply.
According to an interview with the technical news media The Register , the failure was triggered by a power outage at the data center in the eastern US region at 4:33 am (Pacific Standard Time) on August 31. The backup generator was activated at the same time as the power failure, but the generator broke down in about 1 hour 30 minutes. Through the subsequent recovery work, 99.5% of the system recovered at 12:30, but the rest was considered unrecoverable and the recovery was abandoned, and the data stored in EBS was lost .
Mr. Hunt got nothing because he was backing up data, but accused 'the Amazon support after the failure was extremely insufficient'. “The frankly, this is the most serious problem,” says Amazon ’s explanation of the failure that occurred on August 31st after 4 days.
And that frankly is the part that annoyed me the most.We got days worth of “we don't know what's wrong, our engineers are looking into it.” Https://t.co/yYMh2hnaWw
— Andy Hunt (@PragmaticAndy) September 4, 2019
Hunt stressed the lesson that the cloud should not be overtrusted, saying, “The true identity of the cloud is just Reston 's underpowered PC, where Amazon's data center is located.”
Related Posts:
in Posted by log1l_ks