Paws::ComputeOptimizer::InstanceRecommendation
This class represents one of two things:
Arguments in a call to a service
Use the attributes of this class as arguments to methods. You
shouldn't make instances of this class. Each attribute should be used as a
named argument in the calls that expect this type of object.
As an example, if Att1 is expected to be a
Paws::ComputeOptimizer::InstanceRecommendation object:
$service_obj->Method(Att1 => { AccountId => $value, ..., UtilizationMetrics => $value });
Results returned from an API call
Use accessors for each attribute. If Att1 is expected to be an
Paws::ComputeOptimizer::InstanceRecommendation object:
$result = $service_obj->Method(...);
$result->Att1->AccountId
Describes an Amazon EC2 instance recommendation.
The AWS account ID of the instance.
The instance type of the current instance.
The finding classification of the instance.
Findings for instances include:
- "Underprovisioned"
—An 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
instances may lead to poor application performance.
- "Overprovisioned"
—An 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 no specification is under-provisioned. Over-provisioned
instances may lead to unnecessary infrastructure cost.
- "Optimized" —An
instance is considered optimized when all specifications of your instance,
such as CPU, memory, and network, meet the performance requirements of
your workload and is not over provisioned. For optimized resources, AWS
Compute Optimizer might recommend a new generation instance type.
The reason for the finding classification of the instance.
Finding reason codes for instances include:
- "CPUOverprovisioned"
— The instance’s CPU configuration can be sized down while
still meeting the performance requirements of your workload. This is
identified by analyzing the
"CPUUtilization" metric of the current
instance during the look-back period.
- "CPUUnderprovisioned"
— The instance’s CPU configuration doesn't meet the
performance requirements of your workload and there is an alternative
instance type that provides better CPU performance. This is identified by
analyzing the "CPUUtilization" metric of
the current instance during the look-back period.
- "MemoryOverprovisioned"
— The instance’s memory configuration can be sized down
while still meeting the performance requirements of your workload. This is
identified by analyzing the memory utilization metric of the current
instance during the look-back period.
- "MemoryUnderprovisioned"
— The instance’s memory configuration doesn't meet the
performance requirements of your workload and there is an alternative
instance type that provides better memory performance. This is identified
by analyzing the memory utilization metric of the current instance during
the look-back period.
Memory utilization is analyzed only for resources that have
the unified CloudWatch agent installed on them. For more information,
see Enabling memory utilization with the Amazon CloudWatch Agent
(https://docs.aws.amazon.com/compute-optimizer/latest/ug/metrics.html#cw-agent)
in the AWS Compute Optimizer User Guide. On Linux instances,
Compute Optimizer analyses the
"mem_used_percent" metric in the
"CWAgent" namespace, or the legacy
"MemoryUtilization" metric in the
"System/Linux" namespace. On Windows
instances, Compute Optimizer analyses the "Memory
% Committed Bytes In Use" metric in the
"CWAgent" namespace.
- "EBSThroughputOverprovisioned"
— The instance’s EBS throughput configuration can be
sized down while still meeting the performance requirements of your
workload. This is identified by analyzing the
"VolumeReadOps" and
"VolumeWriteOps" metrics of EBS volumes
attached to the current instance during the look-back period.
- "EBSThroughputUnderprovisioned"
— The instance’s EBS throughput configuration doesn't
meet the performance requirements of your workload and there is an
alternative instance type that provides better EBS throughput performance.
This is identified by analyzing the
"VolumeReadOps" and
"VolumeWriteOps" metrics of EBS volumes
attached to the current instance during the look-back period.
- "EBSIOPSOverprovisioned"
— The instance’s EBS IOPS configuration can be sized down
while still meeting the performance requirements of your workload. This is
identified by analyzing the
"VolumeReadBytes" and
"VolumeWriteBytes" metric of EBS volumes
attached to the current instance during the look-back period.
- "EBSIOPSUnderprovisioned"
— The instance’s EBS IOPS configuration doesn't meet the
performance requirements of your workload and there is an alternative
instance type that provides better EBS IOPS performance. This is
identified by analyzing the
"VolumeReadBytes" and
"VolumeWriteBytes" metric of EBS volumes
attached to the current instance during the look-back period.
- "NetworkBandwidthOverprovisioned"
— The instance’s network bandwidth configuration can be
sized down while still meeting the performance requirements of your
workload. This is identified by analyzing the
"NetworkIn" and
"NetworkOut" metrics of the current
instance during the look-back period.
- "NetworkBandwidthUnderprovisioned"
— The instance’s network bandwidth configuration
doesn't meet the performance requirements of your workload and there is an
alternative instance type that provides better network bandwidth
performance. This is identified by analyzing the
"NetworkIn" and
"NetworkOut" metrics of the current
instance during the look-back period. This finding reason happens when the
"NetworkIn" or
"NetworkOut" performance of an instance
is impacted.
- "NetworkPPSOverprovisioned"
— The instance’s network PPS (packets per second)
configuration can be sized down while still meeting the performance
requirements of your workload. This is identified by analyzing the
"NetworkPacketsIn" and
"NetworkPacketsIn" metrics of the
current instance during the look-back period.
- "NetworkPPSUnderprovisioned"
— The instance’s network PPS (packets per second)
configuration doesn't meet the performance requirements of your workload
and there is an alternative instance type that provides better network PPS
performance. This is identified by analyzing the
"NetworkPacketsIn" and
"NetworkPacketsIn" metrics of the
current instance during the look-back period.
- "DiskIOPSOverprovisioned"
— The instance’s disk IOPS configuration can be sized down
while still meeting the performance requirements of your workload. This is
identified by analyzing the
"DiskReadOps" and
"DiskWriteOps" metrics of the current
instance during the look-back period.
- "DiskIOPSUnderprovisioned"
— The instance’s disk IOPS configuration doesn't meet
the performance requirements of your workload and there is an alternative
instance type that provides better disk IOPS performance. This is
identified by analyzing the
"DiskReadOps" and
"DiskWriteOps" metrics of the current
instance during the look-back period.
- "DiskThroughputOverprovisioned"
— The instance’s disk throughput configuration can be
sized down while still meeting the performance requirements of your
workload. This is identified by analyzing the
"DiskReadBytes" and
"DiskWriteBytes" metrics of the current
instance during the look-back period.
- "DiskThroughputUnderprovisioned"
— The instance’s disk throughput configuration doesn't
meet the performance requirements of your workload and there is an
alternative instance type that provides better disk throughput
performance. This is identified by analyzing the
"DiskReadBytes" and
"DiskWriteBytes" metrics of the current
instance during the look-back period.
For more information about instance metrics, see List the
available CloudWatch metrics for your instances
(https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html)
in the Amazon Elastic Compute Cloud User Guide. For more information
about EBS volume metrics, see Amazon CloudWatch metrics for Amazon EBS
(https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using_cloudwatch_ebs.html)
in the Amazon Elastic Compute Cloud User Guide.
The Amazon Resource Name (ARN) of the current instance.
The name of the current instance.
The time stamp of when the instance recommendation was last
refreshed.
The number of days for which utilization metrics were analyzed for
the instance.
An array of objects that describe the recommendation options for
the instance.
An array of objects that describe the source resource of the
recommendation.
An array of objects that describe the utilization metrics of the
instance.
This class forms part of Paws, describing an object used in
Paws::ComputeOptimizer
The source code is located here:
<https://github.com/pplu/aws-sdk-perl>
Please report bugs to:
<https://github.com/pplu/aws-sdk-perl/issues>