Skip to main content

Deploy with an agent

Copy agent prompt

Before you start

Connect your AWS account using the Spring Winter quickstart. You need durable flow and credential storage for editable deployments. Check the upstream deployment instructions and pin a release before you deploy. Source repository.

Data dependencies

The standard runtime needs no SQL database. Provision a database before deploying only if your flows or storage plugin require one.

Configure the deployment

  1. Select a Spring Winter project in the AWS Region you want to use. Use a web server for the HTTP app and configure dependencies before you start it.
  2. Use nodered/node-red on port 1880.
  3. The editor stores flows and settings in /data.
  4. Use a persistent host for interactive editing or build a versioned GitHub image that includes flows, settings and nodes and treats changes as deployments.
  5. Configure admin authentication and keep credential secrets out of the build.
When you run the HTTP app on Spring Winter, set a health path that returns HTTP 200 without signing in. Use Runtime variables for runtime configuration. Task storage is temporary. Verify that every file you need after replacement goes to durable storage.

Verify the deployment

Check the deployment in History if you created Spring Winter compute. Wait for the workflow to succeed, then test the application over HTTPS. Sign in to the editor, trigger a harmless flow and verify that the intended flow and credentials are present after replacement.