Tools used ( n8n on Docker, AWS - us-east-1 region, Jenkins for CICD, Github - Code repo, Terraform - Infrastructure as a Code, Hostinger - Domain name provider, AWS ACM - SSL Certificate, VS Code - for coding)
I built this entire structure using Amazon Q (CLAUDE 4) in just few hours— it’s fully functional, it’s even BETTER.
To put this in perspective, a previous company I worked for invested over $1 million and spent more than a year developing a similar solution to deploy on AWS. Despite all that time and money, their project never truly succeeded.
Someone once told me, “Make it better, but never fail to make it work!” I took that advice to heart.
The result? A modular, Infrastructure-as-Code (IaC) solution that simply works—reliably and efficiently. Here’s the finished product.
Next I will be hosting n8n on AWS with ECS - Fully Production ready for Enterprises
n8n
Update - added code to Git and Jenkins DevOps / CICD pipeline too
Hi, not sure what the novelty is here TBH and also it’s not “built with n8n”. IaC is around for over 10 years. If you want your post to have value share a repo so at least the people that are interested in it can have a look.
Reg
J
I agree however I have not seen a single post of anyone achieving this yet. Neither on youtube nor here on the community hence thought of sharing. I did not find any other place to share this. I am going to create a youtube video to showcase this.
There is no Novelty 
Enterprises spend millions on AWS to create the infra that I have here
Hi,
Well there are some references left and right on the forum: Run n8n docker hub image on AWS ECS Fargate with EFS (there is a link which I posted).
As far as resources, there are enough online resources for ECS and it’s not that hard to adapt for N8N specific if that’s missing
Personally I have terraform setups but I’m not willing to share/ play support (and imho knowing how to operate/support is the most important in achieving success).
As regarding to the millions being spent on building IaC setups. I highly doubt that. Usage costs for cloud resources is another story.
I think the most important part for fellow readers is that “self-hosted” doesn’t mean free. Any well built solution (as in enterprise-grade,AWS managed type resources (custom VPC per env, connectivity, alb, RDS, redis, …) on AWS will easily costs several hundreds per month only on infra to keep it powered on without usage. Following the discussions a licensing fees and cloud costs it’s good to put things clear.
Reg,
J.
My apologies, I may have missed that link which you posted. I will definitely look into it before I do my ECS setup. For Enterprises I am giving my own experience as I do work as an AWS solutions architect full time with Fin-Tek / Pharma and I know how much they invest on cloud. This is what I set up for my own personal use and not a single soul has to use it . I am just sharing my thoughts here as its an open forum.
