Geneos on Amazon Web Services Cloud

Overview Copied

This guide provides you the list of considerations and recommendations when deploying Geneos on Amazon Web Services (AWS). In addition, this guide defines the requirements needed to deploy Geneos on Amazon Elastic Compute Cloud (EC2).

The illustration below shows a running Geneos environment with Gateway and Netprobe components that are connected to AWS:

Prerequisites Copied

Having a basic understanding of how to download, run, and configure a Netprobe and Gateway is required before you can proceed. For how to configure and install these components, refer to the following guides:

The following requirements for both Geneos and Amazon Web Services environments must be met prior to the setup of this deployment.

Geneos connection requirements Copied

This section provides the requirements for connecting one Geneos component to another when deploying to AWS. EC2 instances may not be able to access machines in an internal network, unless those machines are set up with a public IP address.

Amazon Web Services EC2 system requirements Copied

The system requirements for Amazon Elastic Compute Cloud (EC2) are available on their website. Ensure that the EC2 instances have instance types that meet the machine requirements for Gateway and Netprobe.

To check the system requirements for Gateway and Netprobe, refer to the following guides:

The EC2 Security Groups, as well as the corresponding subnets, routing tables, internet gateways, should allow access to the ports. Below are some recommendations:

Performance and cost considerations Copied

Be aware that the amount of traffic between AWS and an internal network has an implication on the cost . The following are instances which involve high traffic:

Example setup and dataviews Copied

The following procedures list how to set up your AWS instance and the configurations required to connect to Geneos components.

Connect to the EC2 instance through SSH Copied


Ensure that your EC2 instance is running and that you already obtained the license key and host IP address. To know more about EC2 instances, visit the Amazon Web Services website.

To configure your AWS instance, follow these steps:

  1. Download an application that allows you to transfer files to your AWS instance. In this example, MobaXterm is used to connect through a Secure Shell (SSH).
  2. Connect using the remote host and username of your running AWS instance.
  3. Provide the private key that is used to generate the EC2 instance.
  4. Click OK.

Provide these information in the Session settings screen:

This shows the fields during the configuration of your session settings:


There are other applications that you can use to connect through a Secure Shell (SSH).
Field Description
Remote host Hostname or IP address of the EC2 running instance you created in Amazon Web Services.
Specify username centos or depending on the AMI you used to generate EC2 instance.
Port Default value: 22
Private Key Path to the downloadable file received when you generated the EC2 instance in Amazon Web Services.

Download the Gateway and Netprobe packages Copied

The procedures on how to download these Geneos components are available to their corresponding documentation guides. Open the following resources:

Once these files are saved on your local machine, follow these steps:

  1. Connect to your EC2 instance using SSH.
  2. Copy the Gateway binaries to your EC2 instance.
  3. Copy the Netprobe binaries to your EC2 instance.

In summary, this section only asks you to migrate the binaries of Gateway and Netprobe into the EC2 instance.

Set up Gateway Setup Editor Copied


As part of the Geneos connection requirements, ensure that your Gateway and Netprobe are up and running properly.

To connect Gateway to the Netprobe on EC2 instance, follow these steps:

  1. Open Active Console.
  2. Connect to the Gateway that is running on the EC2 instance.
  3. Create a probe in Gateway Setup Editor.
  4. Provide a name and hostname.
  5. Add a defined probe to a managed entity.
  6. Create a sampler which depends on what you wish to monitor or use.
  7. Click Save to apply your changes.

Provide the following information in the Probes section in Gateway Setup Editor:

This dataview in Active Console monitors the CPU sampler of the AWS instance:

Field Description
Name Name of the probe.
Hostname Hostname or IP address of the EC2 running instance you created in Amazon Web Services.
Port Default value: 7036
["Geneos"] ["Geneos > Gateway"] ["User Guide"]

Was this topic helpful?