n8n + Puppeteer Deployment
Budget: ₹1,000 – ₹2,000 INR
I want my self-hosted n8n instance to run smoothly on AWS EC2, inside Docker made with coolify, with full Puppeteer support for any browser-automated workflows I create. The AWS account is already live and configured, so you can focus entirely on the containerisation and server-side setup rather than account provisioning. I'll provide the coolify account credentials.
Here is what I need from you:
• Build (or refine) a Dockerfile / docker-compose.yml that bundles n8n together with all Chromium dependencies required by Puppeteer.
• Spin up the stack on an EC2 instance (Amazon Linux 2 or Ubuntu—whichever suits the build best) and make sure the service auto-starts on reboot.
• Persist n8n data volumes so updates or crashes never wipe my workflows.
• Secure the endpoint (HTTPS via Let’s Encrypt or an equally simple TLS approach) and harden the EC2 instance with the usual firewall and least-privilege tweaks.
• Expose any environment variables—webhook URL, credentials, execution mode, etc.—through a clear .env file so I can adjust settings without diving into the image.
• Hand over concise, step-by-step documentation covering rebuilds, upgrades, and backup/restore.
I will test by running a sample workflow that launches Puppeteer, grabs a screenshot, and stores it in n8n; success means it finishes without errors and survives an EC2 reboot.
If Docker, Node.js, and AWS CLI are second nature to you, let’s get this container live.
Here is what I need from you:
• Build (or refine) a Dockerfile / docker-compose.yml that bundles n8n together with all Chromium dependencies required by Puppeteer.
• Spin up the stack on an EC2 instance (Amazon Linux 2 or Ubuntu—whichever suits the build best) and make sure the service auto-starts on reboot.
• Persist n8n data volumes so updates or crashes never wipe my workflows.
• Secure the endpoint (HTTPS via Let’s Encrypt or an equally simple TLS approach) and harden the EC2 instance with the usual firewall and least-privilege tweaks.
• Expose any environment variables—webhook URL, credentials, execution mode, etc.—through a clear .env file so I can adjust settings without diving into the image.
• Hand over concise, step-by-step documentation covering rebuilds, upgrades, and backup/restore.
I will test by running a sample workflow that launches Puppeteer, grabs a screenshot, and stores it in n8n; success means it finishes without errors and survives an EC2 reboot.
If Docker, Node.js, and AWS CLI are second nature to you, let’s get this container live.
Related categories:
Linux
Amazon Web Services
Node.js
Ubuntu
Docker
Automation
Docker Compose
Containerization
n8n