To execute subfinder, we require a "$HOME/.config/" directory. Creating "/home/sbx_user1051/.config/" does not help since this filesystem becomes read-only once the lambda is started. Only "/tmp" is writable in AWS lambdas.
Finally, the chmod command is necessary because the "/tmp/.config" directory is created as root. Using chown is not possible, as it would break multi-cloud compatibility, since the end user is surely not the same on AWS, Google, and Azure.
Once your image is deployed, you can test subfinder using the command below:
fyoorer
commented
1 year ago
Hi,
To execute subfinder, we require a "$HOME/.config/" directory. Creating "/home/sbx_user1051/.config/" does not help since this filesystem becomes read-only once the lambda is started. Only "/tmp" is writable in AWS lambdas.
Finally, the chmod command is necessary because the "/tmp/.config" directory is created as root. Using chown is not possible, as it would break multi-cloud compatibility, since the end user is surely not the same on AWS, Google, and Azure.
Once your image is deployed, you can test subfinder using the command below:
python shadowclone.py -i domains.txt -s 3 -c "/go/bin/subfinder -dL {INPUT}" -o subf.txt
PS : I tested this configuration using python 3.11.