> ## Documentation Index
> Fetch the complete documentation index at: https://docs.springwinter.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy n8n

> Set up n8n and connect its dependencies with Spring Winter.

## Deploy with an agent

Copy agent prompt

Help me deploy n8n for private company use in our own AWS account. Read [https://docs.springwinter.dev/deploy/open-source/n8n](https://docs.springwinter.dev/deploy/open-source/n8n.md), [https://docs.n8n.io/deploy/host-n8n/install-options/install-with-docker.md](https://docs.n8n.io/deploy/host-n8n/install-options/install-with-docker.md), and [https://docs.springwinter.dev/api-reference/agents](https://docs.springwinter.dev/api-reference/agents.md). Fetch the public OpenAPI specification from my Spring Winter origin. Use my local SPRINGWINTER\_TOKEN or existing SPRINGWINTER\_API\_TOKEN. Keep credentials out of chat, logs and source.

Confirm my project, AWS connection, Region and budget. Pin a release. Check its required services, container port, health path, network access and durable storage. Data requirements for this deployment: PostgreSQL for this company deployment. Redis is needed only if you choose queue mode.

1. Create a private PostgreSQL database in your Spring Winter project. Wait for the writer. Open Connect and prepare an application database and role.
2. Deploy docker.n8n.io/n8nio/n8n as a web server on port 5678. Set DB\_TYPE=postgresdb and DB\_POSTGRESDB\_HOST, DB\_POSTGRESDB\_PORT, DB\_POSTGRESDB\_DATABASE, DB\_POSTGRESDB\_USER and DB\_POSTGRESDB\_PASSWORD. Use database TLS settings appropriate for your deployment.
3. Set a stable N8N\_ENCRYPTION\_KEY, the HTTPS WEBHOOK\_URL and N8N\_PROXY\_HOPS for the actual proxy chain. Restrict editor access to the company. If workflows must receive external webhooks, expose only the necessary routes through a suitable proxy. If you need file-backed features, verify their durable storage before use.
4. Start the main instance and let it migrate the database. In queue mode, provision Redis before starting the main instance and start workers after migrations. Use the same database and encryption key for all n8n processes.

Show me the planned resources, database and migration order, secret names and estimated cost. Identify components that require separate hosting. Wait for approval before making changes. Include any planned restart, task replacement or restore in that approval. Use documented Spring Winter operations and wait for each workflow to finish. Create and run a harmless workflow. Test a webhook if enabled and confirm stored credentials can still be used after task replacement. Report resource links and anything you could not verify.

## Before you start

[Connect your AWS account](https://docs.springwinter.dev/connect-aws.md) and choose a project. Review the [upstream deployment instructions](https://docs.n8n.io/deploy/host-n8n/install-options/install-with-docker.md) for the release you plan to pin.

This guide covers private company use in your own AWS account. n8n is source-available under its [Sustainable Use License](https://docs.n8n.io/n8n-community-license.md).

## Data dependencies

PostgreSQL for this company deployment. Redis is needed only if you choose queue mode. See [SQL databases](https://docs.springwinter.dev/deploy/databases.md) for private writer access and connection details.

## Deployment order

1. Create a private PostgreSQL database in your Spring Winter project. Wait for the writer. Open Connect and prepare an application database and role.
2. Deploy docker.n8n.io/n8nio/n8n as a web server on port 5678. Set `DB_TYPE=postgresdb` and `DB_POSTGRESDB_HOST`, `DB_POSTGRESDB_PORT`, `DB_POSTGRESDB_DATABASE`, `DB_POSTGRESDB_USER` and `DB_POSTGRESDB_PASSWORD`. Use database TLS settings appropriate for your deployment.
3. Set a stable `N8N_ENCRYPTION_KEY`, the HTTPS `WEBHOOK_URL` and `N8N_PROXY_HOPS` for the actual proxy chain. Restrict editor access to the company. If workflows must receive external webhooks, expose only the necessary routes through a suitable proxy. If you need file-backed features, verify their durable storage before use.
4. Start the main instance and let it migrate the database. In queue mode, provision Redis before starting the main instance and start workers after migrations. Use the same database and encryption key for all n8n processes.

Use [Runtime variables](https://docs.springwinter.dev/concepts/environment-variables.md) for runtime credentials. For a [Spring Winter web server](https://docs.springwinter.dev/deploy/web-servers.md), set an app-supported health path that returns HTTP 200 without credentials. Check **History** before running the application check.

## Verify the deployment

Create and run a harmless workflow. Test a webhook if enabled and confirm stored credentials can still be used after task replacement.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.