Amazon(US:AMZN) Xi Niu Cai Jing·2025-08-11 07:56Core Points - Amazon Web Services (AWS) faced significant backlash after deleting the account and all data of a senior open-source developer without warning, leading to accusations of "digital destruction" [2][3] - The developer, Abdelkader Boudih (known as Seuros), reported that AWS requested identity verification, which he completed, but his account was still deleted due to alleged issues with a third-party payment provider [2] - AWS attributed the account deletion to problems with a third-party payment person, who had been covering monthly testing fees, but Seuros argues that this was not the real issue [3] Summary by Sections Account Deletion Incident - AWS deleted Seuros' account on July 23 after rejecting his identity verification documents, despite him providing valid identification and billing information [2] - The account contained critical data, including over 20 Rubygem project codes, teaching materials, unpublished manuscripts, and other important resources [2] AWS's Justification - AWS claimed the deletion was due to issues with a third-party payment provider, who had been responsible for payments but became unreachable after the FTX collapse [2] - AWS refused to revert to Seuros' original credit card, citing "privacy compliance," and placed the responsibility for the account termination on the user [2] Internal Insights and Developer Response - Seuros speculated that the real reason for the account deletion was an internal error during a verification process involving "inactive" accounts, which mistakenly led to the deletion of an active account [3] - An AWS insider suggested that the deletion was a result of a mistake made by AWS administrators during a verification process [3] - In response to the data loss, Seuros is developing a free AWS migration and data cleaning tool to assist developers and small teams in transferring their data to other cloud platforms [3] - Seuros manages clients with over $400,000 in monthly AWS spending, and several clients have agreed to migrate following the incident [3]