2 ms·
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 acce
by chimeracoder 13y ago
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 has come and gone, you're still paying for that peak until the end of the month, no matter how low your usage might fall. [0]
Note: I still use Glacier for long-term backup, because that's the exact use case it's meant for. But it's important to be aware of that cost: if I ever need to retrieve that data, I know I need to do it very slowly (and carefully) to avoid racking up a massive bill.
[0] http://www.daemonology.net/blog/2012-09-04-thoughts-on-glacier-pricing.html http://www.daemonology.net/blog/2012-09-04-thoughts-on-glaci...
- copergi 13y agoThere's a few calculators that make it quite simple to figure out restore costs.
- mjn 13y agoIt's true that Glacier is a bit tricky, but you can easily cap your retrieval costs (with a bit of margin) if your use-case allows you to choose a maximum retrieval rate, rather than thinking in terms of retrieval amount. If your peak hourly retrieval rate for a month is N Mbps, your cost is no more than $3N. So for example, $30 for a month that includes 10 Mbps retrievals, $300 for 100 Mbps retrievals, etc. A bit more detail in an older comment of mine: https://news.ycombinator.com/item?id=7147325 https://news.ycombinator.com/item?id=7147325