Closed marcelloromani closed 1 week ago
In true rubber-duck debugging fashion, after submitting this bug I searched online for some more SignatureDoesNotMatch
reports and realised the issue might be the request going through a proxy.
Lo and behold, http_proxy
and https_proxy
were set to a proxy server.
The fix was thus:
$ unset http_proxy
$ unset https_proxy
at which point the multipart threshold didn't make any difference (a part from influencing performance as expected).
The whole transfer also got a lot faster (probably the proxy was overwhelmed).
Mountpoint for Amazon S3 version
mount-s3 1.10.0
AWS Region
us-east-1
Describe the running environment
Running in EC2 RedHat 8 Linux Connected to the EC2 instance via Session Manager
sh-4.4$ whoami ssm-user
Copying the file with
failed with:
I then issued
and repeated the
aws s3 cp
command, which now succeeded.I am mounting the bucket with
I can copy small files with no issues.
When trying to copy a 100MiB file instead the log shows:
My hypothesis
Setting the aws cli multipart threshold to a high value means that the whole file was transferred in one go instead of using multi-part. That solved the issue for the aws cli cp.
Mount-s3 instead uses multipart read with apparently no possibility to disable this feature.
note I uploaded the file to S3 from a different machine, using different credentials than those on the EC2 instance where mount-s3 is running.
Mountpoint options
What happened?
fails with:
Relevant log output