Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Amazon S3 Pricing Changes Effective April 1, 2014

aws.amazon.com

Post reply on HN
Print view View original

51–60 of 189 posts

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#51

Post by [deleted] »

brianwawok wrote: post #46
toomuchtodo wrote: post #32

Earlier quoted context omitted.

Not having to wait 4-8 hours to access them. Also, pulling from S3 costs you nothing (if you're in EC2 or other AWS services). Glacier access costs can get expensive depending on the quantity of data you need to access in a short period of time: "Glacier is designed with the expectation that retrievals are infrequent and unusual, and data will be stored for extended periods of time. You can retrieve up to 5% of your…

What if you have 100 TB? I would quibble over 25k a year..

[deleted]

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#52

Post by robbles »

thomaslangston wrote: post #8

My concern is what it always been for AWS, no first party support for limiting my bill. The best effort from AWS is just an email notification when they "think" my bill is over a limit. If I can't limit my risk to a surprise bill of thousands of dollars after missing a midnight email, I still can't use their service at any usage based price other than free.

You actually can do this yourself quite readily, through use of CloudWatch billing metrics (which can be broken down by individual service). Define some alarms based on billing thresholds, and perform automated scaling actions in response.

AWS can't exactly do this for you, as explained by previous commenters, but they do give you the basic features you'd need for implementing it.

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#53

Post by chris_mahan »

balls187 wrote: post #47
thomaslangston wrote: post #8

My concern is what it always been for AWS, no first party support for limiting my bill. The best effort from AWS is just an email notification when they "think" my bill is over a limit. If I can't limit my risk to a surprise bill of thousands of dollars after missing a midnight email, I still can't use their service at any usage based price other than free.

While not the best solution, you can call Amazon, speak to someone to have your "surprise" bill mitigated. This is 1st hand information from a AWS Rep I once dated.

That is so wrong it's not funny. Call? Isn't our use of computers predicated on the notion that we don't want to do manual labor?

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#54

Post by hatred »

frade33 wrote: post #43
dekhn wrote: post #18

Earlier quoted context omitted.

Gdrive is not a competitor to S3. Google Cloud Storage is.

I should have made it clear, thanks for pointing it out. I guess this was in the wake of Google Cloud Platform pricing going down yesterday?

Also Amazon's Gdrive competing equivalent is cloud drive.

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#55

Post by bowlofpetunias »

thomaslangston wrote: post #8

My concern is what it always been for AWS, no first party support for limiting my bill. The best effort from AWS is just an email notification when they "think" my bill is over a limit. If I can't limit my risk to a surprise bill of thousands of dollars after missing a midnight email, I still can't use their service at any usage based price other than free.

If you're able to set up a service that risks a high bill, but cannot set up something that turns an email into some other action (anything from a text message to automatically shutting down your service), I don't think the limitations of AWS are the problem...

(Having said that, AWS could really do a lot better with it's notification targets than just email.)

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#56

Post by ericd »

robbles wrote: post #52
thomaslangston wrote: post #8

My concern is what it always been for AWS, no first party support for limiting my bill. The best effort from AWS is just an email notification when they "think" my bill is over a limit. If I can't limit my risk to a surprise bill of thousands of dollars after missing a midnight email, I still can't use their service at any usage based price other than free.

You actually can do this yourself quite readily, through use of CloudWatch billing metrics (which can be broken down by individual service). Define some alarms based on billing thresholds, and perform automated scaling actions in response. AWS can't exactly do this for you, as explained by previous commenters, but they do give you the basic features you'd need for implementing it.

If you can get something to monitor your billing rate, you might be able to get PagerDuty to call you if your billing rate goes over x per hour.

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#59

Post by toomuchtodo »

eli wrote: post #44
toomuchtodo wrote: post #6

Earlier quoted context omitted.

Unless you're storing massive amounts of data, no point in using Glacier now, as it's still $0.01/GB (vs $0.03/GB for standard durability). And wow. Hell of a price drop.

300% is still 300%.

It's only 300% for the first TB in S3. It gets progressively cheaper after that.
Post reply on HN