Encode s3 bucket access log format into Terraform #227
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.
We recently had some confusion around the "log object key format" that is set for access logging of our S3 buckets. Due to it being modified directly in the AWS console instead of through a PR to this repo, it went unnoticed for some time. It turns out that, until recently, the AWS Terraform module didn't support configuring this setting anyway. This PR adds configuration for the log object key format.
Support for specifying the log object key format was added in AWS provider v6 (we are on v5), so this PR is dependent on/based off of #236.