

The app automates the migration of the Neo4j movies graph database to Amazon Neptune. After ensuring you meet the prerequisites, follow the instructions there to run the migration.

Git clone the AWS CDK app from the GitHub repo. An Amazon Neptune DB cluster with one graph database instance.An Amazon S3 bucket from which to load data into Neptune.This instance acts both as the migration source and as a client to run AWS CLI commands, such as copying exported files to an Amazon S3 bucket and loading data into Amazon Neptune. An Amazon EC2 instance to download and install a Neo4j graph database, and Apache TinkerPop Gremlin console for querying Amazon Neptune.The app automates the creation of the following resources: The following architecture shows the building blocks that you need to build a loosely coupled app for the migration. Imports the converted data into Amazon Neptune.Converts the exported data to the bulk load CSV format in Amazon Neptune by using the neo4j-to-neptune utility.Exports the movies graph from the example project on the Neo4j website as a CSV file.Set up and configure Neo4j and Amazon Neptune databases.

The example app completes the following tasks:
#Neo4j aws how to#
This post shows you how to migrate from Neo4j to Amazon Neptune by using an example AWS CDK app that utilizes the neo4j-to-neptune command-line utility from the Neptune tools GitHub repo. You can benefit from the service’s purpose-built, high-performance, fast, scalable, and reliable graph database engine when you migrate data from your existing self-managed graph databases, such as Neo4j. Amazon Neptune is a fully managed graph database service that makes it easy to build and run applications that work with highly connected datasets.
