Rehost Node.js PMS to AWS
Budget: ₹1,500 – ₹12,500 INR
An existing Node.js (v14.x) Property Management System is running smoothly on Replit, but it now needs a proper production home. I work on Windows and already have PostgreSQL up and running locally. The goal is to replicate the full stack on my machine, iron-out any build or dependency hiccups, and then push a hardened, SSL-secured release to AWS.
Key steps in the workflow
• get the repo building on Windows, resolving environment, path, or native-module issues
• organise all .env variables so they load cleanly both in development and production
• validate the local PostgreSQL connection, run migrations/seed data, and document any required extensions
• prepare a production build, optimise static assets, and verify memory usage
• recommend and provision an AWS target (EC2, Lightsail, or ECS—whichever best suits this single-service app)
• configure Nginx as a reverse proxy if it provides an advantage over a straight Node port expose
• install and tune PM2 (or similar) for graceful reloads, log rotation, and auto-restart on crash
• issue and renew SSL certificates to serve all traffic over HTTPS
• hand back a repeatable deployment script or Terraform/CloudFormation snippet so future rebuilds are one command away
Acceptance criteria
1. npm start (or an equivalent PM2 command) boots the app without warnings on my Windows machine.
2. A public AWS endpoint serves the PMS over HTTPS with a valid certificate.
3. rebooting the instance or force-killing the process triggers an automatic recovery.
4. All database calls succeed against the PostgreSQL instance.
5. A concise README documents local setup, environment variables, and the exact deploy steps.
Once it runs stably, I should be able to shut the laptop lid or restart the server without the application missing a beat.
Key steps in the workflow
• get the repo building on Windows, resolving environment, path, or native-module issues
• organise all .env variables so they load cleanly both in development and production
• validate the local PostgreSQL connection, run migrations/seed data, and document any required extensions
• prepare a production build, optimise static assets, and verify memory usage
• recommend and provision an AWS target (EC2, Lightsail, or ECS—whichever best suits this single-service app)
• configure Nginx as a reverse proxy if it provides an advantage over a straight Node port expose
• install and tune PM2 (or similar) for graceful reloads, log rotation, and auto-restart on crash
• issue and renew SSL certificates to serve all traffic over HTTPS
• hand back a repeatable deployment script or Terraform/CloudFormation snippet so future rebuilds are one command away
Acceptance criteria
1. npm start (or an equivalent PM2 command) boots the app without warnings on my Windows machine.
2. A public AWS endpoint serves the PMS over HTTPS with a valid certificate.
3. rebooting the instance or force-killing the process triggers an automatic recovery.
4. All database calls succeed against the PostgreSQL instance.
5. A concise README documents local setup, environment variables, and the exact deploy steps.
Once it runs stably, I should be able to shut the laptop lid or restart the server without the application missing a beat.
Related categories:
Linux
NoSQL Couch & Mongo
Nginx
Amazon Web Services
Node.js
PostgreSQL
Full Stack Development
Documentation
SSL
Terraform