The FAAS scripts don't replace cadofactor.py. They're intended to spin up a bunch of ec2 instances, configure them, and then call cadofactor.py on them with parameters optimal for that size of cluster. The CADO-NFS guys were super helpful in this process.
Unfortunately StarCluster is currently out of date, and I ran into a bunch of difficulties adapting things to c4.8xlarge instances that don't seem to work out of the box anymore. That and random ec2 volatility were the source of most of the necessary handholding.
If someone has a suggestion for a lighter weight replacement for StarCluster, that would be great.
Sharon Goldberg: Attacking the Network Time Protocol: https://eprint.iacr.org/2015/1020
Miro Haller: MEGA: Malleable Encryption Goes Awry: https://mega-awry.io/
Nadia Heninger: Mining your Ps and Qs: https://factorable.net/
Dan Shumow: On the Possibility of a Back Door in the NIST SP800-90 Dual EC PRNG: https://rump2007.cr.yp.to/15-shumow.pdf
Marc Stevens: MD5 considered harmful today: https://www.win.tue.nl/hashclash/rogue-ca/
Adam Suhl: On the Possibility of a Backdoor in the Micali-Schnorr Generator: https://eprint.iacr.org/2023/440