Nagios 4 AMI

Our Nagios AMI with additional statistics support.

NAGIOS XI provides monitoring of all critical mission infrastructure components, including applications, services, operating systems, network protocols, systems metrics and network infrastructure.Hundreds of third -party accessories allow the monitoring of practically all internal and external applications, services and systems.

Features  

Some of Nagios’s most outstanding characteristics are:

• Comprehensive monitoring
• Reports generation
• Multi-Tant capacity
• Expandable architecture
• Stable, reliable and respected platform
• Customizable code

The main characteristics of our AMI are

• AMI based on Ubuntu Jammy Jellyfish
• Nagios 4 installed and configured from Ubuntu package (latest stable version)
• Nagiosgraph installed and configured from our own Deb package (latest stable version)
• Optimized with: NGINX, PHP 7.4 and FCGIWARP

Installation  

The installation follows the normal process of creating an instance in EC2.The recommended instance size is T3.Medium.

The security group usually includes the following permissions:

The fields marked with (*) are essential, both to access the web interface and for the normal operation of the server.Although we use 0.0.0/0 to allow access to all sources as an example, we recommend blocking access only to their networks or hosts.

Once the instance is working, we can access using:

• SSH: Using the .pem that we have selected when launching the instance, and the user ubuntu.
• HTTP: Using the URL https: //ip.of.nagios.instance/nagios4/, with Nagiosadmin and password the ID of the instance we just created.

Configuration  

Let’s encrypt SSL configuration  

To configure a valid certificate we must first change the host name of the EC2 instance to generate the certificate. AWS does not allow to generate certificates for the default name of the instance, because the names (and the IPS) are volatile.

Edges the file /etc/nginx/sites-enabled/nagios4.conf and configures the domain name in the Server_name inputs. Be sure to break them down. If, for example, we use the nagios4.imaxe.cloud entry, the configuration would remain as:

server {
    listen 80;
    server_name nagios4.imaxe.cloud;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;

    server_name nagios4.imaxe.cloud;

then we will restart the service using the command:

service nginx restart

the last step is to use certbot to configure the registration and renewal of our certificate, with the command:

certbot --nginx --agree-tos --register-unsafely-without-email -d nagios4.imaxe.cloud

After executing this command you can access the instance using https://yourdomainname

Support  

The use of our ami Nagios includes its support in relation to:

• AMI installation
• Initial configuration
• Additional configurations related to AMI (for example, support for LetsenCrypt)
• Nagios configuration aspects that may be related to AMI
• Basic general support of Nagios
• Support for updates and migrations of AMI

In any case, if you have any questions, you can always contact us and we will try to help you.

Changelog