[Enhancement]: Handle Lambda@Edge cloud watch shared configuration

[npenin]

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)

• aws_lambda_function
• aws_cloudfront_distribution
• aws_cloudwatch_log_group

Potential Terraform Configuration

resource aws_cloudwatch_global_log_group "logs"
{
  name              = "/aws/lambda/us-east-1.my-function-name"
  retention_in_days = 5
}

References

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/edge-functions-logs.html

Would you like to implement a fix?

No

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

[npenin]

another potential way to implement it would be thanks to hashicorp/terraform#24476