Skip to content
Flowise AI Platform & Data · Flowise 3.1.4 Launch on AWS

Operations

This page covers running Flowise day to day: how it is secured, how to manage the services, where logs go, what to back up, how updates work and how to get help.

Security model

  • Loopback only. nginx serves HTTPS on 127.0.0.1:8443 and [::1]:8443. Flowise listens on 127.0.0.1:3000. Nothing listens on a public interface.
  • TLS 1.2 and 1.3 with a certificate created for this instance.
  • Per-instance secrets. The certificate, private key and owner password are created on first boot. The image contains none of them, and no provider keys.
  • File permissions. The ubuntu user can read the certificate, but not the private key or the owner password.
  • Service sandbox. The flowise service runs as the flowise user and can write only to /var/lib/flowise.
  • No telemetry. DISABLE_FLOWISE_TELEMETRY=true.

Keep the security group closed to inbound traffic, and connect with Session Manager or SSH restricted to your administrative range. Only give Flowise accounts to people you trust with your provider credentials.

Manage the services

sudo systemctl status flowise nginx
sudo systemctl restart flowise
sudo systemctl reload nginx

Check that Flowise answers:

curl -sS http://127.0.0.1:3000/api/v1/ping
curl -sS http://127.0.0.1:3000/api/v1/version

ping returns pong. The first-boot service, sushi-flowise-firstboot, runs before Flowise and nginx on every boot and creates anything that is missing. The owner account is created once, by sushi-flowise-admin.

Logs

sudo journalctl -u flowise -n 100 --no-pager
sudo journalctl -u nginx -n 50 --no-pager
sudo journalctl -u sushi-flowise-firstboot -u sushi-flowise-admin --no-pager

Flowise also writes log files to /var/lib/flowise/logs/.

Backups

Back up these together, over a private channel:

  • /var/lib/flowise/ (database, encryption key, uploads and logs)
  • /etc/flowise/ (certificate, key and owner password)

Stop Flowise first so the SQLite database is consistent:

sudo systemctl stop flowise
sudo tar -czf /root/flowise-backup.tar.gz /var/lib/flowise /etc/flowise
sudo systemctl start flowise

Move the archive off the instance, or take an EBS snapshot instead. The archive contains your stored provider credentials and their encryption key: keep it private.

Updates

  • Ubuntu packages, including nginx and OpenSSL, receive unattended security updates.
  • Flowise and Node.js are not updated by apt. A new Flowise release comes as a new version of the image. There is no in-place upgrade: launch the new version, restore /var/lib/flowise and /etc/flowise with their ownership, and switch your users to the new instance.

Support

Software Sushi supports the packaging, first-boot setup and this documentation. Email info@softwaresushi.com with your Flowise version, what you ran and the error. Never include the owner password, provider keys or a backup. Support coverage beyond installation questions requires a separate agreement. FlowiseAI support is not included.

Last updated October 13, 2026 · Suggest an improvement