Self-Hosting n8n on AWS

Self-hosting n8n on AWS makes sense when control, networking, or cost at volume beats the convenience of n8n Cloud. ## Reference setup - ECS/Fargate or EC2 for the n8n app - Managed Postgres for state - Redis if you need queue mode / workers - Secrets Manager for credentials - ALB + HTTPS - Private subnets for database access - Backups and restore drills ## Security baseline - Least-privilege IAM - No long-lived keys in workflow JSON - Separate staging and production where practical - Restrict editor access with SSO or strong identity - Monitor failed executions ## When not to self-host If you have one workflow and no engineering capacity, Cloud is often better. Self-hosting without monitoring creates a new outage class. ## Our delivery pattern We provision, harden, migrate critical workflows, document runbooks, and hand over AWS resources into your account. ## Next step If you already feel Zapier spend or data-residency pressure, bring approximate monthly execution volume. We can compare Cloud vs AWS total cost plainly.