aws-samples / aws-samples/aws-security-reference-architecture-examples
[Guidance] Inspector Findings for SRA Lambda Functions
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 303
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
**Community Note**
- Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
I've deployed the latest version of the SRA from the most recent merge and the varying add-ons from the SRA. One of which being Amazon Inspector for performing scanning of both Lambda Dependencies and Code Scanning.
When reviewing the findings in Inspector the Lambda Functions that are part of the varying accelerators within the SRA are being flagged with several different types of findings:
Could you please provide recommendations for resolving these or add to the backlog?
Thanks
Contributor guide
Research direction
Review the Amazon Inspector findings affecting the SRA Lambda functions and the accelerators mentioned in the issue. Identify the specific finding types and determine whether the expected outcome is written recommendations or backlog items; completion requires documenting an agreed resolution path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100