pull down to refresh
Agreed! I would go further and suggest that the signer machine should be domiciled in your home/office/citadel/bunker/spacestation. In general, securing your own devices physically is something ordinary human beings can reason about more easily, than securing things in a remote server (even if you already trust the remote rack operator).
Regardless, even separating it out into an AWS Nitro enclave while running the node software in the hosting ECS instance would still improve your security in practice, as it at least makes it somewhat harder to exfiltrate your keys for anyone not named "Amazon".
The thing you have to balance here is that obviously if you are running the signer in your home Internet connection then the latency from your home Internet connection to the node machine is added on to every signing event. That is why we also have alternate deployments like running on an STM32 that is connected to the USB port of the node machine, which reduces that latency, and the new proof-of-concept work done by Vatsal to run it in AWS Nitro.
Just to emphasize, we recommend keeping the signer on a separate device from the Lightning node. Running both the node and signer on same device removes much of the benefit, since compromising the device could expose the signing key.