Search for a command to run...
Guide to Zero-Interruptions Deployment for Node.js on AWS EC2
A software engineer who likes to explore new technologies, problem-solving, build projects, and have a keen interest in Web development.
No comments yet. Be the first to comment.
How a 3-line Prisma query fired 1,847 database queries per request — and how we found, fixed, and prevented it from ever coming back.
When building backend systems, especially SaaS applications, handling background jobs correctly is critical. Whether it's sending emails, processing payments, or scheduling reminders, choosing the rig
Clearing the Confusion Around JavaScript Function Arguments
When we work with objects and arrays in JavaScript, we often need to copy data. But copying in JavaScript is not always as simple as it looks. Depending on the method you use, you may end up with shared references which can cause unexpected changes i...
Deploying code sounds easy — until you’re doing it multiple times a day while keeping your production server stable.
Our Node.js backend powers critical features, so even a broken build or 2–3 minutes of downtime wasn’t acceptable. As our team grew, deployment became risky:
Manual SSH deployments were slow
Missed steps caused crashes
Different machines had different Node versions
Rollbacks were painful
Hotfixes slowed down because the pipeline wasn’t automated
We needed a bulletproof CI/CD pipeline.
Below is the journey of how we moved from a patchy deployment process to a fully automated CI/CD setup using GitHub Actions + AWS EC2 + PM2.
Every update required logging into EC2, pulling code, installing dependencies, restarting PM2, and praying we didn’t break something.
During busy days, this became tedious — and errors slipped in.
One laptop used Node 16, another had Node 18.
Some deployments skipped tests.
Some forgot npm install.
Some overwrote .env accidentally.
We were relying on luck, not process.
If something broke:
We scrambled to revert to the previous commit
Re-deployed manually
Restarted PM2 again
Not fast, not reliable.
We needed automation.
We began by automating the basics:
Install Node
Install dependencies
Run tests
Prepare build artifacts
GitHub Actions became our “CI engine”.
Why GitHub Actions?
Close to the repository
Easy secrets management
Parallel jobs
Free for most usage
Very simple YAML-based workflows
This ensured every push was validated before deployment.
Next, we automated deployment.
Instead of SSH-ing manually to EC2, GitHub Actions now:
Builds the backend
Uploads the updated code to EC2
Restarts PM2 automatically
Verifies that the server comes back online
We securely stored:
EC2 host
SSH user
Private key
Environment variables
in GitHub Secrets, eliminating credential sharing.
This alone removed 90% of deployment friction.
PM2 became our process manager.
It allowed:
App restarts without downtime
Crash auto-recovery
CPU utilization monitoring
Log management
Easy rollbacks using saved snapshots
Whenever a deployment happened:
pm2 restart node-app
The app restarted instantly while keeping old connections alive.
Downtime: 0 seconds.
We moved all sensitive configuration from code into:
.env file on EC2
GitHub Secrets for CI
PM2 ecosystem config for runtime variables
This ensured:
No secrets in Git
Easy environment change without redeploy
Safer rollbacks
We refined the pipeline further:
To ensure the API booted correctly.
By keeping previous build folders.
To reduce EC2 disk usage over time.
Using PM2 logs + CloudWatch.
Small improvements → Big stability gains.
┌─────────────────────────┐
│ GitHub Actions │
│ (CI: Build & Test Code) │
└───────────┬─────────────┘
│
▼
┌────────────────────────────────────────────────┐
│ GitHub Actions Deployment Job │
│ 1️⃣ SCP/SSH to EC2 │
│ 2️⃣ Upload Build Files │
│ 3️⃣ Restart PM2 │
└───────────┬───────────────────────────┬────────┘
│ │
┌───────────▼────────────┐ ┌──────────▼─────────────┐
│ AWS EC2 Ubuntu │ │ GitHub Secrets │
│ Node.js + PM2 Runtime │ │ (SSH, Host, Env Keys) │
└───────────┬────────────┘ └─────────────────────────┘
│
┌───────────▼────────────┐
│ Node.js Application │
│ (Zero Downtime via PM2)│
└────────────────────────┘
Migrating to a CI/CD pipeline wasn’t just a tooling upgrade — it was an operational transformation.
With GitHub Actions + EC2 + PM2, we achieved:
Fully automated deployments
Zero downtime during restarts
Safe and secure environment handling
Consistent, reliable build process
Faster development cycles
No more late-night "quick fixes" breaking production
Today, pushing to main is all it takes for a clean, fast, safe deployment — every single time.