Running Neo4j Graph Databases on AWS May 2017
© 2017, Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether express or implied. This document does not create any warranties, representations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers.
Contents Introduction 1 Transacting with the Graph 1 Deployment Patterns for Neo4j on AWS 2 Basics 3 Networking 3 Clustering 5 Database Storage Considerations 10 Operations 15 Disaster Recovery 19 Conclusion 20 Contributors 20 Further Reading 21 Notes 21
Abstract Amazon Web Services (AWS) is a flexible, cost-effective, and easy-to-use cloud computing platform. Neo4j is the leading NoSQL graph database that is widely deployed in the AWS Cloud. Running your own Neo4j deployment on Amazon Elastic Compute Cloud (Amazon EC2) is a great solution for users whose applications require high-performance operations on large datasets. This whitepaper provides an overview of Neo4j and its implementation on the AWS Cloud. It also discusses best practices and implementation characteristics such as performance, durability, cost optimization, and security.