- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello Heedong,
The SignatureDoesNotMatch error commonly occurs when there is a mismatch between the request signature calculated by AWS and the signature provided in the request. This can happen if the access key or secret key is incorrect or if the endpoint being used is incorrect. Based on the error message you have shared, it seems like there could be an issue with the filename that contains special characters like #. The # character is a reserved character in URLs that represents a fragment identifier. This could be causing the signature calculated by AWS to be different from the signature provided in the request.
To resolve this issue, you can try URL encoding the filename before using it in the AWS CLI command by replacing the special characters with their corresponding URL-encoded values.
For example, # can be replaced with %23. You can use the following command to encode the filename:
- export FILENAME="video_20220527_breadroll_ss6hmdf_t1_#5.mp4"
- export ENCODED_FILENAME=$(python -c "import urllib; print urllib.quote('''$FILENAME''', safe='')")
Then, you can use the encoded filename in your AWS CLI command like this:
- aws s3 cp s3://{}/ai-oven-woosong/$ENCODED_FILENAME ./
Alternatively, you can rename the file to avoid using special characters like # in the filename.
Reference:
- AWS S3 Developer Guide - Accessing Amazon S3 using the AWS SDKs: https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-character-encoding
- AWS CLI documentation - cp command: https://docs.aws.amazon.com/cli/latest/reference/s3/cp.html
With your detailed explanation, I understood exactly what caused the problem. Your good answer helped me a lot. Thank you.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 8 Monaten
- AWS OFFICIALAktualisiert vor 8 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren