Allow for viewing CloudFront's CloudWatch Logs
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 807
- Avg merge
- 10h 12m
- Merged PRs (30d)
- 7
Description
**Is your feature request related to a problem? Please describe.**
It is not related to a problem. In fact, the plugin is working as expected but when working with Lambda@edge functions, the relating CloudWatch log files may be stored in different regions.
**Describe the solution you'd like**
It would be incredibly useful for debugging reasons to have "CloudFront Logs" which could be structured similarly to "CloudWatch Logs" but it simply would be an aggregation of all of the CloudFront logs through all regions that contain CloudFront logs compared to the one your AWS account has currently selected.
**Describe alternatives you've considered**
The only alternative at the moment is searching for those log files manually. This flow requires you to leave the editor and it would be nice if you could stay completely inside it.
**Additional context**

(just adding the screenshot for reference of what section I am addressing)
In terms of how I would structure the UI aspect, I likely would choose to nest the CloudFront logs as follows:
CloudWatch Logs > CloudFront Logs > Regions
Would love to hear if others would find this a useful and logical addition.
Contributor guide
Research direction
Start by locating the existing CloudWatch Logs view in the aws-toolkit-vscode extension and tracing how it discovers log files for the selected region. Compare that flow with the requested CloudFront Logs grouping by regions. Done means CloudFront logs from all relevant regions are browsable inside the editor without manual searching.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript, vscode
- Domain
- cloud, devtools, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100