3 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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
con risposta 2 anni fa
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
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa