CDK: switch to CloudFront EdgeFunction
See original GitHub issueIs your feature request related to a problem? Please describe. At the moment, CDK stacks have to be deployed to us-east-1 because of the Lambda@Edge function.
Describe the solution you’d like
The CloudFront module provides a (experimental) EdgeFunction
module that behaves exactly like a normal Function
, however if the stack is deployed to a region that isn’t us-east-1, it will isolate the function into a new stack and create the function in the correct region.
Current blockers
I’ve tried to switch to EdgeFunction
locally, and there are a few issues:
Re the circular dependency, the only solution seems to be using another stack and importing the role in. We could have ‘support’ constructs that go into a separate shared stack, which would also solve #947.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:5
Top GitHub Comments
Hey Arjun, this sounds great. I’m hesitant to jump in a use an experimental module, although either way, I’ll have a play with this myself.
Any updates on this?