Running Private Node Server on Amazon EC2

Amazon Web Services (AWS) is a suite of cloud services and infrastructure, including online-hosted virtual machines, storage, networking and more. It allows users to deploy a virtual server with the required configuration with just a few clicks.

SmartBear provides a preconfigured AMI (Amazon Machine Image) for users who want to run Private Node Server in the Amazon EC2 cloud. This guide explains how you can launch an instance of Private Node Server.

In This Guide


You must have an Amazon Web Services (AWS) account before deploying Private Node Server on Amazon EC2.

Sign in or create an AWS account.

Region Availability

Private Node Server is currently available in the following AWS regions:

Code Name
us-east-1 US East (N. Virginia)
us-east-2 * US East (Ohio)
us-west-1 * US West (N. California)
us-west-2 US West (Oregon)

* To launch Private Node Server in the Ohio or N. California region, first you need to contact Support or your Sales representative and let us know your AWS account ID and the AWS region you want to use. We will share the AMI with your AWS account and notify you when it is ready for use.


Launching Private Node Server From an AMI

  1. Open the Amazon EC2 console at
  2. From the top menu, select the US region where you want to launch Private Node Server.

    Select AWS region

  3. The next steps depend on the region you selected:

  4. Choose the instance type that meets the requirements for your desired monitoring capacity, then click Next: Configure Instance Details.

    Choose Instance Type

  5. On the next screen, you can select the network, subnet and other parameters. Once done, click Next: Add Storage.

    Configure Instance Details

  6. (Optional.) Add additional storage to your instance, if needed. Then click Next: Tag Instance.

    Add Storage

  7. Name your instance and click Next: Configure Security Group.

  8. Now you need to configure a security group that will allow access to the private node’s Control Panel (web interface). To do that, select Create a new security group and enter a name and description for the group.

    Add the following rules for inbound traffic:

    Type Protocol Port Range Source
    HTTPS TCP 443 Anywhere


    Specific IP addresses from which you will access the private node’s Control Panel.
    HTTP TCP 80 Anywhere


    Specific IP addresses from which you will access the private node’s Control Panel.

    Configure Security Group

  9. Click Review and Launch.
  10. Review the instance launch details and click Launch.
  11. When you are asked to specify a key pair, select Proceed without a key pair, select the acknowledgement check box and click Launch Instances.

Your Private Node Server instance is now running.

Important: You will be charged for each hour or partial hour your instance is running, from the moment it boots until you terminate it. When you no longer need the instance, be sure to terminate it as explained below.

Getting the Instance IP Address

You need to know the IP address of your Private Node Server to access its web interface (Control Panel). To find the IP address:

  1. In the Amazon EC2 console, select Instances on the left.
  2. Select your running instance.
  3. Find the Public IP value in the table, or in the Description pane at the bottom.

    IP address



Once you know the IP address, navigate to https://<ip address> in your browser. Ignore the certificate warning and log in as insiteadm / 1nSitePa$$. You will see the Private Node Server Control Panel informing you that the node is not registered.

Private Node Server Control Panel

Completing the Configuration

There are a few more things you need to do to get your instance truly up and running:

Resizing an Instance

You can add more CPUs, memory and storage to your existing Private Node Server instance later, if needed. For more information, see Resizing Your Instance in Amazon AWS documentation.

Terminating an Instance

When you no longer need an instance, you can terminate (delete) it. Historical monitoring data is stored in AlertSite, so terminating an instance will not delete its monitoring data, unless you also delete the corresponding location from AlertSite.

To terminate an instance:

See Also

© 2017 SmartBear Software. All rights reserved.      Terms of Use · Privacy Policy