feat(s3): Allow separate logging bucket for AWS Config #137
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
omnibrian
force-pushed
the
feat/aws-config-separate-bucket
branch
from
09ac7b4
to
48153a8
Compare
For the case where the central logs bucket has Object Lock enabled, AWS Config does not support logging directly to the central logs bucket. A workaround for that issue is to create a separate bucket without Object Lock enabled and replicate everything over to the central logs bucket. This change adds the option to create that separate bucket with a replication rule into the central logs bucket and repointing AWS Config to use that separate bucket instead.
omnibrian
force-pushed
the
feat/aws-config-separate-bucket
branch
from
48153a8
to
aabb331
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
Description of changes:
For the case where the central logs bucket has Object Lock enabled, AWS Config does not support logging directly to the central logs bucket. A workaround for that issue is to create a separate bucket without Object Lock enabled and replicate everything over to the central logs bucket. This change adds the option to create that separate bucket with a replication rule into the central logs bucket and repointing AWS Config to use that separate bucket instead.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.