How to access OpUtils on AWS using EC2 instance

    Running OpUtils on AWS helps in ensuring world-class network management for your devices while eliminating the need for a physical server for monitoring.

    You can use OpUtils in AWS using one of two methods:

    1. By purchasing and running OpUtils AMI from AWS store
    2. By installing OpUtils in a separate EC2 instance

    By purchasing and running OpUtils AMI from AWS store

    Before you begin, please purchase OpUtils AMI from here.

    1. After the purchase of the AMI, you will be required to launch an EC2 instance from this AMI. For more information on how to do this, please check this page. While creating the instance, ensure that the following metrics meet the required criteria:
      • EC2 Instance Type: m4.xlarge or above
      • Operating System: Windows 10/8/7 (or) Windows Server 2008 and newer (Supported up to 2019)
      • Storage: 20 GB (minimum)
    2. Once the instance is launched from the given AMI, you need to initiate an RDP session of the particular instance. To learn more about this action, please check this page.
    3. Use the RDP session to log into the instance.
    4. After logging in to the instance, go to the Services app. To do this, type "Services" into the Windows search bar, and click on the Services app result.
    5. In the Services app, check whether the following service is running: ManageEngine OpUtils.
    6. If the ManageEngine OpUtils service is in a running state, go to your browser and connect to OpUtils's console using either of these two ports:
      • http://<ec2_instance_public_dns>:8060 (for HTTP connection)
      • https://<ec2_instance_public_dns>:8061 (for HTTPS connection)
    7. Log in to OpUtils using the following credentials:
      • Username: admin
      • Password: --Instance ID--

    Note:

    When you access OpUtils using the public IP/DNS address, note that the "Public IP/DNS address" changes when the instance is stopped/terminated. As in a network, devices need to forward syslogs and traps to the OpUtils server, so the public IP has to be updated in the end devices every time it changes. Hence, it is recommended to use an elastic IP address for seamless monitoring. For more details on Elastic IP addresses, click here.

    By installing OpUtils in a separate EC2 instance

    Pre-requisites

    Before installing OpUtils in AWS, ensure that you meet the following pre-requisites:

    • If you are planning to manage up to 250 devices using OpUtils, we recommend you have the following instance configurations:
      • EC2 instance type: m4.xlarge or above
      • OS: Windows 10/8/7 or Windows Server 2008 or above (up to 2019 supported)
      • Memory space: 20 GB (minimum)

    Note: The above specifications are the minimum requirements. You may need to change the configurations according to the number of devices you are monitoring and additional integrations/modules (such as firewall, IP address management, etc.). To know more about creating instances, click here.

    • Ensure that the instance's Public IP/DNS is not blocked by any firewall and is accessible to all devices in your network.
    • Ensure that the required security ports are available for use.

    Steps to install and run OpUtils from EC2 instance

    1. Remotely connect to your EC2 instance.
    2. In that instance, open your web browser.
    3. Download and install OpUtils.
    4. Log in to OpUtils using the username admin and password Instance ID.

    Important Note:

    Ensure that the following ports in your OpUtils instance are not blocked for proper functioning of OpUtils and its add-ons (this step is necessary for both running OpUtils from AMI and running OpUtils from an EC2 instance)

    Port

    Protocol

    Port Type

    Usage

    Remarks

    13306

    TCP 

    Static (PostgreSQL)

    Database Port

    Can be changed in conf/database_params.conf file.

    1433

    TCP

    Static (MS SQL) 

    Database Port 

    Can be changed in conf/database_params.conf file/ dbconfiguration.bat file.

    22 

    TCP 

    Static 

    SSH Port 

     

    8060

    TCP 

    Static 

    Web Server Port 

    Can be configured using ChangeWebServerPort.bat. 

    161

    UDP

    Static 

    SNMP

     

    135

    TCP

    Static 

    WMI

     

    445

    TCP 

    Static 

    WMI

     

    5000 to 6000

    TCP 

    Dynamic

    WMI

     

    49152 to 65535

    TCP

    Dynamic

    WMI

    Windows 2008R2 and higher

    2000

    TCP

    Static

    Internal Communication Port

     

    56328

    TCP

    Dynamic

    ShutDown Listener Port

     

    162

    UDP

    Static

    SNMP Trap Receiver Port

     

    514

    UDP

    Static

    SYSLOG Receiver Port

    SYSLOG Receiver Port can be changed via WebClient

    69

    UDP

    Static 

    TFTP Port [NCM]

     

    1514

    UDP

    Static 

    Firewall Log Receiver [FWA]

    Firewall Receiver Port can be changed via WebClient

    9996

    TCP

     

    NetFlow Listener Port [NFA]

    NetFlow Listener Port can be changed via WebClient

    Thank you for your feedback!

    Was this content helpful?

    We are sorry. Help us improve this page.

    How can we improve this page?
    Do you need assistance with this topic?
    By clicking "Submit", you agree to processing of personal data according to the Privacy Policy.