Currently, what I have been seeing from many folks around the Nuclei integration is that nuclei in this tool are meant for a single (or maybe 2-3 checks) at most, given the short amount of time a Lambda could run. I am wondering if there is a way to flip this on its head like so:
python3 shadowclone.py -i ~/nuclei-templates/* -o /tmp/output -s `for i in ($ls ~/nuclei-templates/**/*.yaml | wc -l) -c "nuclei -duc -l www.static-site.org -t {INPUT}
In the case above, each of the Nuclei YAML files could be uploaded to the Lambda; I'm not sure if "streaming" would work in this way, however instead of sending each URL to lambda with a static nuclei, could we send a file (the nuclei YAML) with a static URL as a way to distribute the checks across 20,000 lambdas? I know it's a bit of an ask. I've tried to work this out. However, this could be 20,000 invocations (or 40,000) vs 1 invocation per URL per check.
Currently, what I have been seeing from many folks around the Nuclei integration is that nuclei in this tool are meant for a single (or maybe 2-3 checks) at most, given the short amount of time a Lambda could run. I am wondering if there is a way to flip this on its head like so:
In the case above, each of the Nuclei YAML files could be uploaded to the Lambda; I'm not sure if "streaming" would work in this way, however instead of sending each URL to lambda with a static nuclei, could we send a file (the nuclei YAML) with a static URL as a way to distribute the checks across 20,000 lambdas? I know it's a bit of an ask. I've tried to work this out. However, this could be 20,000 invocations (or 40,000) vs 1 invocation per URL per check.