I Followed the Official AWS Amplify Guide and Was Charged $1,100
elliott-king.github.io
I Followed the Official AWS Amplify Guide and Was Charged $1,100
1–10 of 293 posts
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#2Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#3> It’s so difficult to be paranoid about every single technology you use.
I would be paranoid with anything related to AWS, I don't want to risk my bankruptcy (or near bankruptcy experience) on small mistakes or the goodwill of the AWS support.
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#4Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#5It is sad experience but I disagree with the author here > It’s so difficult to be paranoid about every single technology you use. I would be paranoid with anything related to AWS, I don't want to risk my bankruptcy (or near bankruptcy experience) on small mistakes or the goodwill of the AWS support.
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#6Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#7Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#8I do not know what others feel but with this kind of frictionless setup, plus low intuitivity in the UX/UI of those services, people are not concerned about setting up a credit card, and billing bundling between services (e.g. AWS batch + Lambda + EC2) is part of the business model.
I do not know how to articulate it, but it's more or less like those modern amusement parks where you pay to enter the facility, and for every attraction and even the toilet you pay to go.
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#9I was able to get the charges reversed, but definitely learned not to trust their guides.
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#10- Choose the lowest cost resource (it's a tutorial!)
- Cleanup resources when the `delete` subscript is run
I don't think it's fair to expect developers to do paranoid sweeps of their entire AWS account looking for rogue resources after running something like this.
If a startup had this behavior would you shrug and say "this happens, you just have to be paranoid"? Why is AWS held to a different standard by some?