When setting up a lambda@edge and we want to customize the cloudwatch, we have to declare the various region the lambda might run in and create as many cloudwatch configurations as regions. This is violating all DRY principle
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Description
When setting up a lambda@edge and we want to customize the cloudwatch, we have to declare the various region the lambda might run in and create as many cloudwatch configurations as regions. This is violating all DRY principle
Affected Resource(s) and/or Data Source(s)
Potential Terraform Configuration
References
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/edge-functions-logs.html
Would you like to implement a fix?
No