Update configuration for the logging bucket. #986
Merged
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.
Issue #, if available:
Fixes #985
Description of changes:
Update configuration for the logging bucket:
AES256
instead of the currentSSE-KMS
setting for the log bucket; see considerations on the default bucket encryption on the target bucket withAES256
(SSE-S3
) in Enabling Amazon S3 server access logging (where I note: You can use default bucket encryption on the target bucket only if you use AES256 (SSE-S3). Default encryption with AWS KMS keys (SSE-KMS) is not supported). I started to see logs in my logs bucket after I changed toAES256
the default bucket encryption for the log bucket itself.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.