AWS Linux admins can't ship journald logs to CloudWatch directly
AWS operators running Linux systems that use journald want service and boot logs in CloudWatch, but the CloudWatch agent requests in these reports say the agent does not read the journal directly. They resort to forwarding logs through syslog or using another collector such as Vector, adding configuration or a workaround—especially on fresh Amazon Linux 2023 deployments. The evidence is repeated requests for this integration, not a measure of market size.
For AWS Linux administrators. Mentioned from Feb 2022 to Nov 2024 on GitHub and Hacker News.
5 different people described this problem in 2 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.0/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.
It's incredible that this isn't solved for a fresh AL2023 and I need to use syslog or change systemd files. What's the point of removing syslog if the new solution can't be integrated with cloudwatch agent?
I would've thought this would be very important feature for the agent; would think one of the most common use cases is someone spinning up an ec2 instance (now AL3 which uses only default journald) and wanting to easily get logs into CW
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