Ah, that means you don’t have the aws CLI installed. The script is actually supposed to fail if you don’t have that installed, so I’m not sure that part is working correctly.
You can install it using pip, either in a virtualenv or not. A virtualenv is a way you can install it without root access and it provides isolation for all the Python dependencies, so you don’t end up with conflicting libraries if you install system wide.
Im trying to get it all to talk to each other locally before approaching you to discuss how best to host this. Im having reasonable success with Docker so looking at DO Kubernetes instances looks like a logical next step.
Bit distracted past few days, got an unexpected funeral to go to tomorrow so I’ll check in again in time for the Thursday update
From the other thread I mentioned that in the past I could start genesis and then add new nodes one by one until there were enough to be a functional network.
I am trying to do that now but it is not working anymore, has something changed that would cause that.
The now, no longer in play scenario was that I wanted to then gain control of any nodes that I created from within the tool.
I’m not completely sure about this off the top of my head, but I think if you wanted new Droplets to come online, you can increase the size of the Droplet count, then run Terraform again, and it’ll bring new Droplets online.
For Droplets that were created outside the tool that you would want to participate in an existing network, I’m not entirely sure if we should handle that within sn_testnet_tool. It would be possible to use Terraform’s data sources for that, but it might be easier to just let those nodes join the network using safe.