←back to thread

I Followed the Official AWS Amplify Guide and Was Charged $1,100

(elliott-king.github.io)
461 points thunderbong | 3 comments | 14 Nov 24 06:48 UTC | HN request time: 1.497s | source
Show context
braza ◴[14 Nov 24 07:45 UTC] No.42133929[source]▶
> Even if you are not using Amplify/OpenSearch, I recommend getting familiar with AWS budgets. > It’s so difficult to be paranoid about every single technology you use.

I 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.

replies(1): >>42133982 #
1. karolist ◴[14 Nov 24 07:53 UTC] No.42133982[source]▶
I feel so to. The cloud billing model shifts responsibility to users under the guise of "flexibility" and "customization". Imagine a car rental company that charges you by the millisecond for every component - engine camshaft revolutions, tire rotations, windshield wiper activations, seat heating time and so on, but has the ability to set up alerts for each component so that customers "control" their usage and budget. It's just user hostile, risky by default cost model.
replies(1): >>42134093 #
2. snoman ◴[14 Nov 24 08:13 UTC] No.42134093[source]▶
The alternative is charging for the rental by the day but a huge proportion of your customers (who probably own a bmw) constantly complain that they’re being overcharged and they want a discount cause they don’t need the blinkers, and refuse to pay for them.

I joke, but this persona is very real, and it leads you to this nickel and dime billing model.

replies(1): >>42134520 #
3. blitzar ◴[14 Nov 24 09:38 UTC] No.42134520[source]▶
Being cheap (in this way) is so often incredibly expensive.