Amazon AWS S3 Goes Down, Takes Down Services, Websites, Apps With It

Um, is Webroot dependent on AWS S3 ?

@ wrote:
Um, is Webroot dependent on AWS S3 ?

I am not sure about that, something does ring a bell from quite a while ago though, maybe @ can find out for certain.

Webroot does use AWS according to this article but there is no reference to AWS S3.
 
"Webroot does the machine learning on the Amazon Web Services (AWS) cloud platform rather than requiring customers to have a load of spare servers to support the system."
 
 

WebrootSA holds amazonaws IP connections and yesterday my search annotations were flaky++.
 
Maybe, BrightCloud employs AWS. 
 
 

An update on the issue from Amazon on the subject, it was caused by a typo.
 
We’d like to give you some additional information about the service disruption that occurred in the Northern Virginia (US-EAST-1) Region on the morning of February 28th. The Amazon Simple Storage Service (S3) team was debugging an issue causing the S3 billing system to progress more slowly than expected. At 9:37AM PST, an authorized S3 team member using an established playbook executed a command which was intended to remove a small number of servers for one of the S3 subsystems that is used by the S3 billing process. Unfortunately, one of the inputs to the command was entered incorrectly and a larger set of servers was removed than intended. The servers that were inadvertently removed supported two other S3 subsystems.  One of these subsystems, the index subsystem, manages the metadata and location information of all S3 objects in the region. This subsystem is necessary to serve all GET, LIST, PUT, and DELETE requests. The second subsystem, the placement subsystem, manages allocation of new storage and requires the index subsystem to be functioning properly to correctly operate. The placement subsystem is used during PUT requests to allocate storage for new objects. Removing a significant portion of the capacity caused each of these systems to require a full restart. While these subsystems were being restarted, S3 was unable to service requests. Other AWS services in the US-EAST-1 Region that rely on S3 for storage, including the S3 console, Amazon Elastic Compute Cloud (EC2) new instance launches, Amazon Elastic Block Store (EBS) volumes (when data was needed from a S3 snapshot), and AWS Lambda were also impacted while the S3 APIs were unavailable.  
 
Full Article

Oops! :I wonder how forgiving Bezos is?:@
 

 

 

Okay this is Official from Webroot!
 
"Hi Daniel,
 
Webroot utilizes multiple AWS regions as well as multiple availability zones in each region. The Virginia S3 incident had no impact on the level of protection WSA offers and no data loss occurred.
 
Please let me know if you have any questions.
 
Thanks
Amelia"
 
Awesome! 😉