Developer Guides Getting Started Getting Started What is a Graph Database? Intro to Graph DBs Video Series Concepts: RDBMS to Graph Concepts: NoSQL to Graph Getting Started Resources Neo4j Graph Platform Graph Platform Overview Neo4j Desktop Intro Neo4j Browser Intro… Read more →
Hosting Neo4j on Microsoft Azure
This guide explains how to deploy a single instance of Neo4j Enterprise on Microsoft Azure.
You should know how to run and operate Neo4j locally. Knowledge of remote drivers to access Neo4j from your application helps you connect to your cloud-hosted database.
Before continuing with the guide make sure you’ve installed the Azure Command Line Interface.
Let’s get started!
Navigate to this Marketplace entry in the link above, and click “Get it Now”. The Marketplace will prompt you to click “Continue” after providing some basic version and publisher information. Click “Continue”.
On the next screen, Azure will inform you that this offering is a “Bring Your Own License” offering. If you are an existing Neo4j customer, you already have a license. If you need an evaluation license, you can obtain one here.
Click the “Create” button.
On the next page, fill out all of the details for the VM you want to create. The most important settings to consider are Size, which controls the available CPU and memory, and optionally “Disks” where you can configure high speed SSDs and larger disk capacity sizes.
In general, we recommend deploying an instance into a new Azure resource group. The wizard will allow you to choose a new name, and the resource group will be created as part of the deploy process.
You will be required to configure administrator access, which you can do either with a password or an SSH public key.
When your settings are just as you want them, click the “Review + Create” tab, and then finally the “Create” button at the bottom of the screen.
After you click “Create”, Azure will create a deployment for your new instance. You can watch the progress of that deployment as it goes. All firewall rules necessary will be created for you, so unless you have custom requirements, you won’t need to change anything.
After your deployment succeeds, it may take a minute or two for the Neo4j service to come up.
Navigate to the resource group that you used, and locate the VM you created. It will be named after the name you chose in the initial configuration step. Locate the VM’s IP address and then use your browser to connect to Neo4j via:
The default username/password for your instance is neo4j/neo4j, and Neo4j will force you to change it on your first login. Make sure to change this password right after deployment.
Because you don’t have a hostname configured or a valid SSL certificate by default, your browser will warn you that the certificate isn’t trusted. This is expected, you can configure a certificate later if you choose.
Bolt clients may connect to this same IP address on port 7687 as normal.
You can use any SSH client as normal to connect to the public IP of your instance. Use the administrative user credentials (password or SSH key) configured during the launch. This user will have sudo access on the machine.
Inside of the VM, you can check the status of the neo4j service like this:
Please consult Neo4j Cloud VMs for details on internals of Azure VMs, including how to stop and start system services, configure Neo4j inside of the VM, and more.
When you’re finished with the instance, if you chose to deploy into a new resource group, simply delete the entire resource group and everything will be removed for you. If you deployed into an existing resource group, you will need to delete the resources that are part of the deployment individually.
You can ask questions and connect with other people launching Neo4j in the cloud at the cloud topic on the Community Site.