Node-RED

Node-RED

Low-code, flow-based programming for event-driven applications

automationiotlow-code

About 10 minutes Resources are created in your AWS account

Screenshot from verification · Click to enlarge

5.0.9 · Verified 5 hours ago

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: data directory writable by the image user, admin area protection. This excludes full business acceptance and trusted TLS certificate issuance.

View report

Quick Deploy

Deployment paused

Latest Version5.0.9
VersionsVerified AtVerifiedStatusAWS Tested
5.0.9Nov 1, 2026Deployment pausedBug FixAWS · referenced
5.0.8Oct 16, 2026Deployment pausedBug FixAWS · referenced
5.0.7Sep 16, 2026Deployment pausedInitialAWS · referenced

Technical information

Container port1880
Supported Architecturesx86_64
AMIami-0d6dd9e8265d48906
Container imagenodered/node-red:5.0.9

FAQ

How do I access Node-RED 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 flow editor is available at / after startup. Configure editor access control before exposing production flows.

Where are application data and credentials stored?

Application data is mounted at /data 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.