Skip to content
Neo4j Graph Database product logo
  • AWS· soonComing soon on Amazon Web Services
  • Azure· nextMicrosoft Azure is next on the roadmap
  • GCP· nextGoogle Cloud is next on the roadmap
Coming soon

Neo4j Graph Database

Neo4j Community 2026.08.1 - the current stable release - with cypher-shell, on Ubuntu 24.04 LTS. Neo4j Browser and Bolt are ready the moment the instance boots, with your credential staged before any port opens so the very first connection is already yours. Heap and page cache auto-size to whatever instance type you launch.

Version
v2026.08.1
Operating system
Ubuntu 24.04 LTS
Architecture
x86_64
Support
Community

What's installed

Every package and version on the image. Nothing else is installed.

  • Neo4j Community 2026.08.1
  • cypher-shell 2026.08.1
  • OpenJDK 21.0.12 JRE

Licensing — Neo4j Community Edition (GPL-3.0), no licence key required

Deploy anywhere

Neo4j Graph Database on AWS.

Microsoft Azure and Google Cloud are next on the roadmap. One clean-room build, one first-boot credential model, one patch cadence — identical on every cloud you run. Every identifier below is the real one; copy it and launch.

  1. AWS

    Amazon Web Services

    AMI · v2026.08.1

    Coming soon

    AWS AMI ID

    ami-08b633e4c88e77301
    Released
    September 12, 2026
    Root volume
    gp3 · 30 GiB

    Instance types

    • t3a.medium
    • t3.medium
    • t3a.large
    • m6a.large

    Regions

    • us-east-1
    AWS launch steps

Getting started

From launch to signed in, step by step.

  1. Launch in us-east-1 with TCP 22, 7474 and 7687 open; wait for the health checks to pass.

  2. Open http://<instance-public-ip>:7474 for Neo4j Browser and sign in with username neo4j and your EC2 Instance ID as the password, exactly as the console shows it (for example i-0123456789abcdef0).

  3. Drivers connect at bolt://<instance-public-ip>:7687 with the same credentials. HTTPS on 7473 is off by design; put TLS in front for production.

  4. SSH as ubuntu with your key pair. Change the password with sudo bash /home/ubuntu/iscripts/pass_neo4j.sh; neo4j_status.sh prints version, service state, sockets and your URLs.

  5. Open 7474 and 7687 only to the addresses that need them.

Security posture

What this image does and does not ship with, one fact per line.

  • Clean-room build on Canonical's official Ubuntu 24.04 LTS image: every component comes from its own official repository or release, nothing is copied from any third-party image, and the finished image was scanned for third-party vendor strings before capture.

  • No usable credential ships in the image; passwords are set on your instance at first boot from EC2 instance metadata (IMDSv2) and the scripts that set them delete themselves afterwards.

  • SSH is key-only, root login over SSH is refused, and build-time SSH keys, shell history and logs were removed before imaging.

  • The published image contains no Neo4j system database and no password: provencloud-neo4j-firstboot.service runs Before=neo4j.service, reads the Instance ID from IMDS and calls neo4j-admin set-initial-password before a single port opens, which removes the window in which a build-time password could be accepted.

  • A second, idempotent first-boot pass confirms the credential and repairs it if IMDS was slow, without ever touching users you created in the meantime.

  • Packages come from Neo4j's own signed apt repository.

  • Bolt and HTTP are the only listeners; open 7474 and 7687 only to the addresses that need them.

  • The bundled password tools enforce at least 10 characters with upper- and lower-case letters, a number and a symbol, and verify the new credential with a real sign-in before reporting success.

  • The image is HTTP-only by design so it works at a bare IP with no certificate warnings: terminate TLS at a load balancer or add a certificate before exposing it publicly, and restrict port 22 and any admin ports to trusted IP ranges in your security group.