The dynamic infrastructure framework for everybody! Distribute the workload of many different scanning tools with ease, including nmap, ffuf, masscan, nuclei, meg and many more!
whenever using axiom-scan with flags for auto creation of a fleet with static prefix and auto removal as is:
axiom-scan -m --fleet scanner --rm-when-done --spinup 5
for the first time it works great, but due to the way aws works with instances termination, if re running this command again the cli will return 2 instances id and break the axiom.
As can be observed above, the terminated yet to be deleted instances return null and interrupt the expected behavior and crashes the program later on. Subsequently the sshconfig is not properly generated and thus many of the axiom-* cli utils fail to run.
A similiar problem occurs when trying to delete such instance:
(venv) user@MacBook ~ % axiom-rm axiom-scanner\*
Deleting 'axiom-scanner01'...
i-09f9*****7a2f
i-0b4*****da56
An error occurred (InvalidInstanceID.Malformed) when calling the TerminateInstances operation: The instance ID 'i-09f9*****7a2f
i-0b4*****da56' is malformed
.
.
.
whenever using axiom-scan with flags for auto creation of a fleet with static prefix and auto removal as is: axiom-scan -m --fleet scanner --rm-when-done --spinup 5
for the first time it works great, but due to the way aws works with instances termination, if re running this command again the cli will return 2 instances id and break the axiom.
As can be observed above, the terminated yet to be deleted instances return null and interrupt the expected behavior and crashes the program later on. Subsequently the sshconfig is not properly generated and thus many of the axiom-* cli utils fail to run.
A similiar problem occurs when trying to delete such instance:
deducted some information with astrixes