Node.js & npm on Ubuntu EC2

Beginner
⏱️ 6 min read
📚 Updated: Aug 2025
Ubuntu / apt / n
Terminal on Ubuntu EC2 showing node and npm versions

What you’ll learn

On a fresh Ubuntu instance in Amazon EC2, you typically install Node.js and npm before deploying an app. This guide uses the distribution packages as a starting point, then upgrades to a supported release line with n, matching the console flow from the original screenshots.

Prerequisites

Before you begin, make sure you have the following:

  • An AWS account with access to EC2.
  • An Ubuntu EC2 instance in the running state.
  • SSH access—for example with PuTTY on Windows or ssh from macOS or Linux—using a user that can run sudo (often ubuntu on official Ubuntu AMIs).

Update package metadata

Refresh the local apt index so installs resolve to current repository metadata:

Terminal (EC2)
sudo apt update

Install Node.js and npm

  1. Install the Ubuntu packages (names may vary slightly by release):

    Terminal (EC2)
    sudo apt install -y nodejs npm

  2. During dependency installation, a dialog may appear stating that daemons are using outdated libraries. On an interactive SSH session, press Enter or choose OK to continue.

    Ubuntu dialog about daemons using outdated libraries during apt
    Ubuntu

  3. Check versions without sudo (you want your login user’s PATH):

    Terminal (EC2)
    node -v
npm -v
    Terminal showing node and npm versions after apt install
    Ubuntu

Upgrade to a current Node.js with n

The nodejs package in Ubuntu is often several majors behind upstream. The n tool downloads prebuilt Node binaries and switches the active version under /usr/local.

  1. Install n globally with npm, then install a newer Node line. Prefer LTS:

    Terminal (EC2)
    sudo npm install -g n
sudo n lts

    To match the original walkthrough exactly you can pin a version instead, for example sudo n 22 for the latest Node 22.x, after checking nodejs.org.

    Terminal showing upgraded Node.js version after running n
    Ubuntu

  2. Open a new SSH session (or run hash -r) and verify again with node -v and npm -v.

Key takeaways

1

apt gives a stable but often older Node; upgrade when your framework or runtime requires a newer major.

2

n is one option; teams also use nvm, fnm, or distribution-neutral NodeSource setup scripts—pick one approach per instance to avoid conflicting binaries.

3

After Node is ready, use FileZilla or git to move project files, then follow Deploy Node.js on EC2 for PM2 and port setup.

Frequently asked questions

Ubuntu freezes versions for the distribution lifecycle. That Node build is maintained for security, but it may not match the newest ECMAScript or npm features your app expects.
n installs system-wide under /usr/local, which is simple for a single-app EC2. nvm is user-scoped and popular for development machines. Either is fine if you stay consistent and document which user runs your process manager.
Running the interpreter as root for routine checks hides permission problems you will hit when the deploy user runs your app. Use sudo only for installs and privileged port binds, not for ordinary version checks.

Next: SFTP with FileZilla

With Node installed, copy your application files from your laptop using the same SSH endpoint and key.

FileZilla and EC2 →
Did you know?

npm ships with Node.js installers on most platforms. After you install a newer Node line with n, run hash -r or open a new shell if which node still points at an old binary.

About the author

Mari Selvan M P
Mari Selvan M P 🔗

Developer, cloud engineer, and technical writer

  • Experience 12 years building web and cloud systems
  • Focus Full Stack Development, AWS, and Developer Education

I write practical tutorials so students and working developers can learn by doing—from databases and APIs to deployment on AWS.

AWS Certified Developer – Associate (Credly)

8 people found this page helpful

PuTTY and EC2 FileZilla and EC2