aws-cloudfront: LogBucket only uses s3 legacy logging
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
Looking to expand on the CloudFront Distribution L2 to allow changes to logging. Right now it accepts a `logBucket` but there is no way to change any other settings. When passing an s3 bucket on this property it creases on CloudFront as an "S3 Legacy" type and has no option to change it.
In the console you can add as a standard S3 type and lets you change the output format among other settings. Would just like to see this supported in the L2!
### Use Case
I would like to change from using W3C format to something like JSON for easier parsing/reading.
### Proposed Solution
Add a way to toggle these settings instead of only being able to do it in the console.
### Other Information
_No response_
### Acknowledgements
- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### CDK version used
2.173.4
### Environment details (OS name and version, etc.)
typescript/node/idk
Contributor guide
Research direction
Start by locating the CloudFront Distribution L2 and its logBucket configuration, then review how CloudFront distinguishes S3 Legacy logging from standard S3 logging. Define the exposed settings needed for selectable output formats such as JSON, and verify the behavior with the relevant CloudFront tests; done means users can configure these options without using the console.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100