i opened an aws account, but then was too anxious to move on and build something with it
I Followed the Official AWS Amplify Guide and Was Charged $1,100
61–70 of 293 posts
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#62Earlier quoted context omitted.
It is very unusual for AWS not to issue refunds in situations like this, so I don't think it's a function of them finding an edge to milk thousands from user mistakes. More likely they've found that issuing refunds is less onerous than it would be to provide accurate and cheap tutorials. Perhaps that does not excuse the behaviour but AWS reversed a $600 charge I incurred using AWS Textract where the charges were comp…
> It is very unusual for AWS not to issue refunds in situations like this ...when asked to. But what percentage of mistakes like this end up just being "eaten" by the end-user, not realizing that they can ask for a refund? What percentage don't even get noticed?
I encountered similar situation twice and AWS did not issue a refund both times. I'm avoiding AWS like plague now. Not going to rely on goodwill of support person handling my ticket today.
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#63Earlier quoted context omitted.
> do paranoid sweeps of their entire AWS account looking for rogue resources That's the thing that annoys me the most about AWS. There's no easy way to find out all the resources I'm currently paying for (or if there's a way, I couldn't find it). Without an easy to understand overview, it feels like I don't have full control of my own account.
You can set up daily or hourly cost and usage reports on the account. I built a finops function based on it, feeding the data into a Postgres db. Make sure to select incremental updates, if not you’ll en up paying for tb of s3 storage.
TB of S3 storage is surprisingly inexpensive though. Especially compared to everything else AWS.
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#64This seems like a glaring bug in the scripts run by that `npx` command. The author is correct, the scripts should 100%: - 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 wou…
My first line of research when I have to use something new is: Can I get a fixed bill every month? What happens if I use more than that, can I limit surprises? If not, I will find something else. We are also very careful with building us into "free" google services after the map surprise a few years ago. That cost us a lot of money in the end.
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#65And here I'm concerned about the 30€/mo I pay for running my (quite fat) home server... at least the metal can't randomly expand and consume 10kW all of a sudden.
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#66unrelated rant, but I'm still salty about it. needed to send "raw" http requests instead of using their bloated sdk for reasons, and requests failed with "content-type: application/json" header, but succeeded with "content-type: application/x-amz-json-1.0". get out of here with that nonsense.
I feel this way about pretty much every aspect of AWS I have touched in my career. Overly bloated, overly complex or weird home brew implementation for no clear gain.
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#67unrelated rant, but I'm still salty about it. needed to send "raw" http requests instead of using their bloated sdk for reasons, and requests failed with "content-type: application/json" header, but succeeded with "content-type: application/x-amz-json-1.0". get out of here with that nonsense.
Didn't you know, Amazon owns JSON? They acquired it this week, please update all your Content-Type headers within 12 months otherwise you will be in violation of their IP holdings.
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#68[dead]
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#69After handling so many of these cases I decided to build a solution that helps with cost monitoring and optimization. It's a single click integration with AWS and Azure.
We're currently working on a solution for these specific cases as well, would love to hear some feedback.
CloudExpat - www.cloudexpat.com
Re: I Followed the Official AWS Amplify Guide and Was Charged $1,100
#70Earlier quoted context omitted.
> do paranoid sweeps of their entire AWS account looking for rogue resources That's the thing that annoys me the most about AWS. There's no easy way to find out all the resources I'm currently paying for (or if there's a way, I couldn't find it). Without an easy to understand overview, it feels like I don't have full control of my own account.
Yes i was charged $400 once for services i had running for three months without any idea it was happening
We were billed about $5000 per month by Google even though we had asked what the billing change would mean for us and they said you will be inside the free limits. Turns out we weren't.