Fix CloudWatch agent binary log files and startup issues #216
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Details
Binary log files removed
btmpandwtmpare binary files in utmp format that CloudWatch agent cannot parse as text logs, resulting in garbled data in log streams. Authentication data is already captured inauth.login a parseable format, so these files are redundant.Agent startup fix
Removed the
-sflag fromamazon-cloudwatch-agent-ctlcommand and addednotify => Service[...]to ensure the agent starts via systemd. This fixes an issue where the agent process would start without supplementary groups (likeadm) because the-sflag bypasses systemd's group resolution.Cleanup
utmpgroup from cwagent user (no longer needed without btmp/wtmp)DiskSpaceUsedmetric from sandbox environmentTest plan
cat /proc/$(pgrep -f amazon-cloudwatch)/status | grep Groups