Move objects in Deep Glacier Archive from one account to another while preserving storage class

Question

Looking for the best approach to moving data in S3 Glacier Deep Archive from one account to another, while preseving current storage class. Any solutions I've come across thus far seem to indicate that all data must be retreived from Deep Archive before copying, which feels redundant and costly given that the data should ultimately remain in Glacier Deep Archive in the destination account.

What is the least costly approach to doing this? Can it be done without first performing (e.g.) a Bulk Retrieval on the original data and then subsequently moving back to Glacier Deep Archive in the destination account?

Answer

Unless AWS Support can work out something custom with you, migrating the data will require you to retrieve it from Glacier in the origin account, and sending it to Glacier in the destination account. You'll probably want to do it from within AWS itself so you don't end up paying egress fees on that data getting it to your local workstation...

Answer

Data stored in S3 Glacier Deep Archive must be retrieved/restored before said data can be moved/copied, regardless of the destination storage class. The best way to copy this data in my opinion, after restoring the data, would be to use the Copy S3 Batch Operation: https://docs.aws.amazon.com/AmazonS3/latest/userguide/batch-ops-copy-object.html#batch-ops-examples-copy

Move objects in Deep Glacier Archive from one account to another while preserving storage class

相关内容