Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Server & Application Monitor (SAM) > SAM Documentation > SAM 6.7 Administrator Guide > Monitor cloud instances with Cloud Infrastructure Monitoring > Configure cloud infrastructure monitoring

Configure cloud infrastructure monitoring


Updated: 2-21-2017

To get started with cloud monitoring, add a cloud account to Cloud Infrastructure Monitoring. When adding an account, add cloud access IDs, test the connection, and select instances to monitor. Cloud monitoring also includes an automatic monitoring option to actively discover new instances and VMs launched from the account, like an always active discovery job. You can modify any of these account settings and access IDS through Cloud account management options.

By default, a few options are enabled for cloud infrastructure monitoring. Modify these settings as needed when adding an account:

  • Automatically monitor and add instances launched using the account, like an Orion discovery job.
  • Enable CloudWatch API polling for metrics from AWS.

    Monitoring metrics polls Amazon CloudWatch APIs and consumes free requests. CloudWatch provides 1 million free requests per month. If you disable CloudWatch monitoring, only the status metric polls until enabled.

  • CloudWatch polling frequency in minutes. The default amount is 5 minutes.

Cloud infrastructure monitoring supports AWS accounts requiring information:

If you need an AWS IAM account, see Amazon documentation and Learn more about Amazon EC2 credentials for cloud monitoring for adding policies and requirements.

You can add up to a total of 10 AWS accounts through Cloud Infrastructure Monitoring Settings.

  1. On the Orion Web Console, select My Dashboards > Cloud.
  2. Locate the Getting Started: Monitor Cloud Instances and click Monitor My Cloud Instances.


    A page displays with a walk-through of steps.

    SAM and integrated VMAN monitor the selected instances without managing them as nodes. To manage as a node with a selected polling method, see Manage the cloud instance as a node


  3. Click Get Started.

    A page displays to add an AWS account and configure cloud settings.

  4. Enter a name to display in the Orion Web Console for the account.
  5. 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.
  6. 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.

  7. 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.

  8. 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 the Orion Platform. The default is enabled.
    • CloudWatch Instance Polling Frequency: sets the polling frequency for the instances associated with the account. The default is 5 minutes.
  9. Optionally, you can access and manage Orion alerts from the page.

    Depending on your account limitations, you may not have access to this option.

    To open the Alert Manager, click the link. You can modify, enable, and create alerts anytime through Alerts & Activity > Alerts and select Manage Alerts. For more information, see Alerts and events for cloud monitoring.

  10. Click Next.

    A page opens to select instances for monitoring accessed with the AWS account IDs and Amazon APIs.

  11. 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. The Do Not Monitor option disables monitoring for the selected instances.

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

    All metrics poll using Amazon API calls, including CloudWatch. All monitored metrics count against the 1 million free requests provided by Amazon. Any requests beyond 1 million will incur additional costs. Other tools in your environment making CloudWatch API calls also count against your free requests limit.

  12. Click Save.
  13. Optionally, you can manage the instance as a node and monitor with Orion agents.

Orion user account settings

The cloud options available for Orion user accounts include:

  • Display the Cloud Summary view
  • Set details pages by default.

To hide or configure a specific view for summary and instance information, you can modify Orion account settings.

To restrict Orion users from management options for a managed cloud instance node, modify the AWS IAM account permissions set in AWS console. For details, see Learn more about Amazon EC2 credentials for cloud monitoring.

  1. In the Orion Web Console, click Settings > All Settings, locate the User Accounts section, and click Manage Accounts.
  2. Select an account and click Edit.
  3. Locate and expand Cloud Monitoring Settings to configure the page to display for the Cloud Summary View.

    The Default setting opens the Cloud Summary page.

  4. Expand Virtual Infrastructure Monitor Settings and locate the Cloud Instance Details View option.

    Set this option to Default to display the Cloud Instance Details page if monitored or Node Details - Cloud if managed as a node.

  5. Click Submit.
Last modified