Supported resources and requirements

AWS Compute Optimizer generates recommendations for Amazon Elastic Compute Cloud (Amazon EC2) instances, Amazon EC2 Auto Scaling groups, Amazon Elastic Block Store (Amazon EBS) volumes, AWS Lambda functions that meet the following Amazon CloudWatch (CloudWatch) metric and resource-specific requirements.

CloudWatch metric requirements

To generate recommendations, Compute Optimizer requires at least 30 consecutive hours of CloudWatch metric data from your resource. For more information about the metrics that are analyzed, see Metrics analyzed by AWS Compute Optimizer. If your resources have not accumulated sufficient metric data, then allow more time for resource recommendations to begin appearing in the Compute Optimizer console.

Note

Lambda functions don't require 30 consecutive hours metric of metric data. For more information about the Lambda function requirements, see Lambda function requirements.

If your resources have accumulated sufficient metric data, but recommendations are not yet showing up in the Compute Optimizer console, then the service might still be performing its analysis. It could take up to 12 hours to complete the analysis, after which time resource recommendations will begin appearing in the Compute Optimizer console.

Amazon EC2 instance requirements

Compute Optimizer generates recommendations for M, C, R, T, and X instance types in AWS Regions where these instance types are available. However, it does not generate recommendations for -g instance types powered by AWS Graviton2 processors (e.g., C6g), and for -n instance types that have higher network bandwidth performance (e.g., M5n). Compute Optimizer also does not generate recommendations for instances that use a different CPU manufacturer than the current instance.

If you’re running instances that use unsupported instance types, in addition to those supported by Compute Optimizer, the service generates recommendations only for the supported instances. To determine the supported Regions for each of these instance types, see Finding an Amazon EC2 instance type in the Amazon EC2 User Guide for Linux Instances.

Auto Scaling group requirements

Compute Optimizer generates recommendations for instances in Auto Scaling groups that are configured to launch and run M, C, R, T, and X instance types in AWS Regions where these instance types are available. However, it does not generate recommendations for -g instance types powered by AWS Graviton2 processors (e.g., C6g), and for -n instance types that have higher network bandwidth performance (e.g., M5n). Compute Optimizer also does not generate recommendations for instances that use a different CPU manufacturer than the current instance.

The Auto Scaling groups must also be configured to run a single instance type (i.e., no mixed instance types), must not have a scaling policy attached to them, and have the same values for desired, minimum, and maximum capacity (i.e., an Auto Scaling group with a fixed number of instances). Compute Optimizer generates recommendations for instances in Auto Scaling groups that meet all of these configuration requirements.

Amazon EBS volume requirements

Compute Optimizer generates recommendations for General Purpose SSD (gp2 and gp3), and Provisioned IOPS SSD (io1 and io2) EBS volume types that are attached to an instance. It also generates recommendations from General Purpose SSD (gp2) volumes to General Purpose SSD (gp3) volumes from the aforementioned volume types.

Data is only reported to CloudWatch when the volume is attached to an instance. Therefore, the volume must be attached to an instance for at least 30 consecutive hours to meet the 30 consecutive hour metric data requirement described earlier in this guide.

Lambda function requirements

Compute Optimizer generates memory size recommendations only for Lambda functions that have configured memory less than or equal to 1,792 MB, and that have been invoked at least 50 times in the last 14 days. Functions that don't match these requirements are given a finding of Unavailable, with a reason code of Inconclusive for functions that have configured memory greater than 1,792 MB, and Insufficient data for functions that have been invoked less than 50 times in the last 14 days.

Functions with a finding of Unavailable are not listed in the Compute Optimizer console, and Compute Optimizer does not generate recommendations for them.