Netdata
Real-time infrastructure monitoring with per-second metrics
Screenshot from verification · Click to enlarge
Application tests passed; AWS environment evidence comes from the referenced platform verification.
Before this version became the public one, it was checked on a real one-off AWS stack: admin area protection, declared host metric mounts, data directory writable by the image user. This excludes full business acceptance and trusted TLS certificate issuance.
Quick Deploy
Deployment paused
Versions
View full version history| Versions | Verified At | Verified | Status | AWS Tested |
|---|---|---|---|---|
| v2.12.0 | Sep 30, 2026 | Deployment paused | New Version | AWS · referenced |
| v2.11.1 | Sep 16, 2026 | Deployment paused | Bug Fix | AWS · referenced |
| v2.11.0 | Sep 11, 2026 | Deployment paused | Security Update | AWS · referenced |
Technical information
FAQ
How do I access Netdata after deployment?
After CREATE_COMPLETE, run SSMPortForwardCommand from the stack Outputs in your local terminal and keep it running. Open http://localhost:8080 to initialize the application privately. Public access stays blocked until you explicitly enable HTTPS. The agent dashboard has no local sign-in. The template restricts Web access to localhost by default; use SSM port forwarding. Configure an authenticated HTTPS gateway before widening AllowedWebCidr. Claiming in Netdata Cloud does not protect the local endpoint.
Where are application data and credentials stored?
Application data is mounted at /var/lib/netdata from the encrypted EBS data volume. The volume survives stack deletion and keeps billing; retention is not a backup. Platform proxy credentials and host configuration are on the root disk and are not included in a data-volume snapshot. See the backup guide before deleting anything.