1 Answer
- Newest
- Most votes
- Most comments
2
Hello.
Judging from the answer at the URL below, it seems that the problem can be resolved by signing using something like Lambda@Edge or by including the "x-Amz-Content-Sha256" header containing the hash of the payload in the request.
https://repost.aws/ja/questions/QUbHCI9AfyRdaUPCCo_3XKMQ/lambda-function-url-behind-cloudfront-invalidsignatureexception-only-on-post
Relevant content
- Accepted Answerasked 3 months ago
- Accepted Answerasked 7 months ago
- asked 8 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 14 days ago
That's what I thought but that was from a couple of months ago so I thought I'd check to see if anything had changed since.
I also tried a POST request, but it resulted in an error, so I think it probably hasn't been changed.