Overview
This Neo4j AMI provides a fully-automated, production-ready installation of Neo4j with Docker Compose, SSL encryption, and secure domain configuration. Designed for rapid deployment, the AMI runs a first-boot workflow that validates DNS settings, provisions HTTPS certificates using Let's Encrypt, and launches the Neo4j instance with secure Bolt connectivity.
Whether you're developing a graph-based application or scaling into production, this AMI streamlines setup and reduces manual configuration. Data and logs are persisted on the host for durability and clean maintenance. Ideal for environments requiring strong security, ease of deployment, and ongoing operational stability.
Key Features
Fully automated Neo4j installation with SSL/TLS enforcement
Secure domain binding with DNS validation
Docker-based deployment for portability and version control
Persistent storage for Neo4j data and logs
Highlights
- Automated First-Boot Setup: Domain mapping, SSL generation, and container deployment handled for you.
- Secure by Default: Neo4j Bolt TLS required + Let's Encrypt HTTPS ensures encrypted communication.
- Production-Ready: Persistent data volumes, restart policies, and hands-free recovery via failsafe scripts.
Details
Unlock automation with AI agent solutions

Features and programs
Financing for AWS Marketplace purchases
Pricing
Vendor refund policy
This product is currently offered free of charge on AWS Marketplace. Since there are no fees associated with the use of this AMI, refunds are not applicable.
Buyers may cancel use of the product at any time by terminating the associated Amazon EC2 instance.
For any questions or concerns, please contact: Perimattic.com Email: aws@perimattic.comÂ
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
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
Support
Vendor support
For any assistance or inquiries, our dedicated support team is here to help 24/7. Feel free to reach out to us anytime. Email: aws@perimattic.com We are committed to providing timely and effective solutions to meet your needs.
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.