New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Glacier support #81
Comments
Sure. Maybe a quicker goal might be Glacier-S3 support though, as it's just
|
Glacier-S3 support would be preferable, actually. At least as far as git-annex goes. amazonka seems to have also taken this approach; it doesn't have bindings to the glacier API currently, but does support the S3 to glacier lifecycle. What seems to be needed: http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTlifecycle.html http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPOSTrestore.html |
Object lifecycle management is also now important to use the Infrequent Access storage class. A user may want to put an object to the standard class to start with, but degrading to the IA storage class after a while, and then later to glacier. Storage class configuration is a rather complex xml document, so a data type that expresses it well would be convenient for users. Amazonka has one here: http://hackage.haskell.org/package/amazonka-s3-1.3.2/docs/Network-AWS-S3-Types.html#t:BucketLifecycleConfiguration |
It would be nice if aws would support Amazon Glacier. Possibly, this would make it possible for git-annex to support Glacier without external tools.
The text was updated successfully, but these errors were encountered: