Recommendation Needed – High Availability Setup for Nagios Core (EC2 vs Kubernetes)
Posted: Mon Mar 23, 2026 5:08 am
Hello Team,
We are currently using the **latest version of Nagios Core** for monitoring our URLs. At present, the setup consists of a **single Nagios server**, and all monitored URLs are within the **same internal network**.
Since several **production URLs are being monitored**, we are now planning to move towards a **High Availability (HA) setup** to avoid a single point of failure.
We would like recommendations on the best deployment architecture moving forward.
**Current Setup**
* Nagios Core (latest version)
* Single server deployment
* Monitoring internal URLs within the same network
* Custom monitoring scripts and plugins
* Server state monitoring of few ec2 instance.
**Future Requirements**
* High Availability monitoring setup
* Ability to scale monitoring as the number of URLs increases
* Support for additional plugins in the future (e.g., DejaClick / browser-based monitoring)
* Improved reliability for production monitoring
**Options Under Consideration**
1. Deploy **Nagios Core on an EC2 instance**
* Possibly with secondary standby instance
* Traditional VM-based HA setup
2. Deploy **Nagios Core inside a Kubernetes cluster**
* Containerized deployment
* Potential for auto-scaling and easier management
**Questions**
1. Which architecture is recommended for **production monitoring with HA**?
2. Is **Kubernetes deployment suitable for Nagios Core**, or is VM/EC2 deployment more stable?
3. What is the **best practice for scaling Nagios with browser-based monitoring tools like DejaClick**?
4. Are there any recommended **HA architectures or reference implementations** for Nagios Core?
Any guidance, architecture recommendations, or best practices would be greatly appreciated.
Thank you.
We are currently using the **latest version of Nagios Core** for monitoring our URLs. At present, the setup consists of a **single Nagios server**, and all monitored URLs are within the **same internal network**.
Since several **production URLs are being monitored**, we are now planning to move towards a **High Availability (HA) setup** to avoid a single point of failure.
We would like recommendations on the best deployment architecture moving forward.
**Current Setup**
* Nagios Core (latest version)
* Single server deployment
* Monitoring internal URLs within the same network
* Custom monitoring scripts and plugins
* Server state monitoring of few ec2 instance.
**Future Requirements**
* High Availability monitoring setup
* Ability to scale monitoring as the number of URLs increases
* Support for additional plugins in the future (e.g., DejaClick / browser-based monitoring)
* Improved reliability for production monitoring
**Options Under Consideration**
1. Deploy **Nagios Core on an EC2 instance**
* Possibly with secondary standby instance
* Traditional VM-based HA setup
2. Deploy **Nagios Core inside a Kubernetes cluster**
* Containerized deployment
* Potential for auto-scaling and easier management
**Questions**
1. Which architecture is recommended for **production monitoring with HA**?
2. Is **Kubernetes deployment suitable for Nagios Core**, or is VM/EC2 deployment more stable?
3. What is the **best practice for scaling Nagios with browser-based monitoring tools like DejaClick**?
4. Are there any recommended **HA architectures or reference implementations** for Nagios Core?
Any guidance, architecture recommendations, or best practices would be greatly appreciated.
Thank you.