Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

A 10-year AWS customer lost their entire account and all data without warning after a verification process failure. The author details a 20-day support nightmare where AWS MENA allegedly deleted the account due to an internal testing mistake involving Java command-line parameter parsing. The incident destroyed years of open-source development work, including Ruby gems and unpublished tutorials. The story highlights the risks of cloud provider dependency and the differences in AWS regional operations, particularly in the MENA region.

AWS deleted my 10-year account and all data without warning

DevOps Daily

duplicate of:
<a href="https://app.daily.dev/posts/aws-deleted-my-10-year-account-and-all-data-without-warning-ahiwhchra" target="_blank" rel="noopener nofollow">https://app.daily.dev/posts/aws-deleted-my-10-year-account-and-all-data-without-warning-ahiwhchra</a>

Nightmare. One conclusion that arises is this: Perhaps it’s worth abandoning the practice of writing software with the --dry-run flag? Instead, let’s write software that expects the --exec flag to be provided; otherwise, it always runs in --dry-un mode by default.
Although I realize that with properly written code such reversal of the logic of operation should not be necessary.
I think we all agree that the code run by AWS MENA support was poorly written. It continued to run despite receiving an unknown flag.

java has neither a -dry nor a --dry command line option. still sucks to loose everything ofcourse.