4 ms·
Overly complex but workable. Which seems like a lot of how AWS operates. I guess the "prefix" could be a pseudo-folder? Although the objects are archived in G
by ck2 14y ago
Overly complex but workable. Which seems like a lot of how AWS operates.
I guess the "prefix" could be a pseudo-folder?
Although the objects are archived in Glacier, you can't get to them via the Glacier APIs. Objects stored directly in Amazon Glacier using the Amazon Glacier API cannot be listed in real-time, and have a system-generated identifier rather than a user-defined name.
So per usual we have no clue how many actual files are in an AWS service (without a complex/expensive transaction) the true directory structure or total size.
Since there is no inbound bandwidth charge, might as well upload directly to glacier via the api for more control.
- twiceaday 14y agoThe archived S3 files don't show up in Glacier because they still show up in S3, they simply have a different storage type. To restore the file you simply right click it and click restore, after 3-5 hours it puts the file back into the bucket. To interact with the archived files via cli you have to go through S3 and not Glacier, as again the files are "in" S3.
- jeffbarr 14y agoThink of Glacier as another storage class for S3 when used in this way. We have regular, reduced redundancy, and now Glacier.
- ck2 14y agoThat actually should have been their entire API extension to integrate S3 with Glacier. Change the storage type, via the aws console or API from Storage Class: Standard <-> Reduced Redundancy <-> Glacier When toggled to Glacier, it archives it, when toggled back to standard or reduced, it moves it back to S3. Would have been beautifully simple and practical.
- jeffbarr 14y agoAnd yes, your prefix can be a pseudo-folder.