Neo4j on GCP
You can deploy a Neo4j cluster via the GCP Marketplace.
Deploy Neo4j via the GCP Marketplace
Deploy Neo4j Enterprise from the Google Cloud Launcher console following the interactive prompts.
Start using Neo4j Browser
Use your web browser to access the cloud-based database URL, and log in with the initial username
neo4j and password you specified during the configuration stage.
The GCP console advises when the deployment is complete. However, you need to wait another few minutes for the Neo4j deployment to complete on the GCP Virtual Machines before the Neo4j Browser is available. Depending on the deployment options selected, this can take more than 5 minutes.
The Cypher command
SHOW SERVERS displays all current servers running in the cluster, including both servers yet to be enabled (i.e. servers in the
Free state) in the DBMS as well as dropped servers.
Access your instance via SSH
You can access the deployed GCP Compute Engine Virtual Machines via SSH from the Deployment Manager screen, or by running the following command in the Google Cloud CLI:
gcloud compute ssh my-cluster-deploy-vm-1
Your cluster default configuration
The following notes are provided on your default cluster configuration.
7473(HTTPS access) are the only ports exposed to the entire internet. Consider narrowing the access to these ports to only your needed networks. External unencrypted HTTP access is disabled by default.
7000are enabled only for internal network access (
10.0.0.8), between the cluster nodes.
Because cloud VMs can start and stop with different IP addresses, the configuration of these VMs is driven by a file in /etc/neo4j/neo4j.template. Configuration changes must be made to the template, not to the /etc/neo4j/neo4j.conf file, which is overwritten with the template substitutions at every startup. The template allows you to configure aspects of the cluster with the VMs metadata. The template’s behavior and layout match the usual neo4j.conf file.
Visit Clustering for more information on how to configure your cluster.
Add users and change passwords as necessary.
Consider creating DNS entries with Google to be able to address your cluster with client applications under a single hostname.
Terminating the deployment
You can use the deployment manager to delete the deployment. To ensure data safety, the disks that back the VMs are not removed when you delete the cluster deployment.
Was this page helpful?