How to use the Amazon EC2 AMI for GroundWork Monitor 7.0

You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

GroundWork Monitor 7.0 bundled with RedHat in the Amazon Cloud (EC2)

Last updated: December 12th 2013
GroundWork Monitor 7.0 Enterprise is available as a ready-to-run 64-bit Amazon Machine Image (AMI) bundled with RedHat 6.5. It is already licensed with a 50 device CORE license.

Quick-start information

If you're an experienced EC2 users this the information you'll need:
AMI name: ami-xxxxxxx.
Minimum instance size: Large
Recommended instance size: Large
Administer your instance using the web interface:e.g.
The instance uses EBS for persistent storage. Amazon EBS I/O and storage charges apply in addition to CPU time. Amazon charges apply to the RedHat OS
Application login user name/password: admin/admin
Operator login user name/password: operator/operator
PostgreSQL postgres password: postgres

Getting Started With GroundWork Monitor 7.0 and Amazon EC2 Cloud

This guide walks through getting started with GroundWork Monitor 7.0 in the Amazon EC2 cloud with a completely hosted, private copy.

Get an Amazon Account

If you have not already created an account on Amazon's EC2 service please do so now. Amazon will charge your account for the resources you consume on their service; GWOS does not receive any of this money.
You can sign up for a new account at:

Get the AMI

The GroundWork Monitor 7.0.1 EC2 AMI image is an Instance Store AMI you purchase from Amazon. You can, of course, launch it, modify it, and bundle it into your own copy.

  • The instance has been left essentially as a clean, patched install of GWMEE 7.0.1. The Network Notification service is ON, and will submit anonymous usage data back to GroundWork when launched. A valid license is required for use and is preinstalled.
  • As with all EC2 instances, this one should be launched with your keys, which will give you root access to the console. See Amazon documentation for key setup.
Locating the GroundWork Monitor Enterprise 7.0.1 AMI
  • Log in to your Amazon account
  • Choose the Region where you wish to launch
  • Go to
  • Unable to render embedded object: File (ami70-1.png) not found.
  • Select the AMI and Launch an instance.
  • Configure the instance to be created:
    In particular the following choices are recommended:
  • Create a single instance
  • Select an availability zone
  • Instance type is Large (m1.large 7.5GB)
    Unable to render embedded object: File (ami70-2.png) not found.
    Follow the on screen instructions. Default values are fine.
    Create Key Pair:
  • A user can use an existing, previously created key pair, create a new pair, or proceed without a key pair.
  • To configure the EC2 instance a user must have access to the console and therefore at this point the user has to create the  SSH keys if they don't exist already. Please follow the onscreen instructions on how to create keys.
  • User can create Security Groups defining access to the EC2 instance. Access should be configured so that SSH (port 22), HTTP (port 80), HTTPS (port 443) and Ntop Web (port 82) are open.
  • The instance is configured with the RedHat firewall (iptables) running with these ports open. You may wish to adjust "iptables" depending on your needs after you have launched the instance and connected via SSH.
    Launch the Instance

    Press the "Launch" button
    Click on "Instances" in the left side Navigation panel to check the instance creation process:
    After a few minutes the status will change from "starting" to "running" The GroundWork application will then launch for the first time, this process takes a few minutes after the instance begins running.

    Configuring the public access point for the GroundWork portal*

    The AMI instance has a private IP Address and a Public DNS. The Public DNS is used to access the GroundWork Monitor portal. The GroundWork Monitor web portal is properly configured with the Public DNS name when you bring the instance up.

    Access the GroundWork Monitor.

    Get the application by opening a new browser tab at the "public DNS" address of the newly created instance.
    Unable to render embedded object: File (ami70-3.png) not found.
    Login using the default administrator credentials: Username: admin
    Password: admin
    You're now ready to explore GroundWork Monitor 7.0.1

    Be sure to change the password for the admin user, and to either disable or change the other default web accounts (User and Operator).
    Changing the default passwords is highly recommended. Do so as the Admin user. From the main protal screen choose (Group -> Organization -> Users and Groups Management)
    This is the panel you will see, click on the User Management, Account Info tabs and check the box for Change Password
    You can now configure monitoring of your cloud and web resources, or any hosts or applications reachable from your EC2 instance.
    Unable to render embedded object: File (ami70-5.png) not found.
    The ami we produced is set for the most popular Time Zone, on the Eastern Seaboard of the United States. We applied the timezone adjustment to PHP referred to in technical bulletin 6.3-3 Timezone for php must be set in 6.3 so that the ami will work when launched in the Eastern US availability zones, but you may adjust this parameter for whatever time zone you launch the AMI in. Follow the instructions in the technical bulletin if you need to launch the ami in another time zone.

Learning about GroundWork Monitor

Check out the "Getting Started with GroundWork Monitor" training course on our web site .
Need to justify a monitoring investment?  Try our whitepapers

Note for VPC and other Non EC2 Deployment

Only if you plan to use your instance in a different way than EC2 will change be needed. For instance you might be launching the AMI in a VPC. In that case the Public EC2 address might be inappropriate. For normal EC2 use ignore the next section.

Change Address

You can make these changes manually by first commenting the script that does it automatically and then editing the necessary files. To do this you need console access to the instance, by using an ssh client (Linux native, Putty for Windows). Prior to connecting to the instance you must:

  • Download the key pair for the instance to the workstation you will use to configure the GroundWork system
  • Make sure that the security group includes an entry for ssh connection from the Source IP of your workstation so the Amazon AWS will allow the connection.
  • Make sure that the security group includes an entry for http access from the Source IP of your workstation
    Manual address configuration steps:
  • ssh or putty to GroundWork Monitor instance using the SSH keys. You log in as user "ec2-user". Assume root privileges by "sudo su -".
  • The next step clears the automatic feature from operating. This is a trivial change.
  • \-bash-3.2# sed -e /^/#/ -i /etc/init.d/groundwork

    Now change the following files, editing in place the address that will be associated with running GroundWork (for example in a VPC this might be the internal IP address).


    You will see many places in these 6 files where the public DNS name appears. It is something like "". Replace that with the hostname or ip address dictated by your circumstances. This will usually be what is returned when you type "hostname -f" or "ifconfig -a". Below you see an example of lines that must be changed.

  • If you made changes to these files you must restart the GroundWork services (gwservices):
    -bash-3.2# /etc/init.d/groundwork restart gwservices
    Stopping GroundWork Services:                               [ OK ]
    Checking for GroundWork Services:
        JBoss is not running
        svscan is not running
        dumblogs are not running
        supervise is not running
        Feeders are not running
        Spoolers are not running
        nagios2collage_socket is not running
        nagios2collage_eventlog is not running
        fping_process is not running
        gdma_spool_processor is not running
    Starting GroundWork Services:
        Connecting to Foundation
        Listener is not ready to accept data feeds ...
        Listener is not ready to accept data feeds ...
        Listener is not ready to accept data feeds ...
        Listener is not ready to accept data feeds ...
        Listener is ready to accept data feeds ...
        Listener services are available.
        Trying auto login to portal...
        Initializing Statusviewer Cache...
        Monitor Status cache initialized
    GroundWork Services start                                   [ OK ]
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.