Closed bughunt8 closed 2 years ago
After retrying this - this seemed to have resolved. Closing this for now.
Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Confirm by changing [ ] to [x] below to ensure that it's a bug:
Describe the bug According to: https://aws.amazon.com/premiumsupport/knowledge-center/restore-s3-object-glacier-storage-class/, the "s3 cp" should be used to overwrite the existing glacier object.
SDK version number % aws --version
Platform/OS/Hardware/Device macOS 10.15.7
To Reproduce (observed behavior)
Assuming the Bucket is bucket1 and Key is /dir1/file1.mp4, then the commands are: (Bucket is Private only, File/Key is in GLACIER)
% aws s3api restore-object --bucket bucket1 --restore-request Days=7,GlacierJobParameters={Tier=Bulk} --key dir1/file1.mp4 % aws s3api head-object --bucket bucket1 --key dir1/file1.mp4
% aws s3 ls s3://bucket11/dir1/
% aws s3 cp s3://bucket1/dir1/file1.mp4 s3://bucket1/dir1/file1.mp4 --storage-class ONEZONE_IA --debug
Expected behavior A successful copy operation. The same command used to work back in Dec 2021.
Logs/output % aws s3 cp s3://bucket1/dir1/file1.mp4 s3://bucket1/dir1/file1.mp4 --storage-class ONEZONE_IA --force-glacier-transfer --debug