Show HN: Freeze – Amazon Glacier GUI Client for Mac OS X
freezeapp.net
freezeapp.net
Feedback:
* Help me figure out how to get at an access key and secret for my account. That could be as simple as including a button that opens up Safari with the IAM console, or as awesome as working with IAM. Right now, this is probably your product's biggest stumbling block, as Amazon's user experience is atrocious.
* "Do you want to initiate inventory retrieval for all non-empty vaults of region US East (N. Virginia)?" — I dunno, you tell me.
* They're always "OK" buttons, not "Ok"
* Inventory and Transfers visibility shouldn't be mutually exclusive
One advantage I can see is more flexible cost, you pay for what you use. Is there other differences?
and they are king of tracking users. nobody does better
if you require source to know that google has the least segmented audience, you are clearly not in advertisement.
why do you think google pushed so hard for g+? or why it keeps trying to keep people logged while searching? even with all that, they are still way behind.
Let me queue up a set of actions and tell me what those actions will cost. Also, track my daily/weekly/monthly cost and tell me what the new rate will be after a given set of actions.
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 average monthly storage (pro-rated daily) for free each month. If you choose to retrieve more than this amount of data in a month, you are charged a retrieval fee starting at $0.01 per gigabyte. Learn more. In addition, there is a pro-rated charge of $0.021 per gigabyte for items deleted prior to 90 days. Learn more
Let's say you store 1TB and decide to download it all later. The retrieval fee is $9.73 (1024GBx0.95x$0.01) and data transfer is $92.07 (1023x$0.09). That's over $100 for just that one retrieval.
When I needed to do a retrieval several months ago, I was able to limit my expense to $7/pcm and just let my client retrieve as fast as it could.
Details are on the aws blog here:https://aws.amazon.com/blogs/aws/data-retrieval-policies-aud...
> "No proprietary encoding of archive descriptions. No proprietary encryption or compression features that would make it complicated or even impossible to use other clients."
That makes it different and more usable (at least for me), even if its behavior isn't "Time Machine" alike.
A trial or a demo would be nice.
Not being proprietary is an advantage. Freeze is as simple as it can be.
I really do not know.
But it is not meant to be a replacement for a full featured backup solution like Arq. I think some people like it a bit more "low-level" and simple and that's what Freeze is for.
I don't like built-in encryption features in file transfer or backup apps too much, because they are often proprietary and that may make it hard to switch to another client.
As a workflow example, I personally encrypt my archives with gnupg and store them on external hard drives and additionally upload them to Glacier for disaster recovery.
On the other hand I find manual local encryption a bit cumbersome workflow wise...
> Amazon Glacier handles key management and key protection for you. Amazon Glacier uses one of the strongest block ciphers available, 256-bit Advanced Encryption Standard (AES-256). 256-bit is the largest key size defined for AES. Customers wishing to manage their own keys can encrypt data prior to uploading it.
I've been running it for the past few hours to put backups of my photos to Glacier. I have zips of each album which vary from a few megabytes to a few gigabytes - in total it's around 40GB. My internet connection isn't that reliable, so around half the uploads have failed with 'Connection Interrupted'. It would be great if they were automatically requeued (maybe at the end of the list?) and were able to be resumed without starting from scratch (I assume behind the scenes uploads are multipart?).
Yes, Freeze uses multipart uploads with 16 MB chunks. Resuming multipart uploads works chunk-wise, for example when you've uploaded 20 MB and then the connection drops, the upload then continues at chunk number 2. When you see that an upload restarts from scratch, then the connection was probably interrupted while trying to upload the first 16 MB.
About automatic retries: Freeze automatically retries 3 times and then you have retry manually.
For unreliable and slow internet connection I recommend setting max. parallel uploads to 1 and disabling the upload speed limit.
I plan make the chunk size configurable for a future update. I makes sense to use a smaller upload chunk size for unreliable internet connections.
$0.055 per 1,000 requests
Command line tool[1] split my 12GB into 1mb chunks and generate around 12k requests:
$0.055 per 1,000 requests 12,694 Requests $0.70
So bigger chunks are cheaper, but probably generate more retries.
[1] - https://github.com/uskudnik/amazon-glacier-cmd-interface
They're not half as sleek though.