#10681 closed enhancement (fixed)
Amazon S3 Glacier Deep Archive storage class
Reported by: | FunnyLip | Owned by: | dkocher |
---|---|---|---|
Priority: | normal | Milestone: | 7.3.1 |
Component: | s3 | Version: | 6.9.4 |
Severity: | normal | Keywords: | aws, s3, gda |
Cc: | iulian_ionitaro@… | Architecture: | |
Platform: |
Description
With AWS GDA now out and usable, it would be lovely to be able to directly access it.
Change History (5)
comment:1 Changed on Sep 13, 2019 at 9:24:31 PM by sirgatez
comment:2 Changed on Mar 18, 2020 at 2:00:15 AM by Julica
- Cc iulian_ionitaro@… added
I think it would be great at least to push to both Glacier and GDA directly as we understand there is a long restore time from Glacier.
comment:3 Changed on Apr 21, 2020 at 7:51:17 AM by dkocher
- Milestone set to 7.3.1
- Owner set to dkocher
- Status changed from new to assigned
comment:4 Changed on Apr 21, 2020 at 11:38:09 AM by dkocher
Added Glacier Deep Archive storage class in r49054.
comment:5 Changed on Apr 21, 2020 at 11:38:25 AM by dkocher
- Resolution set to fixed
- Status changed from assigned to closed
Allow selection of Glacier storage class as default for uploads in r49056.
Note: See
TracTickets for help on using
tickets.
Not only is Glacier Deep Archive supported, you can not PUT directly to Glacier and Glacier Deep Archive within the PUT request. Could we get an update to support this functionality? Thanks :-)
It would also be nice to make sure any objects required to use Cryptomator to browse a vault, should obviously not be pushed to this storage layer unless a user explicitly requests to do so. It's understandable if I need to wait to restore an object before I can get it from the vault.
https://aws.amazon.com/about-aws/whats-new/2018/11/s3-glacier-api-simplification/