How to Deploy a Nodejs Application on Free Tier AWS EC2 Instance: A Step-by-Step Guide

What Is a Free Tier AWS EC2 Instance?

An AWS EC2 (Elastic Compute Cloud) instance is essentially a virtual computer running in Amazon’s data centers. When you sign up for a new AWS account, Amazon gives you access to the “Free Tier,” which includes 750 hours per month of a micro instance (usually t2.micro or t3.micro, depending on your region) for the first 12 months.

Think of it as renting a tiny, blank-slate computer in the cloud that runs Linux. You get complete administrative access (root access) to install whatever you want, including Node.js, databases, and web servers.

Why People Use AWS EC2 for Node.js Hosting

Many developers choose AWS EC2 over platforms like Heroku, Render, or Railway because it offers unmatched flexibility. PaaS (Platform as a Service) providers are incredibly convenient, but they often sleep after periods of inactivity or charge hefty premiums once you scale past their free tiers.

EC2 gives you raw infrastructure. There are no arbitrary file system restrictions, your application won’t “go to sleep” to save resources, and you learn real-world DevOps skills that are highly valued in the tech industry.

Key Features of AWS EC2 Free Tier

750 Hours Monthly: Enough to run one instance continuously every single day of the month.
Elastic Block Store (EBS): You get 30 GB of free SSD storage to house your operating system and application files.
Custom Security Groups: A built-in virtual firewall to control exactly which ports are open to the public.
Static IP Capabilities: Through AWS Elastic IPs, you can ensure your server’s IP address doesn’t change when you reboot it.

How It Works: The Deployment Workflow

Deploying a Node.js app on EC2 involves shifting from your local development environment to a remote server environment. Instead of clicking buttons on a dashboard, you will interact with your server using a command-line interface via SSH (Secure Shell).

[ Your Local Laptop ] ---SSH / Git---> [ AWS EC2 Instance ] ---> [ Runs Node.js via PM2 ]

Your app runs continuously on the remote machine. To make it accessible to the internet safely, you use Nginx as a reverse proxy, which listens for web traffic on standard web ports (80 for HTTP) and routes it internally to your Node.js application.

Practical Use Cases

Building a Portfolio MVP: A developer launching a backend API for a portfolio project can host it on EC2 without paying a dime for the first year.
Webhook Receivers: If you are building a tool that integrates with Stripe or GitHub webhooks, you need a 24/7 online URL to catch incoming data payloads.
Discord or Slack Bots: Script-based applications that require constant uptime and low memory consumption fit perfectly within the free tier limits.

Step-by-Step Guide: How to Deploy a Nodejs Application on Free Tier AWS EC2 Instance

Step 1: Launch Your Free Tier EC2 Instance

Log in to your AWS Management Console.
Search for EC2 and click on Launch Instance.
Name your instance (e.g., nodejs-app-server).
Under Application and OS Images, select Ubuntu (Latest LTS version). Ensure it says “Free tier eligible”.
For Instance Type, choose t2.micro (or t3.micro if applicable in your region).
Under Key Pair, click Create new key pair. Name it, download the .pem file, and keep it safe. You cannot download this again!

Step 2: Configure Network Security Groups

Before launching, scroll down to Network Settings.

Check Allow SSH traffic from Anywhere (or change to “My IP” for maximum security).
Check Allow HTTP traffic from the internet.
Check Allow HTTPS traffic from the internet.

Click Launch Instance.

Step 3: Connect to Your Instance via SSH

Open your local terminal (Mac/Linux) or Git Bash (Windows) and navigate to where your .pem file is stored.

First, fix the key permissions:

Bash

chmod 400 your-key-name.pem

Now, connect to your server using its Public IPv4 address (found on your EC2 dashboard):

Bash

ssh -i "your-key-name.pem" ubuntu@your-ec2-public-ip

Step 4: Install Node.js and NPM

Once logged into your Ubuntu server, update the system packages and install Node.js via the NodeSource repository:

Bash

sudo apt update
sudo apt install -y curl git
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt-get install -y nodejs

Verify the installation by running node -v and npm -v.

Step 5: Clone and Setup Your Node.js Application

Clone your repository directly onto the server:

Bash

git clone https://github.com/your-username/your-repo-name.git
cd your-repo-name
npm install

Create your configuration files or .env file using the nano editor:

Bash

nano .env

Add your environment variables, then press Ctrl + O, Enter, and Ctrl + X to save and exit.

Step 6: Keep the App Running with PM2

If you start your app with npm start, it will close the moment you disconnect your SSH session. To prevent this, use PM2, a production process manager.

Bash

sudo npm install -g pm2
pm2 start server.js --name "my-node-app"

To ensure PM2 revives your application if the EC2 instance reboots unexpectedly, run:

Bash

pm2 startup systemd

Copy the command generated by the output, paste it into the terminal, and then save the configuration:

Bash

pm2 save

Step 7: Configure Nginx as a Reverse Proxy

Right now, your app runs on an internal port (like 3000). We need to map web traffic coming to port 80 to your Node app.

Install Nginx:

Bash

sudo apt install nginx -y

Open the default configuration file:

Bash

sudo nano /etc/nginx/sites-available/default

Find the location / block and update it to look like this:

Nginx

location / {
    proxy_pass http://localhost:3000; # Change 3000 to your app port
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
}

Save and exit. Test your Nginx configuration and restart the service:

Bash

sudo nginx -t
sudo systemctl restart nginx

Now, open your web browser and enter your EC2 Public IP address. Your Node.js application should be live!

Benefits of Hosting on AWS EC2 Free Tier

Zero Financial Cost: Great for tinkering, testing concepts, and learning server administration without an initial financial commitment.
Complete Customization: You are the root administrator. You can configure custom logging, cron jobs, and firewalls exactly how your application requires.
Production Grade Skills: Working with SSH, systemd, and Nginx prepares you for managing enterprise environments.

Limitations of AWS EC2 Free Tier

While a great starting point, a micro instance comes with tight limitations. It typically provides only 1 GB of RAM and 1 vCPU.

A small team building a production-grade application might quickly exhaust these resources. For instance, running a heavy build step like npm run build for a Next.js or heavy React application directly on the server can freeze the instance due to memory exhaustion.

Pros and Cons

Pros	Cons
Completely free for the first 12 months	Only 1 GB of RAM can cause crashes during heavy tasks
High configuration flexibility	No automatic SSL configuration included out-of-the-box
Server doesn’t sleep or idle down	Steep learning curve if you don’t know the Linux CLI

Alternative Hosting Options

Platform	Type	Free Tier?	Best Used For
AWS EC2	VPS (IaaS)	Yes (12 Months)	Complete server control & DevOps learning
Render	PaaS	Yes (Basic)	Fast, configuration-free deployments
Railway	PaaS	Trial Credits	Modern developer experience with simple usage limits
DigitalOcean	VPS	No (Paid)	Predictable $4-$5/month pricing with simple UI

Common Mistakes Users Make

Forgetting to Open Port 80/443: Spending hours debugging why the application won’t load in a browser, only to find out the AWS Security Group is blocking public HTTP requests.
Not Setting Up PM2: Running the application via node index.js and wondering why the website goes down the minute the terminal window is closed.
Exceeding Free Tier Limits: Accidentally running two or three micro instances simultaneously, which burns through the 750 free hours quickly and results in unexpected charges.

Frequently Asked Questions

1. Will I get charged if I exceed 750 hours on AWS EC2 Free Tier?

Yes. The 750-hour limit is cumulative across all running instances. If you run two micro instances simultaneously for a full month, you will use 1,500 hours and get billed for the extra 750 hours.

2. What happens to my EC2 instance after the 12-month free tier expires?

Your instance will continue running, but AWS will begin billing you at the standard pay-as-you-go hourly rate for that specific instance type.

3. How do I point my custom domain name to my EC2 instance?

You need to copy the Public IP address of your EC2 instance and create an A Record inside your domain registrar’s DNS management dashboard (like Namecheap or GoDaddy) pointing to that IP.

4. Why does my EC2 IP address change whenever I stop and start the instance?

AWS reassigns public IPs from a dynamic pool when an instance restarts. To keep your IP static, allocate an Elastic IP in the EC2 dashboard and associate it with your instance. Note: Elastic IPs are free only when attached to a running instance.

5. Can I run a MongoDB database on the same free tier EC2 instance?

Technically yes, but it is not recommended. MongoDB can be resource-heavy, and sharing 1 GB of RAM between Node.js and MongoDB will likely cause out-of-memory errors that crash your server.

6. How do I add an SSL certificate (HTTPS) to my EC2 application?

You can use Certbot to install a free Let’s Encrypt SSL certificate. Certbot automatically hooks into your Nginx configuration and handles certificate renewals.

7. Why does my Node.js build process freeze mid-way on EC2?

This happens when your application runs out of RAM during compilation. You can resolve this by setting up a Swap Space (virtual memory on the SSD storage) or by building the application locally and pushing only the deployment files.

8. Is the AWS Free Tier safe for production use?

It is safe for low-traffic apps or testing, but it lacks the redundancy, high availability, and computing power needed to handle thousands of concurrent production users safely.

9. Can I deploy multiple Node.js applications on one EC2 instance?

Yes. You can use PM2 to manage multiple applications running on different internal ports, and configure Nginx to route traffic to specific apps based on different subdomains.

10. How do I update my code on the server after making changes locally?

The most straightforward way is to commit your code changes to GitHub, log back into your server via SSH, navigate to your app folder, run git pull, and then execute pm2 restart all.

Final Thoughts

Deploying a Node.js application on an AWS EC2 free tier instance is an excellent move if you want total control over your hosting stack and a clear view into how modern server deployment functions. It is best suited for students, backend developers testing MVPs, and anyone eager to build foundational DevOps skills.

However, if you don’t want to manage security updates, configurations, and terminal commands, a simpler PaaS alternative might save you some setup friction.

SEO & Strategic Implementation Details

Internal Linking Opportunities (Placeholders)

How to Setup an AWS Account safely without hidden fees (Link within the “Launch Your Free Tier EC2 Instance” section).
Understanding Linux File Permissions and Chmod (Link near the chmod 400 code snippet block).
Choosing the Right Node.js Framework for Modern Web Apps (Link within the cloned app instructions section).
Introduction to Nginx Reverse Proxies and Load Balancers (Link within the Nginx configuration section).
How to secure your web server with Let’s Encrypt (Link within the FAQ covering SSL certificates).