Using AlertSite UXM > Private Nodes > Setup > Deploying to Amazon EC2

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

Requirements

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)

If you want to launch Private Node Server in a region other than US West (Oregon), first, you need to contact Support or your Sales representative and tell us your AWS account ID and the desired AWS region. We will share the AMI with your AWS account and let you know when it is ready for use.

Considerations

Launching Private Node Server From an AMI

  1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
  2. From the top menu, select the US region where you want to launch Private Node Server.

    Select AWS region

  3. On the left, select AMIs.
  4. Change the filter to Public Images and filter by the owner ID 693228085634. You should see the AMI named SmartBear Private Node <version>.

    Finding Private Node Server AMI

  5. Select the AMI on the list and click Launch. If there are multiple versions, launch the latest version.

    Launch AMI

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

    Choose Instance Type

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

    Configure Instance Details

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

    Add Storage

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

  10. Now you need to configure a security group that will allow communication between your Private Node Server and AlertSite platform. 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 Purpose
    SSH TCP 22 Anywhere 0.0.0.0/0 For remote support on your Private Node Server.
    HTTPS TCP 443 Anywhere 0.0.0.0/0 To access the Control Panel (web interface) of Private Node Server.
    HTTP TCP 80 Anywhere 0.0.0.0/0 To access the Control Panel (web interface) of the Private Node Server. Note that http:// will automatically redirect to https://.

    If you are launching your instance into a VPC network, you also need to add the following Outbound Rules:

    Type Protocol Port Range Destination Purpose
    HTTPS TCP 443 204.2.244.25 (privateagent.alertsite.com) To register your private node and ServerAgent in AlertSite, to send monitoring data and to collect configuration updates from AlertSite.
    SMTP TCP 25 Anywhere To send email alerts (if you will not use a mail relay host).
    Custom TCP Rule TCP 4892 The IP addresses of AlertSite locations chosen for ServerAgent reporting. In order for ServerAgent to report Private Node Server health status and performance data to AlertSite.

    Note: You can skip this rule for now and add it to the security group later when configuring ServerAgent.

    Additionally, the protocols, hosts and ports of any external websites you want to monitor.

    Configure Security Group

  11. Click Review and Launch.
  12. Review the instance launch details and click Launch.
  13. 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

Notes:

 

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

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