Older Zabbix AMI versions (up to 4.4 version) should refer to this documentation
If you are using a version of the AMI Zabbix prior to version 4.4, we strongly recommend that you update to the latest AMI version. You will get more stability and security.
If you have any questions about the update, please contact us.
- AMI based on Ubuntu Bionic Beaver
- Zabbix 4.0 server installed (latest stable version)
- Zabbix 4.0 web interface installed and configured.
- Program configured and configurable for sending notification via AWS SNS.
- Optimized with: apache2, PHP 7, mariadb server, zabbix 4.0 repository
Installation and configuration
The installation follows the normal process of creating an instance in EC2. The recommended instance size is t2.large.
The security group usually includes the following permissions:
|Type||Protocol||Range of ports||Source|
|(*) Custom TCP rule TCP||TCP||10050 – 10052||0.0.0.0/0|
The fields marked with (*) are essential, either to access the web interface or for the normal operation of the server.
Once the instance is running, we can access using:
- SSH: Using the .pem that we have selected when launching the instance.
- HTTPS: Using the url https: //zabbix.instance.ip/zabbix/, with user Admin and key the ID of the instance that we just created.
Shipment configuration with SNS
This Zabbix installation is now ready to ship using AWS SNS . This configuration allows us to avoid problems related to sending mail in AWS, and have an advanced and secure notification delivery system.
Up to 5 different SNS issues can be configured (to distinguish according to the importance of the shipment), which are “Not classified”, “Information”, “Warning”, “Average”, “High” and “Disaster”.
The recommended steps to configure notifications are:
- Create our SNS topic
- Create a user with permissions to send SNS
- Edit the file /etc/zabbix/zabbix_sns.ini and indicate the necessary values
- Once this step is configured, in the Zabbix interface we can choose the “aws-sns” medium for the user that we are configuring.
SSL configuration valid with Let’s Encrypt
In order to configure a valid certificate we must first change the host name of the EC2 instance to allow us to generate the certificate. AWS does not allow certificates to be generated for the default name of the instance, because names (and IPs are volatile).
Personalization and support
If you need to customize the default options of the AMI, or have any questions or problems, you can write me at the address: