Adding code-security script, and update AWS sizing to include lambda

sullivan1337 commented 2 years ago

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate)

Types of changes

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes if appropriate.
[x] All new and existing tests passed.

tkishel commented 2 years ago

Is the counting of lambda functions due to an upcoming change of CSPM licensing or is this change for CWP? Because these scripts up do not size for CWP, and if they will now, either that lambda function count should be divided by 6 and/or broken out into a Compute summary since credit consumption for lamdba functions is not one credit per resource like CSPM resources.

tkishel commented 2 years ago

Also, could you update spec/resource-count-aws_spec.sh to include lambda function data and checks?

PaloAltoNetworks / pcs-sizing-scripts