Fix audit log permissions using adm group (development) #221
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
log_group = admfor audit log permissionsProblem
CloudWatch agent lost access to audit logs after rotation. Previous fixes
(#215, #219) used ACLs, but auditd ignores default ACLs when creating files.
Logrotate-based solutions caused double rotation or required service restarts.
Solution
Use auditd's built-in
log_groupsetting:auditd.conf:log_group = admmax_log_file_action = rotate(auditd handles rotation)admgroup) reads via standard Unix permissionsNo ACLs, no logrotate, no race conditions.
Changes
auditd.pp: Setlog_file_group = 'adm', remove logrotate configauditd.conf.erb: Uselog_group = <%= @log_file_group %>logrotate.erbTest plan
auditd.confhaslog_group = admadm