Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.4 Administrator Guide > Monitor cloud instances with Cloud Infrastructure Monitoring > Cloud account management

Cloud account management

 

Updated: 2-21-2017

When you add a cloud account, SAM and integrated VMAN access the cloud service to provide a list of instances and volumes for monitoring. Through the Cloud Account page, you can manage the configuration settings and information for these accounts, select cloud instances and VMs to monitor, and remove accounts from monitoring.

Cloud Infrastructure Monitoring uses the cloud account to access instances and volumes, poll for metrics through the cloud service API, and issuing management comments. The feature supports up to 10 AWS accounts, up to 1,000 monitored instances, and up to 1,000 managed cloud instance nodes.

We recommend planning your monitoring for best performance and usage of your CloudWatch resources. The closer you meet or exceed supported Orion monitoring amounts may affect performance and poller load.

Through the page, you can:

Access Manage Cloud Account page

You can access cloud accounts through Settings > All Settings > Product Specific Settings or using the Cloud Infrastructure Monitoring Settings link in the Cloud Summary page.

  1. In the Orion Web Console, select Settings > All Settings.
  2. In Product Specific Settings, select the Cloud Infrastructure Monitoring Settings link.

    A page displays with all the configuration and system options you need to manage cloud settings: Add Cloud Accounts, Manage Cloud Accounts, Retention Settings, and Edit Global Thresholds.

  3. Select Manage Cloud Accounts.

    The Cloud Accounts page displays with options to add and remove accounts, edit properties, and select instances for monitoring.

Directly through the Cloud Accounts page, you can also click Auto-monitoring on and off through the account List.

File:Success_Center/Reusable_content_-_InfoDev/SAM/Cloud_Reuse/Cloud_account_management/cloud-automonitoring.png

Add an additional cloud account

Add up to 10 AWS cloud accounts for monitoring. Each account provides access to instances and volumes for cloud monitoring.

Cloud infrastructure monitoring supports AWS accounts with the following settings and information:

  • Amazon Web Services (AWS) IAM user accounts with assigned permissions and group membership for CloudWatch metrics
  • AWS Access Key ID and Secret Address Key

You can add AWS accounts using the AWS IAM account access IDs. If you need these IDs, access the AWS console and make note of the access information for the account:

  1. Log in to the AWS Console.
  2. Click Account > Security Credentials.
  3. Scroll down to Access Credentials.

Each account requires a set of permissions to poll data and management cloud instances. SolarWinds recommends modifying these permissions before adding the account. For JSON permissions and instructions, see Learn more about Amazon EC2 credentials for cloud monitoring.

  1. On the Cloud Accounts page, click Add Cloud Account.

    The Add a Cloud Account to Monitor page displays.

  2. Enter the AWS Access Key ID and Secret Address Key located in the AWS console. If you need these values, make note of the access information through the AWS console:

    1. Log in to the AWS Console.
    2. Click Account > Security Credentials.
    3. Scroll down to Access Credentials.
  3. Optionally, enter a description to help identify the account.

    Use this description to keep track of the IAM user accounts added. The Orion display name and AWS account name can differ.

  4. Click Test Connection to verify the access keys to AWS.

    If issues occur, check the access keys and IAM user account in the AWS console.

  5. Optional, modify the settings for the following features:

    • Automatic Monitoring: automatically adds instances for monitoring when launched for the account. This feature acts as a discovery job detecting new instances. These instances add for monitoring. To add as nodes, use the manage as node option per Instance Details page. The default is enabled.
    • CloudWatch Instance Polling: enables CloudWatch API polling for metrics through AWS into SAM and integrated VMAN. The default is enabled.
    • CloudWatch Instance Polling Frequency: sets the polling frequency for the instances associated with the account. The default is 5 minutes.
  6. Click Next.

    A page opens to select instances for monitoring.

  7. Select instances and click Monitor to enable monitoring.

    Filtering options include the state, region, availability zone, type, platform (or OS), and monitoring state (on/off). From the list of instances, select the Monitoring On option to on to monitor. Do Not Monitor disables monitoring.

    If an instance is not available, an icon File:Success_Center/Reusable_content_-_InfoDev/SAM/Cloud_Reuse/Cloud_account_management/cloud-instance-notavailable.png displays on the instance.

    Data polls and displays according to the configured polling interval.

    All metrics poll using Amazon API calls, including CloudWatch. All monitored metrics count against the 1 million free requests per month provided by Amazon. To see your current calculated free request usage, see the cloud account properties after adding and polling the account.

  8. Optionally, you can access and manage alerts from the page.
  9. Click Save.

Edit account properties

Modify access IDs and options for a selected, existing cloud account. Run a test connection when changing any access IDs for an account.

  1. On the Cloud Accounts page, select an account from the list.
  2. The account edit properties page opens with populated values.

    The page also displays a calculated amount of approximate Amazon CloudWatch requests used for the month under the Enable CloudWatch API Polling option. AWS provides the value at the time of editing the properties.

  3. Modify settings as needed.

    If you modify access keys, click Test Connection to verify the changes.

  4. Click Submit.

Choose Instances/VMs to monitor

If you have disabled the option for automatically monitoring instances launched by an account or stopped monitoring selected instances, this option allows you to select and monitor specific instances. These instances do not count against your SAM and integrated VMAN licenses.

Monitored instances poll using Amazon API calls, including CloudWatch. All monitored metrics count against the 1 million free requests provided per month by Amazon. Any requests beyond 1 million will incur additional costs. To see your current calculated free request usage, see the cloud account properties.

  1. On the Cloud Accounts page, select an account from the list.
  2. Click Choose Instances/VMs.

    The Orion Platform accesses the AWS account and provides a list of instances for monitoring. Instances currently monitored have a green monitoring state.

  3. Select instances and click Monitor to enable monitoring.

    Filtering options include the state, region, availability zone, type, platform (or OS), and monitoring state (on/off). From the list of instances, select the Monitoring On option to on to monitor. Do Not Monitor disables monitoring.

    If an instance is not available, an icon File:Success_Center/Reusable_content_-_InfoDev/SAM/Cloud_Reuse/Cloud_account_management/cloud-instance-notavailable.png displays on the instance.

    Data polls and displays according to the configured polling interval.

  4. Click Save.

To stop monitoring a cloud instance, click the Monitoring On/Off button per instance.

Remove Account

When you remove an AWS account, any instances are also removed from monitoring. Node management?

  1. On the Cloud Accounts page, select an account from the list.
  2. When prompted, select to remove the account.

When you remove an account, you no longer have access to monitor selected instances and volumes. If you have managed the cloud instances or applications on the instances as nodes, the Orion Platform prompts you with additional options.

Last modified
07:30, 14 Mar 2017

Tags

Classifications

Public