Skip to content

Installing in an Amazon Web Services region

Use the procedures on this page to install the Zenoss Cloud Collector virtual appliance as an Amazon Web Services (AWS) Elastic Compute Cloud (EC2) instance.

Prerequisites

To perform these procedures, you need:

  • An Amazon Web Services account with permission to run an m4.xlarge instance in EC2.

  • An Amazon Virtual Private Cloud (VPC).

  • A named Amazon EC2 key pair.

  • The ID of the Zenoss Cloud Collector AMI to use.

    The image ID varies by region; for more information, please contact your Zenoss Services representative.

Procedures

To install in an AWS region, first create an instance and then configure the instance.

Creating an instance

Follow these steps:

  1. Log in to AWS and open the EC2 Dashboard page.

  2. Under Create Instance, click Launch Instance.

  3. In the left column of the Step 1 page, click Community AMIs. If any filters are selected, deselect them.

  4. In the search field, enter the ID of the Zenoss Cloud Collector AMI.

    The current AMI IDs for the latest images are:

    Region AMI ID
    eu-west-2 ami-05b80174d864e05cb
    eu-central-1 ami-03cc40e06d53fb502
    us-east-1 ami-0d81fade3d00472a6
    us-east-2 ami-0f4045d19b1ad73c7
    us-west-1 ami-00375fedef3e2ff7f
    us-west-2 ami-087d4ece251e77feb

    Other AWS regions

    To gain access to a Zenoss Cloud Collector AMI in an AWS region not included in the preceding table, please contact Zenoss Support.

    Warning

    The name of the image (zenoss-collector) may be different from the one shown in the preceding screenshot. By relying on the ID in the preceding table, you're sure to have the correct, up-to-date image.

  5. Click Select.

  6. On the Step 2 page, select the m4.xlarge instance type (4 CPU, 16GB RAM, EBS storage).

  7. At the bottom of the page, click Next: Configure Instance Details.

  8. On the Step 3 page, configure the instance.

    1. In the networking area, choose the VPC and subnet that contains the devices to monitor.

      A public IP address is not required.

    2. In the Network interfaces section, use the default configuration.

    3. At the bottom of the page, click Next: Add Storage.

  9. At the bottom of the Step 4 page, click Next: Add Tags.

    The default storage of an m4.xlarge instance is sufficient.

  10. Optional: On the Step 5 page, add one or more tags, if desired.

  11. At the bottom of the Step 5 page, click Next: Configure Security Group.

  12. Optional: On the Step 6 page, create or select a security group.

    Add a specific source IP address to the SSH rule, or a range of source IP addresses, if desired.

    At the bottom of the Step 6 page, click Review and Launch.

  13. On the Step 7 page, review the instance details, and then click Launch.

  14. In the key pair dialog box, select a named key pair to use for gaining access to the collector console, and then click Launch Instances.

Configuring a collector instance

Follow these steps:

  1. Log in to AWS and open the Instances page.

  2. Select the instance you created in the previous procedure, and then give it a name.

  3. When the Status Checks column shows 2/2 checks and a green check mark icon, scroll down to the Description area.

  4. Review the networking requirements and edit the security group as required.

    By default, AWS allows all outbound connections.

Optional: Set additional DNS search domains or SSH keys

You can customize DNS resolution for your virtual machine and grant access to additional users. The following options are supported:

  • Additional DNS forwarding/DNS search domain entries
  • A default resolver other than the one provided by AWS
  • Additional SSH public keys

Example

For example, you wish to enable the following options for your virtual machine:

  • Forward DNS queries for *.example.com and *.example.org to the 203.0.113.4 and 203.0.113.5 resolvers
  • Forward DNS queries for *.myorg.example.net to the 198.51.100.253 resolver
  • Forward all other queries to the 192.0.2.2 and 192.0.2.3 resolvers
  • Grant access to the private SSH keys associated with public_key1 and public_key2 (through the ccuser account)

To configure the options, create the following JSON object:

{
    "dns-forwarding": [
        {
            "dns-search": ["example.com", "example.org"],
            "dns-servers": ["203.0.113.4", "203.0.113.5"]
        },
        {
            "dns-search": ["myorg.example.net"],
            "dns-servers": ["198.51.100.253"]
        }
    ],
    "default-dns-servers": ["192.0.2.2", "192.0.2.3"],
    "sshkeys": [ "public_key1", "public_key2"]
}

Then, add the object to the user data section of your virtual machine configuration in the AWS web console.

Procedure

Follow these steps:

  1. Create a JSON object that includes the options you wish to enable.

    See the previous section for an example JSON object.

  2. In the AWS web console, navigate to your virtual machine, then click on Actions > Instance settings > Edit user data.

    The AWS console displays the submenu on the left.

  3. In the New user data area, configure your virtual machine.

    1. Click Modify user data as text.
    2. In field below the control you clicked, paste your JSON object.

  4. At the bottom of the page, click Save.

  5. Reboot the virtual machine.

Next step

Configure the login password and connect to a Collection Zone (Initializing a collector appliance).