New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws s3 cp/mv --recursive incorrectly reports object as needing to be restored from glacier #2385
Comments
I needed to use --force-glacier-transfer. |
Google led me here for the same error message. It would be nice if that option were suggested in the error message. |
how much cost in money it takes on this flag " --force-glacier-transfer." ? |
thoward-godaddy
pushed a commit
to thoward-godaddy/aws-cli
that referenced
this issue
Feb 12, 2022
* ci: Enable basic mypy typechecking
thoward-godaddy
pushed a commit
to thoward-godaddy/aws-cli
that referenced
this issue
Feb 12, 2022
…he future (aws#2396) * Revert "Remove import from builtins" This reverts commit 0ecbbe45105896e8e4c9c1823c75e490752b0433. * Revert "chore: Enable basic mypy typechecking" This reverts commit 9d29984c652ef8d0466e023cd5ee79503aa4a9e9.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a directory of files on S3 that was transitioned to glacier. The files were recently restored from Glacier and have not yet expired. I can copy individual files using "aws s3 cp". But, if I attempt to recursively copy the entire directory, the aws cli gives me the following error on all files:
The text was updated successfully, but these errors were encountered: