You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Got the problem:
AWS used to be lenient earlier with bucket name and key name, but now it's being validated strictly. We used to pass
bucketName = bucketName + path
key = fileName
This is being rejected by now. Need to pass bucketName as name only and add the path to the key
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or 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.
Describe the bug
While trying to use s3 client put object method, it is returning this error message. The error comes with .net framework only, .net core works fine.
The request signature we calculated does not match the signature you provided. Check your key and signing method.
Expected Behavior
It used to work fine with .net framework and was able to put an object without any errors
Current Behavior
Getting above error probably since daylight savings changes!?
Reproduction Steps
var amazonS3Client = new AmazonS3Client();
var s3PutRequest = new PutObjectRequest
{
BucketName = param.bucketName,
Key = param.key,
ContentBody = param.data
};
var s3PutResponse = await amazonS3Client.PutObjectAsync(s3PutRequest);
Possible Solution
No response
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
AWSSDK.Core: 3.7.202.18
AWSSDK.S3: 3.7.205.4 and 3.7.205.5 (Error started on 3.7.203.7)
Targeted .NET Platform
.NET Framework 4.8
Operating System and version
Windows 11
The text was updated successfully, but these errors were encountered: