Live data from Hacker News

Amazon S3 Pricing Changes Effective April 1, 2014

aws.amazon.com

61–70 of 189 posts

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#62
post #26

Earlier quoted context omitted.

I don't think a few TB counts as "massive", and that still saves you over a grand a year. Why move backups to a 3x more expensive service, what's the upside?

Glacier's pricing is actually very difficult to calculate. If you only ever store data (and never retrieve it), it's easy, but the moment you need to start accessing it, the pricing is actually very difficult to calculate correctly: > Unlike every other service Amazon provides, with Glacier you're not paying for your net usage throughout each month: Instead, you're paying for your peak hour — and once that peak hour…

There's a few calculators that make it quite simple to figure out restore costs.

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#64

It would be interesting to go back through the Everpix post mortem docs[1] and see if a big price swing like this could have put them in the black (or close to it). [1] https://github.com/everpix/Everpix-Intelligence

That's no different than startups of the past having to pay thousands to millions of dollars to setup servers. These days those same servers can be setup in minutes for a fraction of the cost.

Timing is everything. Sometimes the current market pricing for a commodity is too expensive to make your business viable today but in the future that will not be the case. Just depends how long that will take.

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#65

Earlier quoted context omitted.

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?

Moving your mouth muscles isn't significantly more manual then moving the finger muscles you used to type this comment.

In either case, expending a few neural cycles prior to the action would be beneficial.

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#66
post #26

Earlier quoted context omitted.

I don't think a few TB counts as "massive", and that still saves you over a grand a year. Why move backups to a 3x more expensive service, what's the upside?

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…

>Not having to wait 4-8 hours to access them

I can't download the data that fast anyways, it is a total non issue for us.

>Glacier access costs can get expensive depending on the quantity of data you need to access in a short period of time

Yeah, it is for backups. That's why we are talking about how we use it for backups.

>We're quibbling over ~$250/year?

Times the "few TB" we are talking about, that is over a$1k a year, as I said. We're not quibbling. I asked a simple question. Why would I take the time and effort to move my backups from a 1c/GB service to a 3c/GB service? There is no upside. "You can pay an extra $1000 for no reason, which is a great idea because $1000 isn't very much" is not very compelling.

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#67
post #24

Earlier quoted context omitted.

What "other options"? You mean sketchy "free 9000 exabytes/month of bandwidth" low end hosting places like hetzner? Those are not alternatives to AWS or azure or google cloud. And those bandwidth costs do not reflect reality, they assume most people use almost none of that bandwidth. The bandwidth still costs the same, just the big users are getting the small users to pay for their bandwidth costs.

That doesn't change the fact that you pay much less for much more.

On a completely different service. Which is the point. I get more food for $10 at burger king than I do at a hotel, but that doesn't make burger king a replacement for hotels.

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#68
post #20
post #10

Storage is cheap, but data transfer out is still $0.12/GB, over 10x more expensive than other options.

In my opinion they're doing that on purpose to discourage people from using S3 as both a storage and a transfer method. Storage and Delivery should be considered separate, as there are benefits to it being a separate service. If you throw a CDN between your customers and S3 you'll not only get a significantly lower cost, you'll also give your customers much better performance.

In that case, where's the price drop on Cloudfront?

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#69
post #24

Earlier quoted context omitted.

What "other options"? You mean sketchy "free 9000 exabytes/month of bandwidth" low end hosting places like hetzner? Those are not alternatives to AWS or azure or google cloud. And those bandwidth costs do not reflect reality, they assume most people use almost none of that bandwidth. The bandwidth still costs the same, just the big users are getting the small users to pay for their bandwidth costs.

There are lots of other options. While they may not all be "cloud" providers, there is a wealth of VPS and dedicated server providers in almost all countries you can name. I have no idea why you are picking on Hetzner in particular. They offer clearly defined bandwidth packages with their servers (20-50 TB) and charge for overages (0.2 cents per GB). Hetzner is perhaps not what you would call a premium provider, but…

>While they may not all be "cloud" providers

Then they are not "other options", that's the point.

Re: Amazon S3 Pricing Changes Effective April 1, 2014

#70

Earlier quoted context omitted.

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?

My main gig revolves around bill auditing. You'd be amazed at the number of Fortune 500's that are supposedly driven by technology that have very manual processes around billing.
Post reply on HN