This chapter describes how Neo4j deployed on cloud virtual machines operate and how they differ from other installation platforms for Neo4j.
Neo4j cloud VMs are based on the Ubuntu distribution of Linux.
When Neo4j is installed on a VM, the method used to do this matches the Debian install instructions provided in the Section 2.3.1, “Debian”.
Because cloud images are based on the standard Neo4j Debian package, file locations match the file locations described in
the Section 5.2, “File locations”, where
neo4j-home is set to /var/lib/neo4j.
The remainder of this page deals only with topics that are different from a standard Linux install.
If you have any other questions not covered by this page, consult Section 2.3, “Linux installation”.
For the cloud version of Neo4j, you must not modify the /etc/neo4j/neo4j.conf file directly, but rather modify /etc/neo4j/neo4j.template.
The system service that restarts Neo4j calls a shell script called pre-neo4j.sh.
In cloud environments, much of the external configuration environment may change. A machine may have a different IP address or a different set of tags when it restarts. Because of this dynamic nature, the pre-neo4j.sh script dynamically overwrites the normal neo4j.conf file each time the system service starts. As a result, you must configure the template to do those substitutions and not the configuration file itself, as it will be automatically overwritten.
You can get system status for
neo4j within the VM by executing the following:
systemctl status neo4j