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

Convert All PE Scans to Utilize SQS #55

Open
4 tasks
arng4108 opened this issue Jan 14, 2025 · 0 comments
Open
4 tasks

Convert All PE Scans to Utilize SQS #55

arng4108 opened this issue Jan 14, 2025 · 0 comments
Assignees
Labels
improvement This issue or pull request will add or improve functionality, maintainability, or ease of use

Comments

@arng4108
Copy link

💡 Summary

Currently, a few of the PE Report scans utilize SQS parallelization for increased performance. We need to apply this SQS parallelization to the rest of the scans as well.

Motivation and context

We may need to scale our operations in the near future. As a result, we need to prepare our code to be able to generate increasingly large numbers of reports and not take forever to execute.

Implementation notes

  • Scans need to be reconfigured to be able to run on a specified list orgs
  • Scans need to be easily callable via command line
  • Scans need to be able to support a dynamic number of available API keys

Acceptance criteria

  • Identify which scans need to be updated for SQS
  • Implement SQS versions of scans
  • Test SQS scans to ensure everything is still working properly
  • Stress test SQS scans to ensure no APIs/infrastructure is being overloaded
@arng4108 arng4108 added the improvement This issue or pull request will add or improve functionality, maintainability, or ease of use label Jan 14, 2025
@arng4108 arng4108 self-assigned this Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement This issue or pull request will add or improve functionality, maintainability, or ease of use
Projects
None yet
Development

No branches or pull requests

1 participant