Support an S3 bucket in a different account #245
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.
Allow principals in the S3 bucket's account to use the KMS Key to decrypt logs.
S3 itself cannot tell us which account an arbitrary bucket is in, so the caller must provide it.
Useful when using an Organization CloudTrail and a dedicated AWS account for logs, as recommended by AWS Multi-account strategy.
Fixes #240
logs encrypted with other aws account cmk
Changes proposed in this pull request: