Re:I Followed the Official AWS Amplify Guide and Was Charged...
by bryancoxwell on Thursday November 14, 2024 @07:23AM
(#42135536)
Well done AWS for finding a way to make your technical debt cost other people money.
[dead]
Re:I Followed the Official AWS Amplify Guide and Was Charged...
by vitiral on Thursday November 14, 2024 @07:35AM
(#42135607)
... only governments, yet this is Amazon
Re:I Followed the Official AWS Amplify Guide and Was Charged...
by rmbyrro on Thursday November 14, 2024 @07:52AM
(#42135731)
If it wasn't clear, my point is: Amazon is so big and dominant at this point that it's got government-like powers.
Re:I Followed the Official AWS Amplify Guide and Was Charged...
by vitiral on Thursday November 14, 2024 @09:04PM
(#42143321)
It wasn't clear, thanks
Re:I Followed the Official AWS Amplify Guide and Was Charged...
by rolandog on Thursday November 14, 2024 @07:37AM
(#42135631)
Completely agree. Having worked previously for ... (humans?) ... I can authoritatively theorize it would be fixed in a jiffy if it weren't making them bucketloads of money.
To make my case: just ponder the opposite: "What would an honest version of AWS do?". They would address the concerns publicly, document their progress towards fixing the issue, and even try to determine who was overcharged due to their faulty code, and offer them some compensation.
"We're too big to fix our own code" is, sadly, taken from the MS playbook (IIRC, something like that was made public after the breach of MS manager mailboxes after the whole Azure breach fiasco that was discovered by, IIRC, the DOJ that paid to have access to logs).
Re:I Followed the Official AWS Amplify Guide and Was Charged...
by fallingsquirrel on Thursday November 14, 2024 @09:04AM
(#42136220)
And yet somehow every time they launch a new product they have no problem adding it to their billing code.
That's been one of the more interesting inside baseball facts I've learned here.