Skip to content

AWS mistakenly erases 10 years of an engineer's data, stirring speculation of a lurking plot

AWS allegedly erased a decade's worth of data, according to a detailed post by software engineer Abdelkader Boudih on their Seuros blog. Boudih's assertion suggests a possible conspiracy, raising questions about the incident.

"AWS erases a decade of an engineer's data, raising suspicions of a hidden agenda"
"AWS erases a decade of an engineer's data, raising suspicions of a hidden agenda"

AWS mistakenly erases 10 years of an engineer's data, stirring speculation of a lurking plot

In a shocking turn of events, software engineer Abdelkader Boudih, also known as Seuros, has lost 10 years' worth of data stored on Amazon Web Services (AWS). This incident serves as a cautionary example of the vulnerabilities that cloud storage services, including AWS, may pose to users.

The loss of data can lead to significant financial damage, downtime, and reputational harm. In Boudih's case, his clients, representing over $400k/month in AWS billing, have agreed to migrate to Oracle OCI, Azure, and Google Cloud.

Common risks associated with using cloud storage services like AWS include data loss, data breaches, misconfigurations, insecure APIs, and loss of control over data security. These risks arise due to factors such as accidental deletions, security misconfigurations, insider threats, and vulnerabilities in cloud access interfaces.

One of the significant concerns is data loss, which can occur if backups are inadequate or recovery processes fail. Attack vectors include ransomware, insider errors, or cloud provider outages. Boudih's data loss was initiated by a simple verification request from AWS that expired before he could respond.

The case of Boudih underscores the importance of maintaining secondary backups outside of the cloud, as well as the need for better transparency and control mechanisms when using cloud providers like AWS. Despite AWS documentation stating a 90-day grace period between account closure and data deletion, Boudih's data was deleted before this period.

Another key risk is dependency on the cloud provider's security measures, leading to loss of direct control and potential exposure to hacking or insider threats. Boudih points to slow progress and ineffective feedback from AWS support as potential signs of a cover-up, although there is no concrete evidence to support this claim.

To mitigate these risks, best practices include automated and tested backups stored separately from the production environment, strict access control with multi-factor authentication, regular security audits, encryption of data in transit and at rest, and maintaining offline or alternative backups besides cloud storage.

Boudih is developing a free tool to help people get their data out of AWS, and he recommends external storage devices such as USB drives and external SSDs as secondary backups due to potential risks with cloud storage.

The data loss didn't just affect Boudih but also any developers who use the tools he had stored on AWS. For instance, a OneDrive user lost 30 years' worth of photos and work due to data loss. This incident highlights the need for users to be vigilant about their data security when relying on cloud storage services.

In sum, Abdelkader Boudih's case serves as a cautionary example of cloud storage vulnerabilities, emphasizing that users relying on AWS or similar services should implement robust, multi-layered data protection strategies to prevent loss and unauthorized access.

  1. Abdelkader Boudih, a software engineer known as Seuros, experienced a significant loss of 10 years' worth of data stored on Microsoft's Azure competitor, Amazon Web Services (AWS).
  2. Boudih's data loss was initiated by a simple verification request from AWS that expired before he could respond, serving as an example of the risks associated with using cloud storage services like Azure and AWS.
  3. One of the key risks of using cloud storage services like Azure and AWS is dependency on the cloud provider's security measures, potentially leading to loss of direct control and exposure to hacking or insider threats.
  4. To mitigate these risks, best practices include maintaining secondary backups outside of the cloud, such as on hardware like external SSDs and USB drives, as well as implementing automated and tested backups stored separately from the production environment.
  5. Additionally, strict access control with multi-factor authentication, regular security audits, encryption of data in transit and at rest, and maintaining offline or alternative backups besides cloud storage can help protect data from loss and unauthorized access.
  6. Boudih is developing a free tool to help people get their data out of AWS, and he recommends external storage devices like USB drives and SSDs as secondary backups due to potential risks with cloud storage.
  7. The data loss didn't just affect Boudih but also any developers who use the tools he had stored on AWS, such as a OneDrive user who lost 30 years' worth of photos and work due to data loss.
  8. In the case of Boudih, his clients, representing over $400k/month in AWS billing, have agreed to migrate to Oracle OCI, Azure, and Google Cloud following the data loss incident.
  9. This incident underscores the importance of adopting robust, multi-layered data protection strategies and being vigilant about data security when relying on cloud storage services like Azure and AWS.

Read also:

    Latest