Production-ready Neo4j with full root access, automated backups, and security hardening - a self-hosted graph database for knowledge graphs, recommendation engines, and network analysis on AWS.
This fully managed Neo4j solution delivers a production-ready graph database on AWS, built on Ubuntu 24.04 LTS. Every instance is pre-configured with security best practices, performance optimizations, and automated operations.
Key Features
Automated Setup and Configuration
On first login, an interactive setup script configures Neo4j with secure credentials, memory settings, and firewall rules - all within minutes.
Built-in Backup and Recovery
Pre-configured daily backups with 7-day retention. One-command restore for fast recovery.
Security Hardened
Authentication enabled by default, UFW firewall pre-configured to allow only SSH (22), HTTP (80/443), and Bolt (7687) from trusted sources, and latest security patches applied.
Performance Optimized
JVM heap, page cache, and transaction settings tuned for the selected instance type.
Use Cases
Knowledge graphs and semantic data modeling
Recommendation engines and personalization
Fraud detection and anti-money laundering
Network and IT infrastructure mapping
Identity and access management graphs
Supply chain optimization and logistics
Getting Started
Launch the AMI from AWS Marketplace on your preferred instance type
SSH into your instance and follow the interactive setup wizard
Access Neo4j Browser, create your graph, and start querying with Cypher
Support
Managed and supported by Perimattic, a cloud infrastructure company with 13+ years of experience serving global clients. We offer free setup assistance, custom integrations, infrastructure consulting, and 24/7 support.
Highlights
Full Root Access Graph Database: get complete OS-level control to configure plugins, APOC procedures, graph algorithms, and JVM settings without per-node pricing.
Automated Daily Backups with 7-Day Retention: Pre-configured backups with auto-purge and one-command restore for fast recovery of your graph data.
24/7 Expert Support by Perimattic: 13+ years of cloud infrastructure expertise with free setup assistance, graph modeling guidance, and dedicated support at aws-support@perimattic.com.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
You pay by the hour based on the EC2 instance size you run for this managed graph database. The eight options split into two families. The t2 and t3 dimensions cover burstable general-purpose instances in medium, large, and xlarge sizes. The m5 dimensions cover fixed general-purpose instances in large and xlarge sizes. Within each family, moving from medium to large to xlarge adds more compute and memory, so your hourly rate scales with the size you select. You choose one instance size to match your workload.
Top-of-mind questions for buyers
What resources do I get for the hourly rate on each instance size?
You get a managed Neo4j graph database running on a single EC2 instance of the size you pick. The vendor handles provisioning, networking, SSL, monitoring, backups, and security patches. Larger sizes add more CPU and memory. Your hourly rate covers both the managed service and the underlying compute.
Am I charged when the instance is stopped or paused?
The software meters running instance-hours, so charges apply while the instance runs. A stopped instance stops accruing hourly software charges. Note that underlying AWS storage tied to a stopped instance may still incur AWS fees separate from this hourly rate.
How do the t2, t3, and m5 instance families differ for billing?
You pick one instance size and pay its hourly rate. The t2 and t3 dimensions are burstable general-purpose instances, which vary performance based on workload. The m5 dimensions run fixed general-purpose performance. Each family and size carries its own hourly rate, so your choice sets your cost.
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Initial release of a production-ready Neo4j deployment on AWS.
Fully automated first-boot configuration for domain binding and SSL setup.
Docker Compose containerization of Neo4j for consistent and maintainable operations.
Mandatory HTTPS with automated Let's Encrypt certificate provisioning.
Enforced Bolt TLS security for encrypted database transactions.
Persistent data and logs mapped to host storage for durability and easy backups.
Simplified environment configuration via .env for domain, admin email, and credentials.
Built-in DNS validation workflow to prevent misconfiguration.
Failsafe logic enabling restart/recovery of setup steps on interruption.
Compatibility with a wide range of EC2 instance types for flexible scaling.
Additional details
Usage instructions
Launch an Instance
From AWS Marketplace, click Continue to Subscribe, then Continue to Configuration, and launch the AMI.
Choose the Recommended Instance Type
Select t2.medium or higher for smooth Neo4j deployment and UI performance.
Neo4j requires adequate CPU and RAM - larger instance types significantly improve query performance, Bolt traffic, and graph exploration via Neo4j Browser.
Configure Security Group
Allow inbound traffic on the following ports:
22 (SSH) - For secure terminal access
80 (HTTP) - Required temporarily for SSL validation
443 (HTTPS) - To securely access the InfluxDB UI
7687 (TCP) - Neo4j Bolt protocol
Connect to the Instance
ssh -i <your-key.pem> ubuntu@<public-ip>
First-Boot Setup
On first boot, the AMI automatically launches an interactive guided setup:
Detects the public IP address of the server
Prompts for the domain name to map to your Neo4j instance
Validates DNS and A-record propagation
Asks for the admin email (for SSL certificate issuance)
Generates a secure Neo4j admin password
Stores credentials in /opt/app/.env
Configures Apache reverse proxy for HTTPS access
Requests and installs a Let's Encrypt SSL certificate
Deploys Neo4j using Docker Compose
Enforces Bolt TLS for all encrypted database communications
Displays the HTTPS URL and generated password after completion
Once completed, Neo4j becomes fully accessible over HTTPS.
Configure DNS
Before (or during) the setup script, add this DNS A-record in your domain provider:
yourdomain.com <your-instance-public-IP>
Setup will proceed only when DNS resolves correctly across multiple global resolvers.
Automatic SSL Setup
After DNS mapping is verified:
A free SSL certificate is issued using Let's Encrypt
HTTPS is enabled in Apache and used as the primary access
Neo4j Browser and Bolt traffic are secured with TLS encryption
Plain HTTP access is disabled for security
Start or Restart Neo4j Manually (if needed)
cd /opt/app
docker compose ps
docker compose restart
Access the Neo4j Browser UI
Open your browser and visit:
https://<your-domain>
Use the following credentials (shown after setup and stored in .env):
Username: neo4j
Password: <generated-password>
Login Credentials
Your credentials are stored here:
cat /opt/app/.env
What We Help With:
Initial setup and configuration assistance (free)
Troubleshooting connectivity, performance, and backup issues
Custom development and integrations
Infrastructure consulting and architecture review
Migration planning from other solutions
Automation solutions and scaling guidance
Instance Sizing Guidance:
t2.medium or t3.medium: Development environments, small applications
m5.large: Production workloads with moderate traffic
m5.xlarge: High-traffic production deployments and larger datasets
For workload-specific sizing recommendations, contact our team for a free consultation.
Refunds and Issues:
If you experience any issues or need to request a refund, contact us at aws-support@perimattic.com and we will respond promptly.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Production-ready Neo4j with full root access, automated backups, and security hardening - a self-hosted graph database for knowledge graphs, recommendation engines, and network analysis on AWS.
Production-ready Neo4j with full root access, automated backups, and security hardening - a self-hosted graph database for knowledge graphs, recommendation engines, and network analysis on AWS.
Production-ready ClickHouse with full root access, automated backups, and security hardening - a high-performance columnar database for real-time analytics on AWS.
Production-ready ClickHouse with full root access, automated backups, and security hardening - a high-performance columnar database for real-time analytics on AWS.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.