The nomad auto join demo here:
set advertise_addr_wan to the PUBLIC IP of the ec2 instance here:
I’m still learning all of this, but my best understanding of the broader configuration is that Consul uses the WAN address in this scenario because the consul/nomad servers are spanning multiple AZs and therefore subnets. So, Consul needs the public IP in order to automatically form a cluster.
I wanted to remove the Public IP from these severs because the services they all run have no need for any inbound traffic from the outside world and that seems more secure, but then (obviously) the consul cluster formation immediately fell over.
My Question:
Is this public IP required in order for Consul to form a cluster in this type of (autojoining) setup? Or, in other words, is this public IP the tradeoff that allows autojoining across AZs to work?
Sub Question
If I did away with this autojoin luxury is it possible to have Consul form a cluster across multiple AZs without the public IP somehow? Or is that always required?