Skip to content
Grafana with Prometheus and Node Exporter 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

Grafana with Prometheus and Node Exporter

Grafana 13.2.1 with Prometheus 3.14.0 and Node Exporter, wired together so the instance shows real host metrics the moment you sign in. Prometheus is already Grafana's default data source and a ten-panel host dashboard is pre-loaded. Each service runs under its own hardened account, and every instance gets its own Grafana encryption key on first boot.

Version
v13.2.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.

  • Grafana OSS 13.2.1
  • Prometheus 3.14.0
  • Node Exporter 1.12.1

Licensing — Open source (AGPL-3.0), no licence key required

Deploy anywhere

Grafana with Prometheus and Node Exporter 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 · v13.2.1

    Coming soon

    AWS AMI ID

    ami-05ce8d9b713f70997
    Released
    September 12, 2026
    Root volume
    gp3 · 20 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, 3000 and 9090 open; wait two to three minutes for first boot.

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

  3. The ProvenCloud Node Overview dashboard is in the ProvenCloud folder. Prometheus is at http://<instance-public-ip>:9090.

  4. Add your own scrape targets in /etc/prometheus/prometheus.yml, validate with promtool check config, then curl -X POST http://localhost:9090/-/reload.

  5. SSH as ubuntu with your key pair. Change the Grafana password with sudo bash /home/ubuntu/iscripts/pass_grafana.sh; run grafana-status for a one-screen health view.

  6. Prometheus on 9090 has no authentication. Restrict it in your security group if the instance is internet-facing.

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.

  • Every instance generates its own 48-character Grafana secret_key on first boot, replacing the documented default that is identical on every Grafana installation in the world, so credentials you store in Grafana are encrypted with a key that is yours alone.

  • Grafana sign-up, organisation creation and anonymous access are off; usage reporting and update checks are disabled, so the instance makes no unsolicited outbound calls.

  • Node Exporter is bound to 127.0.0.1 because its host metrics are detailed and unauthenticated.

  • Prometheus on 9090 is a read-only, unauthenticated query interface - restrict it in your security group if the instance is internet-facing.

  • Prometheus and Node Exporter run under hardened systemd units (NoNewPrivileges, ProtectSystem=strict, ProtectHome, PrivateTmp).

  • 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.