Lambda Edge not working when using anything else than us-east-1

When using an AWS region other than us-east-1, I'm getting the following error:
`
CREATE_FAILED AWS::CloudFront::Distribution CFDistribution Resource handler returned
message: "Invalid request
provided:
AWS::CloudFront::Distribution:
The function must be in region
'us-east-1'. ARN:
arn:aws:lambda:eu-west-1:16178
0196320:function:oidc-auth-Clo
udFrontAuthFunction-6MGhzj0e5r
ok:1 (Service: CloudFront,
Status Code: 400, Request ID:
287a68e2-8ffe-4e8c-a7a3-0f3120
db1c8d)" (RequestToken: d88e64
29-752a-7ea7-0910-76dbb1585f45
, HandlerErrorCode:
InvalidRequest)
ROLLBACK_IN_PROGRESS AWS::CloudFormation::Stack oidc-auth The following resource(s)
failed to create:
[CFDistribution]. Rollback
requested by user.
`
In https://github.com/serverless-nextjs/serverless-next.js/issues/2179 there was a similar issue.

Reproduce the deployment with a region other than us-east-1 and inspect the CloudFront and Lambda@Edge configuration that produces the reported error. Compare the behavior with the related serverless-next.js issue 2179. Done should mean the sample deploys successfully from a non-us-east-1 configuration while satisfying CloudFront's us-east-1 Lambda@Edge requirement.

Written by the indexing model from the issue text.