Load balancing Neo4j community edition ami on aws is not providing any response

[daniel.picardo]

Thanks for your post!

It looks like another will probably fix the issue I am facing. Bug Report - AWS Community AMI fails when deployed to a private subnet

I think I have caused confusion by not stating what exactly the problem was. :( But unfortunately I did not know at the time what might be the cause (not that I am sure now, but kind of feels like I might finally have a handle on it)

I am using a keypair, which is how I am able to ssh into the instance. And the health checks again are probably failing because neo4j is not starting when I have only private ips and dns available (private subnet only) (again, I will check and then reply on the results)

That's one way to obtain an internet route to a resource on the private network, however you could just use the machine cname (shown as 'Public DNS IPv4 in the console).

Since it is a private subnet there is no public DNS.

No, the private IP will only be visible to other machines on the AWS network. To access the machine you should use the public CNAME, which will point to the public IP. Note that the public IP will change each time the machine is restarted, however the CNAME will always point to what it is.

If neo4j is running the load balancer should be able to access it (as you have mentioned further on in your post too). So I am thinking the problem is with Neo4j not starting up when only private ip is allocated to the instance. But you are right, I should (and will) be using the CNAME to access the instance (after setting it up against the load balancer).