Configure single s3 bucket for logs #15
Merged
Conversation
This file contains hidden or 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
Member
Stretch96
commented
Apr 15, 2022
Stretch96
commented
- Cloudfront logs go into '/cloudfront/*'
- S3 logs go into '/s3/*'
- Reduces the amount of s3 buckets required
Stretch96
force-pushed
the
configure-single-s3-bucket-for-logs
branch
2 times, most recently
from
c2d03eb to
5006719
Compare
* Cloudfront logs go into '/cloudfront/*' * S3 logs go into '/s3/*' * Reduces the amount of s3 buckets required
Stretch96
force-pushed
the
configure-single-s3-bucket-for-logs
branch
from
5006719 to
630c248
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.