You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have one stack for all our resources (db/cognito/cloudfront/s3 etc) and another stack for all our lambdas and API gateway.
If I first add a cloudfront distro in the resources stack and then add a lambda@edge in the API stack, all works as expected (nice!). But if I go back and update the cloudfront in the resources stack, ex. enable compression, then the lambda@edge is no longer associated with the cloudfront.
Any thoughts / workarounds?
All the best.
The text was updated successfully, but these errors were encountered:
Hi!
We have one stack for all our resources (db/cognito/cloudfront/s3 etc) and another stack for all our lambdas and API gateway.
If I first add a cloudfront distro in the resources stack and then add a lambda@edge in the API stack, all works as expected (nice!). But if I go back and update the cloudfront in the resources stack, ex. enable compression, then the lambda@edge is no longer associated with the cloudfront.
Any thoughts / workarounds?
All the best.
The text was updated successfully, but these errors were encountered: