3 Answers
- Newest
- Most votes
- Most comments
1
In my experience, this happens when the request doesn't exactly match the presigned URL that was created.
Make sure that you include the content type when signing the URL; and that the content type is the same when you send the request.
0
I was using a customer managed key improperly instead of the s3 managed key. That was the more specific issue
answered 2 years ago
0
After using Postman, I found out the issue is KMS. Server side encryption was enabled on the bucket and that was causing the error
answered 2 years ago
Relevant content
- asked 3 months ago
- asked 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago