Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dramatically cut RAM usage when performing typical filtering by ARN. #732

Merged
merged 4 commits into from
Mar 16, 2025

Conversation

anonymous-work-156
Copy link
Contributor

By using a generator function instead of loading all events into RAM, memory usage is cut significantly when scanning significant numbers of events. This is useful to find less-used IAM roles inside busy trails.

@flosell flosell merged commit 8bb826b into flosell:master Mar 16, 2025
9 checks passed
@flosell
Copy link
Owner

flosell commented Mar 16, 2025

Thank you for the contribution @anonymous-work-156 - merged and released

@anonymous-work-156
Copy link
Contributor Author

Happy to contribute.

I've also made other changes on my fork which might be of interest, but as it stands I don't have a comprehensive test env, so it would be some extra work for you. Wildcard matching of select target, selecting of either user or role, sorting select results, then into parallel processing (relevant for locally cached events). I have also been exploring generation of additional resource ARNs which are not stated explicitly in events.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants