Child pages
  • Using AWS to run OP5 Monitor
Skip to end of metadata
Go to start of metadata

A very easy way of getting started with OP5 Monitor is to deploy a Monitor server in The Cloud. This article shows one approach via the most famous cloud to date: Amazon Web Services (AWS). This guide will go from a first visit to the AWS Marketplace all the way to a running and checking OP5 Monitor server.

Preparing an AWS account and a new instance

  1. Create an Amazon account

    You may already have an AWS account and not even know it. If you've already shopped at Amazon, you can simply go to the AWS Marketplace, click on "Sign in", and use your Amazon credentials. If that doesn't work, simply click on "Create a new account" instead and follow the instructions.

  2. Once you've created an account or signed in, search for "OP5" in the Marketplace search box at the near top of the the screen. On the results page, click on the "OP5 Monitor" search result:

  3. You will arrive at the details page. Click on the orange button in the upper to subscribe (you can change the instance scale later):


  4. Click "Continue", and you will then reach the launching page:

  5. Here, you will need to choose in which region you want the server to run. In determining which region to choose, consider where your monitoring targets are located - either you choose the one that is

    * geographically closest to where you are


    * geographically closest to the things you are going to be monitoring

    Which one you choose depends on many things - network distance, latency, closeness to a particular hosting facility or user base, etc - but generally speaking, placing it close to where you are is a good idea.

    Then scroll down, and unless you've previously provisioned servers in the Amazon Web Services Cloud, you will see this:

  6. A key pair is used to access your Amazon Web Services instances via SSH, and you will need one for advanced administration of the Monitor machine.

    Click the link to visit the Amazon EC2 Console. A new tab will open, looking like this:

  7.  Click "Create key pair" and give your new keypair a name that you will use to identify it within Amazon Web Services. Once you've created your keypair, a download will start for a file named <your-keypair-name>.pem.

    Save this file in a secure place - it is the only way you can administer your instance, and you can't recover it if you lose it!

    You will be taken back to the key pair inventory, which will look something like this:

  8. You can now close the EC2 Management Console tab, bringing you back to the AWS Marketplace tab. If you reload the page, you'll notice that it has now discovered your new keypair and looks like this:

  9. Once you have a key pair specified, click "Launch with 1-Click". This brings you to a screen looking a lot like this one:

  10. Close this popup with the X icon in the top-right corner of the popup. This will bring you to this page:

  11. You now have an instance of op5 Monitor running on the Amazon Web Services Cloud!

    In order to be able to log in to your new, fresh instance, click "Manage in AWS Console". This will bring you to a page much like this:

  12. Here, you have two details that you will need in order to log into your new instance - the Instance ID, which in my case is i-d88a7136, and the Public DNS, which in my case is

    In order to log in to your new instance, copy the Public DNS, open a new tab in your browser and paste it into the address bar, followed by Enter.

    If you want more information on how to use the Amazon Web Services Cloud, this contains all the information you need to get started. 

Getting started with op5 Monitor

  1. When you've pasted the Public DNS into the address bar and pressed Enter, you will be sent to this page:

  2.  Click the op5 Monitor button, which brings you to this page:

  3. You will be prompted to create an account with administrator privileges the first time you access op5 Monitor. Input username and password and click Create account, which brings you to this page:

  4. This is the Host Wizard, the first thing you encounter when you log into Monitor (unless you later turn it off by unchecking "Always show this Host Wizard when I login"). Click Next, which brings you to this page:

  5. This is the Device Type page of the Host Wizard, where you choose the type of the device you want to monitor. Me, I scroll down a bit, selecting "Web Server", which makes the page look like this:

  6. I then click Next, which brings me to this page:

  7. Here, I type in the details of the server I want to monitor - in this case, I want to monitor the web server, referring to it as

    If I wanted to add more web servers, I'd just click "+ Add Host", and more fields would appear.

    I then click Next, which brings me to this page:

  8. Here, I have a choice of either saving my configuration and going on to view the new hosts that I've added, or saving my configuration and going back to adding more hosts through the wizard.

    Me, I'm happy with what I've done, and click "Save Configuration and View Added Hosts", which after some processing brings me to this page:

  9. Voila! You have now added your first host and your first service into your very own instance of op5 Monitor, running on the Amazon Web Services Cloud!


Further reading

For more information about op5 Monitor and tips about using the various features, here are some links to resources to learn more:

OP5 Monitor Documentation