News for hackers. Stuff that matters.

A comment on AWS mistakes to avoid. Parent comment

Re:AWS mistakes to avoid by Sir_Cmpwn on Sunday December 27, 2015 @03:28AM (#10796846)
This is correct. The biggest cost I saw was bandwidth, followed by cycles on their machines. MediaCrush was a "media hosting website" (see original comment) and as such, used a lot of bandwidth and did a lot of work transcoding things, and had a large storage requirement.
[ Parent | on HN ]
Re:AWS mistakes to avoid by wise_young_man on Sunday December 27, 2015 @03:47AM (#10796882)
Were you comparing bandwidth/data transfer in your numbers for EC2, S3 or CloudFront?
[ Parent | on HN ]
Re:AWS mistakes to avoid by Sir_Cmpwn on Sunday December 27, 2015 @03:53AM (#10796892)
I don't know, it was an anecdotal story from a while ago. Before we left AWS we were utilizing all three (iirc these numbers didn't factor in CloudFront though). Point I'm making is - do the research and don't just reach immediately for AWS.
[ Parent | on HN ]
Re:AWS mistakes to avoid by wise_young_man on Sunday December 27, 2015 @03:58AM (#10796897)
Oh okay I was just curious. I completely agree. The AWS bill at my startup went up quite a bit after the free trial ended since there are many variables that are included with each service such as how many requests/mo, tiered bandwidth, etc. The AWS calculator is nice and so is the billing estimator, but it's still quite confusing.
[ Parent | on HN ]