3 Respuestas
- Más nuevo
- Más votos
- Más comentarios
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
respondido hace 2 años
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
respondido hace 2 años
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 4 meses
- OFICIAL DE AWSActualizada hace 3 años