Lamda: Attack wave detection & proxy event v2

[timokoessler]

Summary by Aikido

Security Issues: 0	🔍 Quality Issues: 2	Resolved Issues: 0

🚀 New Features

• Introduced API Gateway v1/v2 parsing and improved SQS JSON parsing.

⚡ Enhancements

• Added attack wave detection in wrappers, triggered agent notifications.

^{More info}

[aikido-pr-checks]

New nested attack-wave detection increases nesting in incrementStatsAndDiscoverAPISpec; consider a guard/early return or extracting the detection to flatten the logic.

Details

✨ AI Reasoning
​A new inner conditional for attack-wave detection was added inside an existing guarded block, increasing nesting and hiding side-effects. Flattening with an early return/guard or extracting detection into its own guard would improve readability and maintainability.

🔧 How do I fix it?
Place parameter validation and guard clauses at the function start. Use early returns to reduce nesting levels and improve readability.

_{Reply @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.
Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info}

[aikido-pr-checks]

Inserted attack-wave detection inside the gateway-event branch increases nesting in incrementStatsAndDiscoverAPISpec; consider a guard/early return or extracting detection to reduce nesting.

Details

✨ AI Reasoning
​Attack-wave detection code was inserted inside the existing gateway-event guarded block, creating deeper nesting and mixing detection side-effects with route discovery. Using an early guard, extracting the detection, or inverting conditions would make the function clearer.

🔧 How do I fix it?
Place parameter validation and guard clauses at the function start. Use early returns to reduce nesting levels and improve readability.

_{Reply @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.
Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info}