I'm curious how this is meant to be solved with RR? As far as I can tell, none of the submit hooks allow custom headers to be set.
Restrict access to an AWS Lambda function URL with Amazon CloudFront origin access control (OAC).
1 messages · Page 1 of 1 (latest)
I'm curious how this is meant to be solved with RR? As far as I can tell, none of the submit hooks allow custom headers to be set.
Restrict access to an AWS Lambda function URL with Amazon CloudFront origin access control (OAC).
By adding x-amz-content-sha256 of the payload in the header. But for a public accessible URL, that's not required:
Never sign origin requests
...
To use this setting, the Lambda function URL must be publicly accessible. If you use this setting with a Lambda function URL that's not publicly accessible, CloudFront can't access the origin.
But I wanted them to be signed...
The docs say to calculate the hash of the payload and put the x-amz-content-sha256 in the request header.
Yes? But it seems none of RR's submit hooks have a way of setting headers?