-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: CloudTrail Object-level logging #119
feat: CloudTrail Object-level logging #119
Conversation
make it so! (comment trigger for tests) |
@dmurray-lacework Any chance we could get some eyes on this for review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to update the Readme docs with terraform-docs markdown
https://github.com/terraform-docs/terraform-docs/
We also require a new example in examples/
directory with the enable_cloudtrail_s3_management_events
field being used.
The ci_tests.sh
needs updated with the new example in the TEST_CASES block.
@TIYZAP Nicely done! 🎉 CI: make it so... |
@dmurray-lacework @afiune What's the ETA on a new release being created in order for this addition to be utilized? |
@TIYZAP it has been released! |
Summary
Currently the
terraform-aws-cloudtrail
module does not contain support for Object-level logging, specifically the ability to add anevent_selector
in order to enable said logging.This need for this functionality originated from the following policies;
lacework-global-80 (Ensure that Object-level logging for write events is enabled for S3 buckets)
lacework-global-81 (Ensure that Object-level logging for read events is enabled for S3 buckets)
Added a dynamic block which can be enabled / disabled based on an associated variable.
Added a additional variable
How did you test this change?
Swapped the
source
to my local path and ran aterraform init
against one of our environments. Modules initialized cleanly.Issue
N/A