- Newest
- Most votes
- Most comments
The move options essentially the copies the object which cannot be done when the objects are in Deep Archive. If you have large number of objects, you can do the following.
- Use lifecycle policy to identify (using prefix or tags) and restore the objects from Deep Archive to Standard.
- Run a batch operation to copy the objects to the new path.
- Write another lifecycle policy to move the copied objects to Deep Archive.
- If versioning enabled, write another lifecycle policy to delete previous versions.
Note that,
- There will be costs associated with moving the objects between the storage tiers.
- If you have versioning enabled, you will need to delete the versions from the previous path.
The issue you're experiencing seems to be related to objects stored in the S3 Glacier Deep Archive storage class. This storage class has some specific limitations when it comes to moving or copying objects.
To address your problem:
-
S3 Glacier Deep Archive: Objects in this storage class cannot be directly moved or copied. They need to be restored first before any operations can be performed on them.
-
IAM Permissions: While the IAM policy you've added includes necessary permissions for standard S3 operations, it may not be sufficient for working with Glacier Deep Archive objects. You might need additional permissions related to Glacier operations.
-
Moving folders: In S3, folders are actually prefixes for objects, not true folders. Moving a "folder" involves copying all objects with that prefix to a new location and then deleting the originals.
-
Size limitations: If any of your objects are larger than 5 GB, you cannot move them using the S3 console. You'll need to use the AWS CLI or SDKs for such operations.
-
Waiting period: When moving folders, especially with many objects, the operation may take some time to complete. It's advisable to wait for the move operation to finish before making additional changes.
To resolve this issue:
- First, restore the objects from Glacier Deep Archive if they're in that storage class.
- Use the AWS CLI or SDK for moving large objects or folders with many items.
- Ensure your IAM policy includes all necessary permissions, including those for Glacier operations if needed.
- Consider using S3 Batch Operations for moving large numbers of objects efficiently.
If the problem persists, you may need to contact AWS Support for more specific assistance related to your account and configuration.
Sources
Copying, moving, and renaming objects - Amazon Simple Storage Service
Moving objects to Glacier Deep Archive in S3 | AWS re:Post
answered 2 years ago
Relevant content
asked 3 years ago
asked 3 years ago
asked 3 years ago
- AWS OFFICIALUpdated 5 months ago

You dont need another LC to move/transition objects back to GDA. In this step - Run a batch operation to copy the objects to the new path, you can choose destination class as GDA. --- However if you need to access the object and keep in hot class for some time then only use LC policy to switch storage-class based on age.
Thanks, but when I try to Restore this folder using this guide (https://docs.aws.amazon.com/AmazonS3/latest/userguide/restoring-objects.html), the option is greyed out?