Cloud

Cloud

NMS Prime in the cloud runs on a Rocky Linux / RHEL 9 VM — either managed by NMS Prime or self-hosted on a provider of your choice (AWS, Hostinger, etc.). The software stack and RPM install process are the same as on-premises; only provisioning and operations differ.

1. Documentation map

Page

Purpose

Page

Purpose

Hardware Requirements

OS, CPU, RAM, disk sizing & Rocky 9 partition layout

Login via SSH

SSH access to your cloud instance

AWS

EC2-specific provisioning & install

Hostinger

Hostinger VPS & CI testing

2. Two ways to run in the cloud

Model

Who provisions the VM

Typical audience

Model

Who provisions the VM

Typical audience

Managed cloud

NMS Prime team

Trial, demo, production without own Linux ops

Self-hosted cloud

You (AWS, Hostinger, other VPS)

Operators who want cloud elasticity but own the VM

2.1. Managed cloud

Request a managed instance via contact.nmsprime.com. You receive:

  • HTTPS URL for the web UI

  • Login credentials

  • SSH key for optional server access (see Login via SSH)

After login, continue with Login and Configuration.

Please provide a valid phone number that is reachable from Germany when you submit your request. Our team will call you within the first 24–48 hours. We typically call two or three times if you are not reachable. We usually call with our number visible — feel free to call back.

Note: The former self-service online signup with screenshot walkthrough has been retired. New instances are provisioned by the NMS Prime team.

2.2. Self-hosted cloud

On any supported VPS or EC2 instance, choose the path for your edition. See Hardware Requirements for sizing; if you install Rocky from ISO, adjust the disk layout there (remove /home) before NMS Prime setup.

2.3. Community (OSS core)

  1. Deploy a fresh Rocky Linux 9 or RHEL 9 VM (see Hardware Requirements)

  2. As root, bootstrap the NMS Prime yum repositories:

    curl -vsL https://github.com/cablelabs/os-provisioning/raw/dev/scripts/INSTALL-REPO.sh | bash
  3. Install packages:

    yum install -y nmsprime-*
  4. Open the web UI and follow Login.

2.4. Enterprise (Prime platform)

Before you install: request package selection, repo access, and license files via contact.nmsprime.com. Do not run yum install for Prime packages until you have received your delivery.

Please provide a valid phone number that is reachable from Germany when you submit your request. Our team will call you within the first 24–48 hours. We typically call two or three times if you are not reachable. We usually call with our number visible — feel free to call back.

  1. Deploy a fresh Rocky Linux 9 or RHEL 9 VM (see Hardware Requirements)

  2. Request access via contact.nmsprime.com — you receive license file(s) and a curated yum install command

  3. Place license file(s) in /etc/nmsprime/licenses/:

    mkdir -p /etc/nmsprime/licenses/ # copy your .lic file(s) here, e.g. via scp
  4. Bootstrap repositories:

    curl -vsL https://github.com/cablelabs/os-provisioning/raw/dev/scripts/INSTALL-REPO.sh | bash
  5. Install packages using the curated yum install command from your delivery (typically not nmsprime-*)

  6. Open the web UI and follow Login.

2.5. RPM repository & versions

Packages are served from repo9.nmsprime.com. The bootstrap script installs nmsprime-repos, which configures yum for OS and Prime package channels.

Channel

Path (on repo9)

Use case

Channel

Path (on repo9)

Use case

Release

/rpm/nmsprime-410/

Stable production installs

Testing

/rpm/nmsprime-testing/

Pre-release validation

GitHub Actions (CI)

/rpm/nmsprime-github-action/<branch>/

Latest builds from dev, dev-next, or feature branches

CI-built RPMs are produced automatically after successful CI on configured branches (dev, dev-next) and can also be triggered manually via the CD RPM Build GitHub Action. To install from a CI branch, request repo credentials via contact.nmsprime.com before running scripts/install-nmsprime-ci.sh — the script waits for license files in /etc/nmsprime/licenses/ before installing packages.

2.6. Provider-specific guides

  • AWS — EC2 provisioning, security groups, Elastic IP

  • Hostinger — VPS setup and GHA install testing

2.7. First login

Default web credentials on a fresh install: root / toor (change immediately). See Login.