presigned url unmatching signature
Hello,
Apologize me if the question seemed noob. I wasted hours trying to debug it.
If I copy a presigned put url from Tigris web interface, the following works:
However, if I generate a presigned url from AWS CLI I get a signature failure:
It is generated by:
Running
and the access key matches the one shown in the Tigris web interface.
I saw this but it does not seem relevant.
P.S. The working URL generated from the web interface looks like:
The failed URL generated by AWS CLI looks like:
Apologize me if the question seemed noob. I wasted hours trying to debug it.
If I copy a presigned put url from Tigris web interface, the following works:
However, if I generate a presigned url from AWS CLI I get a signature failure:
It is generated by:
Running
aws configureand the access key matches the one shown in the Tigris web interface.
I saw this but it does not seem relevant.
P.S. The working URL generated from the web interface looks like:
The failed URL generated by AWS CLI looks like:
Fly.io
I’m getting SignatureDoesNotMatch when creating a presigned-url for PUT. const url = await getSignedUrl( s3Client, new PutObjectCommand({ Bucket: config.AWS_BUCKET, Key: key, }), { expiresIn: dayjs.duration(10, 'minutes').asSeconds(), } ); Log output for debugging purposes: [3:12:26 ...
Solution
Update. Python’s SDK works.
Update. I used curl’s built‑in aws sig v4 and the following did successfully work:
Note. For the record, a developer may deploy a python app which generates presigned URLs for generic HTTP requests.
Note. I still don’t know why AWS CLI does not generate a correct signature.
Update. I used curl’s built‑in aws sig v4 and the following did successfully work:
Note. For the record, a developer may deploy a python app which generates presigned URLs for generic HTTP requests.
Note. I still don’t know why AWS CLI does not generate a correct signature.
