Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Configure an Amazon Resource Optimization rule

Configure an Amazon Resource Optimization rule

The Cloud Management system tracks usage metrics to help you to identify discovered resources that are underutilized. Configure values for the metrics in a resource optimization rule (for example, Volume IOPS, CPU usage, and network I/O) that can flag a resource as underutilized.

Before you begin

Role required: cloud_admin

About this task

Resource Optimization allows you to generate reports that help you to better manage or utilize resources. The reports list underutilized resources. You can configure rules to schedule when to generate a report. To use the resource optimization feature, Amazon resources must already be discovered and imported into the instance. Use the Amazon Web Services account record form to perform Discovery.

Amazon Resource Optimization allows you to track Amazon resource usage through the Amazon CloudWatch API.

The application supports optimization of the following resources:

  • AWS VMs
  • Elastic Block Store (EBS)
  • Elastic Load Balancing (ELB)
Note: There is a potential charge to use this feature.
Note: You cannot create a new rule. You can, however, unselect the Active check box to stop tracking metrics for a particular resource.


  1. Navigate to Amazon AWS Cloud > Administration > Resource Optimization Rules and select a rule.
  2. Update the rule as needed and then click Update.
    Table 1. Resource Optimization Rules form, common fields for all rules
    Field Description
    Name Name of the rule.
    Over a period of days Number of consecutive days that are combined to calculate the metric.
    Note: CloudWatch metric data is kept for two weeks. A rule that tries to fetch data older than two weeks will not return data. The maximum recommended period for any rule is 14 days.
    Active If selected, the rule is applied to the data.
    Workflow The workflow that runs the rule.
    Table 2. Unique fields for the EBS rule
    Field Description
    Volume IOPS < Threshold value that is triggered once the volume IOPS is below this number.
    Include unattached volumes If selected, unattached volumes will be included.
    Table 3. Unique fields for the EC2 rule
    Field Description
    CPU Usage (%) < Threshold for percentage of CPU usage.
    and Network IO (MB) < Threshold for size of the Network IO.
    For number of days Number of days to use for the rule
    Table 4. Unique fields for the ELB rule
    Field Description
    Number of attached healthy instances Threshold for the number of attached healthy instances.
    No instance attached If selected, a report will be generated for the ELB - Unattached category.
    Number of requests Threshold for the number of requests.


There are three default rules:

EBS: Volume IOPS < 1 over a period of 7 days.

EC2: CPU Usage (%) < 10 AND Network IO (MB) < 5 for 4 days over a period of 14 days.

ELB: Number of requests < 100 over a period of 7 days.

If the condition is met, that VM will be considered as an underutilized resource and will show up in the Self-Service > Cloud Admin Portal Resource Optimization section.

If that VM is assigned to a user, it will also show up on the Resource Utilization report in the Self-Service > MY Virtual Assets Resource Optimization section for that user.