Ad Widget

Collapse

How to make a Proxy in a physical machine communicate with Zabbix in AWS.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ojosaghae
    Junior Member
    • Dec 2022
    • 13

    #1

    How to make a Proxy in a physical machine communicate with Zabbix in AWS.

    Good day! I'm new here and this is my first post.

    I just started using Zabbix about a couple of months ago (July / August 2022) and I must say, it's very interesting and robust. However, I need help.

    I have Zabbix server (Version 6.2.6) installed on a physical machine running Ubuntu 20.04.5 LTS in the office to monitor the physical equipment (servers, switches etc). I also have Zabbix Proxy (version 5.0.17) installed on a separate dedicated machine in the office. They both work seamlessly. They are behind a pfSense firewall.

    The office is having a remote site, and I want to monitor from the cloud, so I have installed Zabbix server on an EC2 instance in AWS. I have opened the following ports on the EC2 as inbound rules, using the Office's WAN IP as the Source:
    UDP 161 - 162
    TCP 443 and 80
    TCP 10051

    I have also done NAT on the firewall:
    Source Address: EC2 Public IP
    Source Ports: *
    Destination Address: Office WAN IP
    NAT IP: Zabbix Proxy IP at the office.
    NAT Ports: 1-65535

    The EC2 Instance is not seeing the Proxy.

    How do I make the EC2 Zabbix instance see the Proxy and poll materials? The proxy is set to Active.

    Any further (non-confidential) information will be supplied.

    Thank you so much in advance!
  • Markku
    Senior Member
    Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
    • Sep 2018
    • 1781

    #2
    First of all, server and proxy must be the same major version (like 6.2.x). I have no idea how reliably your current setup can be working. See: https://www.zabbix.com/documentation.../compatibility

    Second, you cannot connect one proxy with two separate server setups. (HA setup is a different case.)

    Third, if the proxy is active, it will connect to the server, not the other way around. See: https://majornetwork.net/2017/10/zab...nts-and-ports/

    Anyway, you can install a second proxy in EC2 (monitoring the remote site) and get it connected to the Zabbix server in the office.

    Markku

    Comment

    • ojosaghae
      Junior Member
      • Dec 2022
      • 13

      #3
      Hello, Markku. Thank you for your explanation. I really appreciate it. Let me explain what I'm trying to achieve - please point me in the right direction.
      Initially, the goal was just to monitor physical devices on-prem. Hence I went with a simple Zabbix installation. And it worked beautifully.

      Now, We have a second office in another location. I want to be able to monitor the equipment in both (and more) offices from a Zabbix EC2 instance.

      How do I go about the setup?

      Comment

      • Markku
        Senior Member
        Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
        • Sep 2018
        • 1781

        #4
        You set up one Zabbix server, and one or more Zabbix proxies (usually in other locations) as needed by your monitoring and firewalling requirements.

        Markku

        Comment

        • ojosaghae
          Junior Member
          • Dec 2022
          • 13

          #5
          Much appreciated, Markku. Let me see if I understand you.
          I have to set the Zabbix Server in the Cloud (as an EC2 instance), then set up the proxies (as physical machines) on the network of the devices to be monitored. Each location will have a different proxy (that's clear).

          Am I right, please? So sorry I'm
          repeating - just want to be sure.
          Last edited by ojosaghae; 26-12-2022, 11:42.

          Comment

          • Markku
            Senior Member
            Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
            • Sep 2018
            • 1781

            #6
            Sounds fine for me.

            Markku

            Comment

            Working...