Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
App Runner presently creates unique log groups for each deployment event (the suffix to the service arn). This creates a few problems for us:
log group clutter, especially when deployments are frequent
lack of IaC control over data expiry
Inability to configure subscriptions during provisioning as log group names are unknown until after a deployment
Describe alternatives you've considered
The preferred solution is that a well known name is used per service (versus per deployment) such that subscriptions and configuration of the log groups is possible as part of IaC provisioning. Similar to what is presently done for both Lambda and ECS Fargate.
Community Note
Tell us about your request App Runner presently creates unique log groups for each deployment event (the suffix to the service arn). This creates a few problems for us:
Describe alternatives you've considered The preferred solution is that a well known name is used per service (versus per deployment) such that subscriptions and configuration of the log groups is possible as part of IaC provisioning. Similar to what is presently done for both Lambda and ECS Fargate.
Additional context n/a
Attachments n/a