diff options
| author |  http://svario.it/gioele <http://svario.it/gioele@web> | 2013-05-31 08:01:56 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-05-31 08:01:56 +0000 |
| commit | b93837a9c566e6209ecffb9da578a64240f37bd6 (patch) | |
| tree | 64b63f5393589c7ed265690a61c5202a1a030d87 | |
| parent | d90ec71751c6e7961e14f999a6fd839a21f0e147 (diff) | |
new wishlist: Restore S3 files moved to Glacier
| -rw-r--r-- | doc/todo/wishlist:_Restore_s3_files_moved_to_Glacier.mdwn | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/todo/wishlist:_Restore_s3_files_moved_to_Glacier.mdwn b/doc/todo/wishlist:_Restore_s3_files_moved_to_Glacier.mdwn new file mode 100644 index 000000000..85fc2785c --- /dev/null +++ b/doc/todo/wishlist:_Restore_s3_files_moved_to_Glacier.mdwn @@ -0,0 +1,7 @@ +I would like to use the automated AWS lifecycle rules to move the git annex files store on S3 to Glacier after a bit of time. Git annex need must support this kind of S3 files explicitly in order for it to work. + +This is different from the adding a Glacier remote to git annex because of the reasons explained in <http://aws.typepad.com/aws/2012/11/archive-s3-to-glacier.html>. + +Basically, the files moved by AWS from S3 to Glacier are not available under the normal Glacier API. In fact, the moved S3 files are listed as available but under the `GLACIER` storage class and need a RESTORE request before they can be GET like other S3 files. Trying to GET an S3 file that has been moved to Glacier will not restore it from Glacier and will result in an 403 error. + +I suppose DELETE needs special care as well. |