How to access OpManager on AWS using EC2 instance?

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

You can use OpManager in AWS using one of the 2 methods:

By purchasing and running OpManager AMI from AWS store

Before you begin, please purchase OpManager AMI from here.

  • 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 required hardware requirements are met. Click here to view the recommended specifications before proceeding.
MetricCriteria
EC2 Instance Typem6i.xlarge or above
Operating SystemWindows 11 (or) Windows Server 2016 and above
Storage20 GB (minimum)
  • 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.
  • Use the RDP session to log into the instance.
  • 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.
  • In the Services app, check whether the following service is running: ManageEngine OpManager.
  • If ManageEngine OpManager service is in a running state, go to your browser and connect to OpManager'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)
  • Log in to OpManager using the following credentials:
    • Username: admin
    • Password: --Instance ID--

By installing OpManager in a separate EC2 instance

  • Remotely connect to your EC2 instance
  • In that instance, open your web browser
  • Download and install OpManager.
  • Login to OpManager using username as admin and password as admin.

Cloud VM Requirements

+

Important Note:

  • Ensure that the necessary ports in your OpManager instance are not blocked for proper functioning of OpManager and its add-ons (this step is a must for running OpManager from AMI as well as for running OpManager from an EC2 instance). Click here to view the full list of required ports.
  • Ensure that the instance's Public IP/DNS is not blocked by any firewall and is accessible to all devices in your network.
  • When you access OpManager 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 & traps to the OpManager server, 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. This applies to both methods above.