I have an AWS Lambda function connected to an API Gateway (Regional HTTP API) and my domain is linked to CloudFront. However, my application's canonical URL is being set to the API Gateway domain instead of my CloudFront domain. How can I ensure that my Lambda function correctly uses the CloudFront domain in the canonical URL when for example react or qwik js generates SSR?
I have an AWS Lambda function connected to an API Gateway (Regional HTTP API) and my domain is linked to CloudFront. However, my application's canonical URL is being set to the API Gateway domain instead of my CloudFront domain. How can I ensure that my Lambda function correctly uses the CloudFront domain in the canonical URL when for example react or qwik js generates SSR?
Share Improve this question asked 9 hours ago Aren SadeAren Sade 5661 gold badge9 silver badges26 bronze badges1 Answer
Reset to default 0To ensure your Lambda function receives the correct domain (CloudFront instead of API Gateway), you need to configure CloudFront to forward the Host header. By default, CloudFront may replace the Host header with the API Gateway domain, which can result in an incorrect canonical URL.
Unfortunately, as far as I know, there is no direct way to pass the user's Host value from CloudFront to API Gateway and then to the Lambda function. However, a workaround I found is to create a whitelist header in CloudFront that exlude the Host value. Then, in API Gateway, you can use "parameter mapping" to set a static domain address (without the http(s) protocol, e.g., example).
While this may not be an ideal solution, it at least helps maintain consistency across different deployments, such as staging and production.