-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat(S3_in_w_x_flags): Support S3 URIs for custom checks paths and whitelist files. #1090
feat(S3_in_w_x_flags): Support S3 URIs for custom checks paths and whitelist files. #1090
Conversation
Co-authored-by: Toni de la Fuente <[email protected]>
a8f91a4
to
031049b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job! Please check my comments above.
As a general comment, review variable braces {}
Co-authored-by: Toni de la Fuente <[email protected]>
031049b
to
a0f5b1f
Compare
Do we need to include required AWS S3 API permissions? |
Review the last commit with those changes pls. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉
New features!! 👏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Context
This new feature will allow users to input S3 URIs when working with whitelists (-w flag) or custom checks paths (-x flag).
Description
If an user input a S3 URI in flags -w or -x, Prowler will automatically read the files from the indicated S3 bucket.
For example:
./prowler -c extra764 -p <profile_name> -w s3://bucket/whitelist.txt
./prowler -c extra764 -p <profile_name> -x s3://bucket/checks
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.