In the git-annex docs for S3, under storageclass, it says
Amazon S3's DEEP_ARCHIVE is similar to Amazon Glacier. For that, use the glacier special remote, rather than this one.
However, Amazon has deprecated the standalone Glacier API, in favor of the S3 Glacier storage classes like S3 Glacier Deep Archive. As I understand it, new AWS accounts cannot sign up for Glacier at all, and existing accounts can only use it if they already had been using it. Instead, Amazon wants you to use the S3 classes, which are the same price but use the S3 API instead of the Glacier API.
For new repositories, should we use S3 with storageclass=DEEP_ARCHIVE?
It's not clear to me if this will work correctly, if the git-annex S3 implementation is built to handle S3 Glacier storage classes correctly. If not, what should we do since we can't use the standalone Glacier anymore?
I don't think
storageclass=DEEP_ARCHIVEwill currently work, git-annex is not able to request that the object be restored.See https://git-annex.branchable.com/todo/wishlist__58___Restore_s3_files_moved_to_Glacier/ for a todo which would solve this.
I've implemented this now, S3 special remote can be configured with
restore=yesand it will initiate a restore.