Open edolstra opened 6 years ago
Also, it might be more sensible to have deployment.ec2.associatePublicIpAddress
default to true
.
Also also, does it ever make sense in the context of NixOps to set it to false
, given that NixOps must be able to connect to the instance? Maybe if you're deploying from within the same VPC, but that's probably not the most common scenario.
In a VPC deployment I forgot to set
deployment.ec2.associatePublicIpAddress
. Then NixOps will wait forever for a private IP address to become reachable: