2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
I'd get CF out of the equation for troubleshooting, and spit out the signedurl request you are making, look at the request to see if there is anything obvious, and try to curl that.
Not sure offhand what detail the S3 access logs capture on these requests, but might try enabling logging and checking that out (possibly best to to this to a test bucket so you can easily locate the logs, etc).
con risposta 5 anni fa
0
I was able to resolve the issue using the following steps:
Go to the cloudfront distribution
Click on the Behaviors tab
Select the checkbox and click on Edit
Select Trusted Signer in the Trusted Key Groups or Trusted Signer radio button
Click Save
https://www.lazydeveloper.tech/aws/aws-cloudfront-invalidkey-unknown-key-when-using-signed-urls/
con risposta 3 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 8 mesi fa