AWS teams struggle to govern automatically created log groups
AWS infrastructure teams have trouble managing CloudWatch log groups that services create automatically: Terraform may not be able to reference or update them reliably in the same apply, and Lambda function tags are not propagated to their log groups. That makes consistent tagging, discovery, and cleanup harder. One signal concerns retrieving serverless logs and artifacts in Azure; it is related to serverless operations but is less central to the AWS log-group management problem.
For AWS infrastructure and platform engineers. Mentioned from Nov 2021 to Mar 2025 on GitHub and Hacker News.
5 different people described this problem in 3 separate discussions.
- Indie fit
- 7.0/10
- Pain
- 6.4/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
We want to be able to easily find LogGroups corresponding to particular lambda function tags via the resource tagging API. In particular, this will allow us to easily find and delete these LogGroups when they are no longer needed
By not having this feature, it becomes very difficult to manage LogGroups within an environment
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks