On Premises Requirements

LNS & OAM supports the following architecture models:

• Single Server
• Single Server with External Services
• Cloud Deployment

2. Installation Options

• On-Premise
• Cloud
  • AWS
    • EC2 Instance
    • EKS (Kubernetes)
  • Microsoft Azure
    • Azure Virtual Machine

The application is deployed on a single physical or virtual server that hosts a single-node Kubernetes cluster. All core components — including the application service, database, Kafka broker, and Redis instance — are deployed as Kubernetes pods and run on the same underlying host.

This is the simplest and fastest deployment model. It is suitable for small-scale production environments as well as for development and testing purposes.

Advantages

• Simple architecture – Easy to deploy, manage, and maintain.
• Lower infrastructure cost – Requires only one server.
• Fast setup – Minimal configuration and operational overhead.

Disadvantages

• Single point of failure – Failure of the host results in a complete system outage.
• No high availability – A single-node Kubernetes cluster does not provide redundancy.
• Limited scalability – Horizontal scaling is constrained by the capacity of a single machine.
• Maintenance downtime – Server maintenance requires full system downtime.

In this architecture, the application runs on a single server, while supporting services (database, Kafka, Redis, etc.) are deployed externally.

This approach improves reliability and scalability compared to the fully self-contained single-server model.

• CPU: 4 cores
• Memory: 16 GB RAM
• Storage: 120 GB SSD

• Ubuntu Server 20.04 LTS or newer
• RHEL 8 or newer

• 80 HTTP
• 443 HTTPS
• 1883 MQTT
• 8883 MQTTS
• 1700

• 1700

LNS supports online and offline installation modes.

Disk layout should allocate all available space to “/”. ← add screenshot from test server here

Installation can be performed by the root user or another user who has sudo rights.

We use an Ansible playbook for LNS installation, and it installs all required packages, so there is no need to install any packages in advance.

Preferred direct SSH access to the server, but other installation options are available (we can send files and instructions).

During installation, a self-signed SSL certificate is generated. If a valid certificate is provided, it can be used instead.

We require a dedicated server for LNS. Nothing should be installed in advance (no other software).

• EC2 instance

• EKS

  • all in cluster
  • services are external (rds, msk, postgres)