Viewing the AWS Compute Optimizer dashboard - AWS Compute Optimizer

Viewing the AWS Compute Optimizer dashboard

The dashboard in the AWS Compute Optimizer console displays an overview of optimization findings for your AWS resources. Your resources are organized into findings classifications, and are separated into service-specific sections. For example, the dashboard shows the findings for your EC2 instances, Auto Scaling groups, EBS volumes, and AWS Lambda functions separately. Use the dashboard to identify the optimization opportunities for each resource type that is supported by Compute Optimizer.

The findings and recommendations are refreshed daily. They're generated by analyzing your resource’s specifications and utilization metrics over a period of the last 14 days. For more information, see Metrics analyzed by AWS Compute Optimizer. Keep in mind that findings and recommendations could take up to 12 hours to be generated, and sufficient metric data must be accumulated. For more information, see CloudWatch metric requirements.

Findings classifications

The findings classifications in the Compute Optimizer console provide an at-a-glance view of how your resources performed during the analyzed period. A percentage, and a count of your resources that are in each classification, are shown on the dashboard. The classifications differ based on the resource type. The following classifications apply to services and resources supported by Compute Optimizer.

EC2 instances

The following findings classifications apply to EC2 instances.

Classification Description

Under-provisioned

An EC2 instance is considered under-provisioned when at least one specification of your instance, such as CPU, memory, or network, does not meet the performance requirements of your workload. Under-provisioned EC2 instances might lead to poor application performance.

Over-provisioned

An EC2 instance is considered over-provisioned when at least one specification of your instance, such as CPU, memory, or network, can be sized down while still meeting the performance requirements of your workload, and when no specification is under-provisioned. Over-provisioned EC2 instances might lead to unnecessary infrastructure cost.

Optimized

An EC2 instance is considered optimized when all specifications of your instance, such as CPU, memory, and network, meet the performance requirements of your workload, and the instance is not over-provisioned. For optimized instances, Compute Optimizer might sometimes recommend a new generation instance type.

Note

For instances, Compute Optimizer generates finding reasons that provide a greater level of detail into why an instance was found to be under-provisioned, or over-provisioned. For more information, see Finding reasons in the Viewing EC2 instance recommendations guide.

Auto Scaling groups

The following findings classifications apply to Auto Scaling groups.

Classification Description

Not optimized

An Auto Scaling group is considered not optimized when Compute Optimizer has identified a recommendation that can provide better performance or cost for your workload.

Optimized

An Auto Scaling group is considered optimized when Compute Optimizer determines that the group is correctly provisioned to run your workload, based on the chosen instance type. For optimized Auto Scaling groups, Compute Optimizer might sometimes recommend a new generation instance type.

Note

For instances in Auto Scaling groups, Compute Optimizer generates finding reasons that provide a greater level of detail into why an Auto Scaling group was found to be not optimized. For more information, see Finding reasons in the Viewing EC2 instance recommendations guide.

EBS volumes

The following findings classifications apply to EBS volumes.

Classification Description

Not optimized

An EBS volume is considered not optimized when Compute Optimizer has identified a volume type, volume size, or IOPS specification that can provide better performance or cost for your workload.

Optimized

An EBS volume is considered optimized when Compute Optimizer determines that the volume is correctly provisioned to run your workload, based on the chosen volume type, volume size, and IOPS specification. For optimized resources, Compute Optimizer might sometimes recommend a new generation volume type.

Lambda functions

The following findings classifications apply to Lambda functions.

Classification Description

Not optimized

A Lambda function is considered not optimized when Compute Optimizer has identified that its configured memory or CPU power (which is proportional to the configured memory) is under-provisioned or over-provisioned. In this case, Compute Optimizer generates a recommendation that can provide better performance or cost for your workload.

When a function is not optimized, Compute Optimizer displays a finding reason of either Memory under-provisioned or Memory over-provisioned.

Optimized

A Lambda function is considered optimized when Compute Optimizer determines that its configured memory or CPU power (which is proportional to the configured memory) is correctly provisioned to run your workload.

Unavailable

Compute Optimizer was unable to generate a recommendation for the function. This could be because the function has not met the requirements of Compute Optimizer for Lambda functions, or the function does not qualify for a recommendation.

For this finding classification, Compute Optimizer displays one of the following finding reasons:

  • Insufficient data when the function does not have sufficient metric data for Compute Optimizer to generate a recommendation.

  • Inconclusive when the function does not qualify for a recommendation because the function has configured memory greater than 1,792 MB, or Compute Optimizer cannot generate a recommendation with a high degree of confidence.

Note

Functions with a finding of Unavailable are not listed in the Compute Optimizer console.

Viewing the dashboard

Use the following procedure to view the dashboard and the optimization findings for your resources.

  1. Open the Compute Optimizer console at https://console.aws.amazon.com/compute-optimizer/.

  2. Choose Dashboard in the navigation pane.

    By default, the dashboard displays an overview of optimization findings for AWS resources across all AWS Regions in the account that you are currently signed in to.

  3. You can perform the following actions on the dashboard:

    • To view the optimization findings for resources in another account, choose Account, and then select a different account ID.

      Note

      The ability to view optimization findings for resources in other accounts is available only if you are signed in to a management account of an organization, you opted in all member accounts of the organization, and trusted access with Compute Optimizer is enabled. For more information, see Accounts supported by Compute Optimizer and Compute Optimizer and AWS Organizations trusted access.

    • To filter findings on the dashboard to one or more AWS Regions, enter the name of the Region in the Filter by one or more Regions text box, or choose one or more Regions in the drop-down list that appears.

    • To clear the selected filters, choose Clear filters next to the filter.

    • To view optimization recommendations, choose the View recommendations link for one of the resource types displayed, or choose the number of resources listed next to a findings classification to view the resources for that classification. For more information, see Viewing resource recommendations.