Keep in mind, just 2 days ago, AWS has provided the following statement to Tom's Hardware: https://www.tomshardware.com/software/cloud-storage/aws-accused-of-a

Keep in mind, just 2 days ago, AWS has provided the following statement to Tom's Hardware: https://www.tomshardware.com/software/cloud-storage/aws-accused-of-a-digital-execution-after-it-deleted-10-years-of-users-data-without-warning-software-engineer-details-complete-digital-annihilation-at-the-hands-of-aws-admins-claims-false-excuses-given-for-account-deletion https://www.tomshardware.com/software/cloud-storage/aws-accu... https://archive.is/0b3Hc https://archive.is/0b3Hc > Update: August 5 7:30am (ET): In a statement, an AWS spokesperson told Tom's Hardware "We always strive to work with customers to resolve account issues and provided an advance warning of the potential account suspension. The account was suspended as part of AWS’s standard security protocols for accounts that fail the required verification, and it is incorrect to claim this was because of a system error or accident." This shows a bigger part of this problem. When these mistakes do happen, they're invariably treated as standard operating procedures. They're NEVER treated as errors. It would appear that the entire support personnel chain and PR literally have no escalation path to treat any of these things as errors. Instead, they simply double-down that it's NOT an error that the accounts was terminated on an insufficient notice over bogus claims and broken policies.