August 16, 2012 | Neo4j
It’s been more than a year now since I rolled out Neo4j Graph Database Server image in Amazon EC2.
In May 2011 the version of Neo4j was 1.3 and just recently guys at Neo Technology published version 1.7.2 so I thought now is the time to revisit this exercise and make fresh AMIs available.
Last year I created Neo4j AMI manually in one region then copied it across to the remaining AWS regions. Due to the size of the AMI and the latency between regions this process was slow.
I started to use Puppet in the past year to automate deployment processes for some of our customers. It made sense then to automate the Neo4j deployment process using a collection of Puppet manifests. Here are some of the benefits of this approach
To pull the manifests from Github run: git clone https://github.com/opencredo/neo4j-puppet.git
If you would like to connect a Neo4j instance from outside of AWS, you should create a Security Group that allows connectivity on port 7474 as well as on port 22 for SSH.
You need to associate this group with the instance at instance launch time. Security Group configuration steps can be found here.
Neo4j-puppet module deploys the JRE from the OpenJDK package instead of the JDK distributed by Oracle.
To install a different version of the JRE you can change the value of the variable $jreinstaller in the file params.pp prior to deployment.
The file params.pp also contains a variable $neoversion that can be used to specify the version of Neo4j that is to be installed.
Currently the Puppet module cannot be used to upgrade existing Neo4j server; it can only be used for fresh deployments.
The Neo4j AMI can be found by searching for “Neo4j 1.7.2 CE Ubuntu 12.04 64-bit” in AWS console.
Alternatively you can use the following hyperlinks to launch Neo4j image in specific region.
This blog is written exclusively by the OpenCredo team. We do not accept external contributions.