@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class InstanceRecommendation extends Object implements Serializable, Cloneable, StructuredPojo
Describes an Amazon EC2 instance recommendation.
Constructor and Description |
---|
InstanceRecommendation() |
Modifier and Type | Method and Description |
---|---|
InstanceRecommendation |
clone() |
boolean |
equals(Object obj) |
String |
getAccountId()
The Amazon Web Services account ID of the instance.
|
GpuInfo |
getCurrentInstanceGpuInfo()
Describes the GPU accelerator settings for the current instance type.
|
String |
getCurrentInstanceType()
The instance type of the current instance.
|
String |
getCurrentPerformanceRisk()
The risk of the current instance not meeting the performance needs of its workloads.
|
EffectiveRecommendationPreferences |
getEffectiveRecommendationPreferences()
An object that describes the effective recommendation preferences for the instance.
|
ExternalMetricStatus |
getExternalMetricStatus()
An object that describes Compute Optimizer's integration status with your external metrics provider.
|
String |
getFinding()
The finding classification of the instance.
|
List<String> |
getFindingReasonCodes()
The reason for the finding classification of the instance.
|
String |
getIdle()
Describes if an Amazon EC2 instance is idle.
|
List<String> |
getInferredWorkloadTypes()
The applications that might be running on the instance as inferred by Compute Optimizer.
|
String |
getInstanceArn()
The Amazon Resource Name (ARN) of the current instance.
|
String |
getInstanceName()
The name of the current instance.
|
String |
getInstanceState()
The state of the instance when the recommendation was generated.
|
Date |
getLastRefreshTimestamp()
The timestamp of when the instance recommendation was last generated.
|
Double |
getLookBackPeriodInDays()
The number of days for which utilization metrics were analyzed for the instance.
|
List<InstanceRecommendationOption> |
getRecommendationOptions()
An array of objects that describe the recommendation options for the instance.
|
List<RecommendationSource> |
getRecommendationSources()
An array of objects that describe the source resource of the recommendation.
|
List<Tag> |
getTags()
A list of tags assigned to your Amazon EC2 instance recommendations.
|
List<UtilizationMetric> |
getUtilizationMetrics()
An array of objects that describe the utilization metrics of the instance.
|
int |
hashCode() |
void |
marshall(ProtocolMarshaller protocolMarshaller)
Marshalls this structured data using the given
ProtocolMarshaller . |
void |
setAccountId(String accountId)
The Amazon Web Services account ID of the instance.
|
void |
setCurrentInstanceGpuInfo(GpuInfo currentInstanceGpuInfo)
Describes the GPU accelerator settings for the current instance type.
|
void |
setCurrentInstanceType(String currentInstanceType)
The instance type of the current instance.
|
void |
setCurrentPerformanceRisk(String currentPerformanceRisk)
The risk of the current instance not meeting the performance needs of its workloads.
|
void |
setEffectiveRecommendationPreferences(EffectiveRecommendationPreferences effectiveRecommendationPreferences)
An object that describes the effective recommendation preferences for the instance.
|
void |
setExternalMetricStatus(ExternalMetricStatus externalMetricStatus)
An object that describes Compute Optimizer's integration status with your external metrics provider.
|
void |
setFinding(String finding)
The finding classification of the instance.
|
void |
setFindingReasonCodes(Collection<String> findingReasonCodes)
The reason for the finding classification of the instance.
|
void |
setIdle(String idle)
Describes if an Amazon EC2 instance is idle.
|
void |
setInferredWorkloadTypes(Collection<String> inferredWorkloadTypes)
The applications that might be running on the instance as inferred by Compute Optimizer.
|
void |
setInstanceArn(String instanceArn)
The Amazon Resource Name (ARN) of the current instance.
|
void |
setInstanceName(String instanceName)
The name of the current instance.
|
void |
setInstanceState(String instanceState)
The state of the instance when the recommendation was generated.
|
void |
setLastRefreshTimestamp(Date lastRefreshTimestamp)
The timestamp of when the instance recommendation was last generated.
|
void |
setLookBackPeriodInDays(Double lookBackPeriodInDays)
The number of days for which utilization metrics were analyzed for the instance.
|
void |
setRecommendationOptions(Collection<InstanceRecommendationOption> recommendationOptions)
An array of objects that describe the recommendation options for the instance.
|
void |
setRecommendationSources(Collection<RecommendationSource> recommendationSources)
An array of objects that describe the source resource of the recommendation.
|
void |
setTags(Collection<Tag> tags)
A list of tags assigned to your Amazon EC2 instance recommendations.
|
void |
setUtilizationMetrics(Collection<UtilizationMetric> utilizationMetrics)
An array of objects that describe the utilization metrics of the instance.
|
String |
toString()
Returns a string representation of this object.
|
InstanceRecommendation |
withAccountId(String accountId)
The Amazon Web Services account ID of the instance.
|
InstanceRecommendation |
withCurrentInstanceGpuInfo(GpuInfo currentInstanceGpuInfo)
Describes the GPU accelerator settings for the current instance type.
|
InstanceRecommendation |
withCurrentInstanceType(String currentInstanceType)
The instance type of the current instance.
|
InstanceRecommendation |
withCurrentPerformanceRisk(CurrentPerformanceRisk currentPerformanceRisk)
The risk of the current instance not meeting the performance needs of its workloads.
|
InstanceRecommendation |
withCurrentPerformanceRisk(String currentPerformanceRisk)
The risk of the current instance not meeting the performance needs of its workloads.
|
InstanceRecommendation |
withEffectiveRecommendationPreferences(EffectiveRecommendationPreferences effectiveRecommendationPreferences)
An object that describes the effective recommendation preferences for the instance.
|
InstanceRecommendation |
withExternalMetricStatus(ExternalMetricStatus externalMetricStatus)
An object that describes Compute Optimizer's integration status with your external metrics provider.
|
InstanceRecommendation |
withFinding(Finding finding)
The finding classification of the instance.
|
InstanceRecommendation |
withFinding(String finding)
The finding classification of the instance.
|
InstanceRecommendation |
withFindingReasonCodes(Collection<String> findingReasonCodes)
The reason for the finding classification of the instance.
|
InstanceRecommendation |
withFindingReasonCodes(InstanceRecommendationFindingReasonCode... findingReasonCodes)
The reason for the finding classification of the instance.
|
InstanceRecommendation |
withFindingReasonCodes(String... findingReasonCodes)
The reason for the finding classification of the instance.
|
InstanceRecommendation |
withIdle(InstanceIdle idle)
Describes if an Amazon EC2 instance is idle.
|
InstanceRecommendation |
withIdle(String idle)
Describes if an Amazon EC2 instance is idle.
|
InstanceRecommendation |
withInferredWorkloadTypes(Collection<String> inferredWorkloadTypes)
The applications that might be running on the instance as inferred by Compute Optimizer.
|
InstanceRecommendation |
withInferredWorkloadTypes(InferredWorkloadType... inferredWorkloadTypes)
The applications that might be running on the instance as inferred by Compute Optimizer.
|
InstanceRecommendation |
withInferredWorkloadTypes(String... inferredWorkloadTypes)
The applications that might be running on the instance as inferred by Compute Optimizer.
|
InstanceRecommendation |
withInstanceArn(String instanceArn)
The Amazon Resource Name (ARN) of the current instance.
|
InstanceRecommendation |
withInstanceName(String instanceName)
The name of the current instance.
|
InstanceRecommendation |
withInstanceState(InstanceState instanceState)
The state of the instance when the recommendation was generated.
|
InstanceRecommendation |
withInstanceState(String instanceState)
The state of the instance when the recommendation was generated.
|
InstanceRecommendation |
withLastRefreshTimestamp(Date lastRefreshTimestamp)
The timestamp of when the instance recommendation was last generated.
|
InstanceRecommendation |
withLookBackPeriodInDays(Double lookBackPeriodInDays)
The number of days for which utilization metrics were analyzed for the instance.
|
InstanceRecommendation |
withRecommendationOptions(Collection<InstanceRecommendationOption> recommendationOptions)
An array of objects that describe the recommendation options for the instance.
|
InstanceRecommendation |
withRecommendationOptions(InstanceRecommendationOption... recommendationOptions)
An array of objects that describe the recommendation options for the instance.
|
InstanceRecommendation |
withRecommendationSources(Collection<RecommendationSource> recommendationSources)
An array of objects that describe the source resource of the recommendation.
|
InstanceRecommendation |
withRecommendationSources(RecommendationSource... recommendationSources)
An array of objects that describe the source resource of the recommendation.
|
InstanceRecommendation |
withTags(Collection<Tag> tags)
A list of tags assigned to your Amazon EC2 instance recommendations.
|
InstanceRecommendation |
withTags(Tag... tags)
A list of tags assigned to your Amazon EC2 instance recommendations.
|
InstanceRecommendation |
withUtilizationMetrics(Collection<UtilizationMetric> utilizationMetrics)
An array of objects that describe the utilization metrics of the instance.
|
InstanceRecommendation |
withUtilizationMetrics(UtilizationMetric... utilizationMetrics)
An array of objects that describe the utilization metrics of the instance.
|
public void setInstanceArn(String instanceArn)
The Amazon Resource Name (ARN) of the current instance.
instanceArn
- The Amazon Resource Name (ARN) of the current instance.public String getInstanceArn()
The Amazon Resource Name (ARN) of the current instance.
public InstanceRecommendation withInstanceArn(String instanceArn)
The Amazon Resource Name (ARN) of the current instance.
instanceArn
- The Amazon Resource Name (ARN) of the current instance.public void setAccountId(String accountId)
The Amazon Web Services account ID of the instance.
accountId
- The Amazon Web Services account ID of the instance.public String getAccountId()
The Amazon Web Services account ID of the instance.
public InstanceRecommendation withAccountId(String accountId)
The Amazon Web Services account ID of the instance.
accountId
- The Amazon Web Services account ID of the instance.public void setInstanceName(String instanceName)
The name of the current instance.
instanceName
- The name of the current instance.public String getInstanceName()
The name of the current instance.
public InstanceRecommendation withInstanceName(String instanceName)
The name of the current instance.
instanceName
- The name of the current instance.public void setCurrentInstanceType(String currentInstanceType)
The instance type of the current instance.
currentInstanceType
- The instance type of the current instance.public String getCurrentInstanceType()
The instance type of the current instance.
public InstanceRecommendation withCurrentInstanceType(String currentInstanceType)
The instance type of the current instance.
currentInstanceType
- The instance type of the current instance.public void setFinding(String finding)
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, Compute Optimizer might recommend a new generation instance type.
The valid values in your API responses appear as OVER_PROVISIONED, UNDER_PROVISIONED, or OPTIMIZED.
finding
- 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, Compute Optimizer might recommend a new generation instance
type.
The valid values in your API responses appear as OVER_PROVISIONED, UNDER_PROVISIONED, or OPTIMIZED.
Finding
public String getFinding()
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, Compute Optimizer might recommend a new generation instance type.
The valid values in your API responses appear as OVER_PROVISIONED, UNDER_PROVISIONED, or OPTIMIZED.
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, Compute Optimizer might recommend a new generation instance
type.
The valid values in your API responses appear as OVER_PROVISIONED, UNDER_PROVISIONED, or OPTIMIZED.
Finding
public InstanceRecommendation withFinding(String finding)
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, Compute Optimizer might recommend a new generation instance type.
The valid values in your API responses appear as OVER_PROVISIONED, UNDER_PROVISIONED, or OPTIMIZED.
finding
- 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, Compute Optimizer might recommend a new generation instance
type.
The valid values in your API responses appear as OVER_PROVISIONED, UNDER_PROVISIONED, or OPTIMIZED.
Finding
public InstanceRecommendation withFinding(Finding finding)
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, Compute Optimizer might recommend a new generation instance type.
The valid values in your API responses appear as OVER_PROVISIONED, UNDER_PROVISIONED, or OPTIMIZED.
finding
- 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, Compute Optimizer might recommend a new generation instance
type.
The valid values in your API responses appear as OVER_PROVISIONED, UNDER_PROVISIONED, or OPTIMIZED.
Finding
public List<String> getFindingReasonCodes()
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 in the 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
VolumeReadBytes
and VolumeWriteBytes
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 VolumeReadBytes
and
VolumeWriteBytes
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
VolumeReadOps
and VolumeWriteOps
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 VolumeReadOps
and VolumeWriteOps
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 in the Amazon Elastic Compute Cloud User Guide. For more information about EBS volume metrics, see Amazon CloudWatch metrics for Amazon EBS in the Amazon Elastic Compute Cloud User Guide.
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 in the 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 VolumeReadBytes
and VolumeWriteBytes
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
VolumeReadBytes
and VolumeWriteBytes
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
VolumeReadOps
and VolumeWriteOps
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 VolumeReadOps
and
VolumeWriteOps
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 in the Amazon Elastic Compute Cloud User Guide. For more information about EBS volume metrics, see Amazon CloudWatch metrics for Amazon EBS in the Amazon Elastic Compute Cloud User Guide.
InstanceRecommendationFindingReasonCode
public void setFindingReasonCodes(Collection<String> findingReasonCodes)
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 in the 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
VolumeReadBytes
and VolumeWriteBytes
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 VolumeReadBytes
and
VolumeWriteBytes
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
VolumeReadOps
and VolumeWriteOps
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 VolumeReadOps
and VolumeWriteOps
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 in the Amazon Elastic Compute Cloud User Guide. For more information about EBS volume metrics, see Amazon CloudWatch metrics for Amazon EBS in the Amazon Elastic Compute Cloud User Guide.
findingReasonCodes
- 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 in the 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 VolumeReadBytes
and VolumeWriteBytes
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 VolumeReadBytes
and
VolumeWriteBytes
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
VolumeReadOps
and VolumeWriteOps
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 VolumeReadOps
and
VolumeWriteOps
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 in the Amazon Elastic Compute Cloud User Guide. For more information about EBS volume metrics, see Amazon CloudWatch metrics for Amazon EBS in the Amazon Elastic Compute Cloud User Guide.
InstanceRecommendationFindingReasonCode
public InstanceRecommendation withFindingReasonCodes(String... findingReasonCodes)
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 in the 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
VolumeReadBytes
and VolumeWriteBytes
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 VolumeReadBytes
and
VolumeWriteBytes
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
VolumeReadOps
and VolumeWriteOps
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 VolumeReadOps
and VolumeWriteOps
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 in the Amazon Elastic Compute Cloud User Guide. For more information about EBS volume metrics, see Amazon CloudWatch metrics for Amazon EBS in the Amazon Elastic Compute Cloud User Guide.
NOTE: This method appends the values to the existing list (if any). Use
setFindingReasonCodes(java.util.Collection)
or withFindingReasonCodes(java.util.Collection)
if
you want to override the existing values.
findingReasonCodes
- 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 in the 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 VolumeReadBytes
and VolumeWriteBytes
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 VolumeReadBytes
and
VolumeWriteBytes
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
VolumeReadOps
and VolumeWriteOps
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 VolumeReadOps
and
VolumeWriteOps
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 in the Amazon Elastic Compute Cloud User Guide. For more information about EBS volume metrics, see Amazon CloudWatch metrics for Amazon EBS in the Amazon Elastic Compute Cloud User Guide.
InstanceRecommendationFindingReasonCode
public InstanceRecommendation withFindingReasonCodes(Collection<String> findingReasonCodes)
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 in the 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
VolumeReadBytes
and VolumeWriteBytes
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 VolumeReadBytes
and
VolumeWriteBytes
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
VolumeReadOps
and VolumeWriteOps
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 VolumeReadOps
and VolumeWriteOps
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 in the Amazon Elastic Compute Cloud User Guide. For more information about EBS volume metrics, see Amazon CloudWatch metrics for Amazon EBS in the Amazon Elastic Compute Cloud User Guide.
findingReasonCodes
- 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 in the 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 VolumeReadBytes
and VolumeWriteBytes
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 VolumeReadBytes
and
VolumeWriteBytes
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
VolumeReadOps
and VolumeWriteOps
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 VolumeReadOps
and
VolumeWriteOps
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 in the Amazon Elastic Compute Cloud User Guide. For more information about EBS volume metrics, see Amazon CloudWatch metrics for Amazon EBS in the Amazon Elastic Compute Cloud User Guide.
InstanceRecommendationFindingReasonCode
public InstanceRecommendation withFindingReasonCodes(InstanceRecommendationFindingReasonCode... findingReasonCodes)
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 in the 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
VolumeReadBytes
and VolumeWriteBytes
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 VolumeReadBytes
and
VolumeWriteBytes
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
VolumeReadOps
and VolumeWriteOps
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 VolumeReadOps
and VolumeWriteOps
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 in the Amazon Elastic Compute Cloud User Guide. For more information about EBS volume metrics, see Amazon CloudWatch metrics for Amazon EBS in the Amazon Elastic Compute Cloud User Guide.
findingReasonCodes
- 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 in the 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 VolumeReadBytes
and VolumeWriteBytes
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 VolumeReadBytes
and
VolumeWriteBytes
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
VolumeReadOps
and VolumeWriteOps
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 VolumeReadOps
and
VolumeWriteOps
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 in the Amazon Elastic Compute Cloud User Guide. For more information about EBS volume metrics, see Amazon CloudWatch metrics for Amazon EBS in the Amazon Elastic Compute Cloud User Guide.
InstanceRecommendationFindingReasonCode
public List<UtilizationMetric> getUtilizationMetrics()
An array of objects that describe the utilization metrics of the instance.
public void setUtilizationMetrics(Collection<UtilizationMetric> utilizationMetrics)
An array of objects that describe the utilization metrics of the instance.
utilizationMetrics
- An array of objects that describe the utilization metrics of the instance.public InstanceRecommendation withUtilizationMetrics(UtilizationMetric... utilizationMetrics)
An array of objects that describe the utilization metrics of the instance.
NOTE: This method appends the values to the existing list (if any). Use
setUtilizationMetrics(java.util.Collection)
or withUtilizationMetrics(java.util.Collection)
if
you want to override the existing values.
utilizationMetrics
- An array of objects that describe the utilization metrics of the instance.public InstanceRecommendation withUtilizationMetrics(Collection<UtilizationMetric> utilizationMetrics)
An array of objects that describe the utilization metrics of the instance.
utilizationMetrics
- An array of objects that describe the utilization metrics of the instance.public void setLookBackPeriodInDays(Double lookBackPeriodInDays)
The number of days for which utilization metrics were analyzed for the instance.
lookBackPeriodInDays
- The number of days for which utilization metrics were analyzed for the instance.public Double getLookBackPeriodInDays()
The number of days for which utilization metrics were analyzed for the instance.
public InstanceRecommendation withLookBackPeriodInDays(Double lookBackPeriodInDays)
The number of days for which utilization metrics were analyzed for the instance.
lookBackPeriodInDays
- The number of days for which utilization metrics were analyzed for the instance.public List<InstanceRecommendationOption> getRecommendationOptions()
An array of objects that describe the recommendation options for the instance.
public void setRecommendationOptions(Collection<InstanceRecommendationOption> recommendationOptions)
An array of objects that describe the recommendation options for the instance.
recommendationOptions
- An array of objects that describe the recommendation options for the instance.public InstanceRecommendation withRecommendationOptions(InstanceRecommendationOption... recommendationOptions)
An array of objects that describe the recommendation options for the instance.
NOTE: This method appends the values to the existing list (if any). Use
setRecommendationOptions(java.util.Collection)
or
withRecommendationOptions(java.util.Collection)
if you want to override the existing values.
recommendationOptions
- An array of objects that describe the recommendation options for the instance.public InstanceRecommendation withRecommendationOptions(Collection<InstanceRecommendationOption> recommendationOptions)
An array of objects that describe the recommendation options for the instance.
recommendationOptions
- An array of objects that describe the recommendation options for the instance.public List<RecommendationSource> getRecommendationSources()
An array of objects that describe the source resource of the recommendation.
public void setRecommendationSources(Collection<RecommendationSource> recommendationSources)
An array of objects that describe the source resource of the recommendation.
recommendationSources
- An array of objects that describe the source resource of the recommendation.public InstanceRecommendation withRecommendationSources(RecommendationSource... recommendationSources)
An array of objects that describe the source resource of the recommendation.
NOTE: This method appends the values to the existing list (if any). Use
setRecommendationSources(java.util.Collection)
or
withRecommendationSources(java.util.Collection)
if you want to override the existing values.
recommendationSources
- An array of objects that describe the source resource of the recommendation.public InstanceRecommendation withRecommendationSources(Collection<RecommendationSource> recommendationSources)
An array of objects that describe the source resource of the recommendation.
recommendationSources
- An array of objects that describe the source resource of the recommendation.public void setLastRefreshTimestamp(Date lastRefreshTimestamp)
The timestamp of when the instance recommendation was last generated.
lastRefreshTimestamp
- The timestamp of when the instance recommendation was last generated.public Date getLastRefreshTimestamp()
The timestamp of when the instance recommendation was last generated.
public InstanceRecommendation withLastRefreshTimestamp(Date lastRefreshTimestamp)
The timestamp of when the instance recommendation was last generated.
lastRefreshTimestamp
- The timestamp of when the instance recommendation was last generated.public void setCurrentPerformanceRisk(String currentPerformanceRisk)
The risk of the current instance not meeting the performance needs of its workloads. The higher the risk, the more likely the current instance cannot meet the performance requirements of its workload.
currentPerformanceRisk
- The risk of the current instance not meeting the performance needs of its workloads. The higher the risk,
the more likely the current instance cannot meet the performance requirements of its workload.CurrentPerformanceRisk
public String getCurrentPerformanceRisk()
The risk of the current instance not meeting the performance needs of its workloads. The higher the risk, the more likely the current instance cannot meet the performance requirements of its workload.
CurrentPerformanceRisk
public InstanceRecommendation withCurrentPerformanceRisk(String currentPerformanceRisk)
The risk of the current instance not meeting the performance needs of its workloads. The higher the risk, the more likely the current instance cannot meet the performance requirements of its workload.
currentPerformanceRisk
- The risk of the current instance not meeting the performance needs of its workloads. The higher the risk,
the more likely the current instance cannot meet the performance requirements of its workload.CurrentPerformanceRisk
public InstanceRecommendation withCurrentPerformanceRisk(CurrentPerformanceRisk currentPerformanceRisk)
The risk of the current instance not meeting the performance needs of its workloads. The higher the risk, the more likely the current instance cannot meet the performance requirements of its workload.
currentPerformanceRisk
- The risk of the current instance not meeting the performance needs of its workloads. The higher the risk,
the more likely the current instance cannot meet the performance requirements of its workload.CurrentPerformanceRisk
public void setEffectiveRecommendationPreferences(EffectiveRecommendationPreferences effectiveRecommendationPreferences)
An object that describes the effective recommendation preferences for the instance.
effectiveRecommendationPreferences
- An object that describes the effective recommendation preferences for the instance.public EffectiveRecommendationPreferences getEffectiveRecommendationPreferences()
An object that describes the effective recommendation preferences for the instance.
public InstanceRecommendation withEffectiveRecommendationPreferences(EffectiveRecommendationPreferences effectiveRecommendationPreferences)
An object that describes the effective recommendation preferences for the instance.
effectiveRecommendationPreferences
- An object that describes the effective recommendation preferences for the instance.public List<String> getInferredWorkloadTypes()
The applications that might be running on the instance as inferred by Compute Optimizer.
Compute Optimizer can infer if one of the following applications might be running on the instance:
AmazonEmr
- Infers that Amazon EMR might be running on the instance.
ApacheCassandra
- Infers that Apache Cassandra might be running on the instance.
ApacheHadoop
- Infers that Apache Hadoop might be running on the instance.
Memcached
- Infers that Memcached might be running on the instance.
NGINX
- Infers that NGINX might be running on the instance.
PostgreSql
- Infers that PostgreSQL might be running on the instance.
Redis
- Infers that Redis might be running on the instance.
Kafka
- Infers that Kafka might be running on the instance.
SQLServer
- Infers that SQLServer might be running on the instance.
Compute Optimizer can infer if one of the following applications might be running on the instance:
AmazonEmr
- Infers that Amazon EMR might be running on the instance.
ApacheCassandra
- Infers that Apache Cassandra might be running on the instance.
ApacheHadoop
- Infers that Apache Hadoop might be running on the instance.
Memcached
- Infers that Memcached might be running on the instance.
NGINX
- Infers that NGINX might be running on the instance.
PostgreSql
- Infers that PostgreSQL might be running on the instance.
Redis
- Infers that Redis might be running on the instance.
Kafka
- Infers that Kafka might be running on the instance.
SQLServer
- Infers that SQLServer might be running on the instance.
InferredWorkloadType
public void setInferredWorkloadTypes(Collection<String> inferredWorkloadTypes)
The applications that might be running on the instance as inferred by Compute Optimizer.
Compute Optimizer can infer if one of the following applications might be running on the instance:
AmazonEmr
- Infers that Amazon EMR might be running on the instance.
ApacheCassandra
- Infers that Apache Cassandra might be running on the instance.
ApacheHadoop
- Infers that Apache Hadoop might be running on the instance.
Memcached
- Infers that Memcached might be running on the instance.
NGINX
- Infers that NGINX might be running on the instance.
PostgreSql
- Infers that PostgreSQL might be running on the instance.
Redis
- Infers that Redis might be running on the instance.
Kafka
- Infers that Kafka might be running on the instance.
SQLServer
- Infers that SQLServer might be running on the instance.
inferredWorkloadTypes
- The applications that might be running on the instance as inferred by Compute Optimizer.
Compute Optimizer can infer if one of the following applications might be running on the instance:
AmazonEmr
- Infers that Amazon EMR might be running on the instance.
ApacheCassandra
- Infers that Apache Cassandra might be running on the instance.
ApacheHadoop
- Infers that Apache Hadoop might be running on the instance.
Memcached
- Infers that Memcached might be running on the instance.
NGINX
- Infers that NGINX might be running on the instance.
PostgreSql
- Infers that PostgreSQL might be running on the instance.
Redis
- Infers that Redis might be running on the instance.
Kafka
- Infers that Kafka might be running on the instance.
SQLServer
- Infers that SQLServer might be running on the instance.
InferredWorkloadType
public InstanceRecommendation withInferredWorkloadTypes(String... inferredWorkloadTypes)
The applications that might be running on the instance as inferred by Compute Optimizer.
Compute Optimizer can infer if one of the following applications might be running on the instance:
AmazonEmr
- Infers that Amazon EMR might be running on the instance.
ApacheCassandra
- Infers that Apache Cassandra might be running on the instance.
ApacheHadoop
- Infers that Apache Hadoop might be running on the instance.
Memcached
- Infers that Memcached might be running on the instance.
NGINX
- Infers that NGINX might be running on the instance.
PostgreSql
- Infers that PostgreSQL might be running on the instance.
Redis
- Infers that Redis might be running on the instance.
Kafka
- Infers that Kafka might be running on the instance.
SQLServer
- Infers that SQLServer might be running on the instance.
NOTE: This method appends the values to the existing list (if any). Use
setInferredWorkloadTypes(java.util.Collection)
or
withInferredWorkloadTypes(java.util.Collection)
if you want to override the existing values.
inferredWorkloadTypes
- The applications that might be running on the instance as inferred by Compute Optimizer.
Compute Optimizer can infer if one of the following applications might be running on the instance:
AmazonEmr
- Infers that Amazon EMR might be running on the instance.
ApacheCassandra
- Infers that Apache Cassandra might be running on the instance.
ApacheHadoop
- Infers that Apache Hadoop might be running on the instance.
Memcached
- Infers that Memcached might be running on the instance.
NGINX
- Infers that NGINX might be running on the instance.
PostgreSql
- Infers that PostgreSQL might be running on the instance.
Redis
- Infers that Redis might be running on the instance.
Kafka
- Infers that Kafka might be running on the instance.
SQLServer
- Infers that SQLServer might be running on the instance.
InferredWorkloadType
public InstanceRecommendation withInferredWorkloadTypes(Collection<String> inferredWorkloadTypes)
The applications that might be running on the instance as inferred by Compute Optimizer.
Compute Optimizer can infer if one of the following applications might be running on the instance:
AmazonEmr
- Infers that Amazon EMR might be running on the instance.
ApacheCassandra
- Infers that Apache Cassandra might be running on the instance.
ApacheHadoop
- Infers that Apache Hadoop might be running on the instance.
Memcached
- Infers that Memcached might be running on the instance.
NGINX
- Infers that NGINX might be running on the instance.
PostgreSql
- Infers that PostgreSQL might be running on the instance.
Redis
- Infers that Redis might be running on the instance.
Kafka
- Infers that Kafka might be running on the instance.
SQLServer
- Infers that SQLServer might be running on the instance.
inferredWorkloadTypes
- The applications that might be running on the instance as inferred by Compute Optimizer.
Compute Optimizer can infer if one of the following applications might be running on the instance:
AmazonEmr
- Infers that Amazon EMR might be running on the instance.
ApacheCassandra
- Infers that Apache Cassandra might be running on the instance.
ApacheHadoop
- Infers that Apache Hadoop might be running on the instance.
Memcached
- Infers that Memcached might be running on the instance.
NGINX
- Infers that NGINX might be running on the instance.
PostgreSql
- Infers that PostgreSQL might be running on the instance.
Redis
- Infers that Redis might be running on the instance.
Kafka
- Infers that Kafka might be running on the instance.
SQLServer
- Infers that SQLServer might be running on the instance.
InferredWorkloadType
public InstanceRecommendation withInferredWorkloadTypes(InferredWorkloadType... inferredWorkloadTypes)
The applications that might be running on the instance as inferred by Compute Optimizer.
Compute Optimizer can infer if one of the following applications might be running on the instance:
AmazonEmr
- Infers that Amazon EMR might be running on the instance.
ApacheCassandra
- Infers that Apache Cassandra might be running on the instance.
ApacheHadoop
- Infers that Apache Hadoop might be running on the instance.
Memcached
- Infers that Memcached might be running on the instance.
NGINX
- Infers that NGINX might be running on the instance.
PostgreSql
- Infers that PostgreSQL might be running on the instance.
Redis
- Infers that Redis might be running on the instance.
Kafka
- Infers that Kafka might be running on the instance.
SQLServer
- Infers that SQLServer might be running on the instance.
inferredWorkloadTypes
- The applications that might be running on the instance as inferred by Compute Optimizer.
Compute Optimizer can infer if one of the following applications might be running on the instance:
AmazonEmr
- Infers that Amazon EMR might be running on the instance.
ApacheCassandra
- Infers that Apache Cassandra might be running on the instance.
ApacheHadoop
- Infers that Apache Hadoop might be running on the instance.
Memcached
- Infers that Memcached might be running on the instance.
NGINX
- Infers that NGINX might be running on the instance.
PostgreSql
- Infers that PostgreSQL might be running on the instance.
Redis
- Infers that Redis might be running on the instance.
Kafka
- Infers that Kafka might be running on the instance.
SQLServer
- Infers that SQLServer might be running on the instance.
InferredWorkloadType
public void setInstanceState(String instanceState)
The state of the instance when the recommendation was generated.
instanceState
- The state of the instance when the recommendation was generated.InstanceState
public String getInstanceState()
The state of the instance when the recommendation was generated.
InstanceState
public InstanceRecommendation withInstanceState(String instanceState)
The state of the instance when the recommendation was generated.
instanceState
- The state of the instance when the recommendation was generated.InstanceState
public InstanceRecommendation withInstanceState(InstanceState instanceState)
The state of the instance when the recommendation was generated.
instanceState
- The state of the instance when the recommendation was generated.InstanceState
public List<Tag> getTags()
A list of tags assigned to your Amazon EC2 instance recommendations.
public void setTags(Collection<Tag> tags)
A list of tags assigned to your Amazon EC2 instance recommendations.
tags
- A list of tags assigned to your Amazon EC2 instance recommendations.public InstanceRecommendation withTags(Tag... tags)
A list of tags assigned to your Amazon EC2 instance recommendations.
NOTE: This method appends the values to the existing list (if any). Use
setTags(java.util.Collection)
or withTags(java.util.Collection)
if you want to override the
existing values.
tags
- A list of tags assigned to your Amazon EC2 instance recommendations.public InstanceRecommendation withTags(Collection<Tag> tags)
A list of tags assigned to your Amazon EC2 instance recommendations.
tags
- A list of tags assigned to your Amazon EC2 instance recommendations.public void setExternalMetricStatus(ExternalMetricStatus externalMetricStatus)
An object that describes Compute Optimizer's integration status with your external metrics provider.
externalMetricStatus
- An object that describes Compute Optimizer's integration status with your external metrics provider.public ExternalMetricStatus getExternalMetricStatus()
An object that describes Compute Optimizer's integration status with your external metrics provider.
public InstanceRecommendation withExternalMetricStatus(ExternalMetricStatus externalMetricStatus)
An object that describes Compute Optimizer's integration status with your external metrics provider.
externalMetricStatus
- An object that describes Compute Optimizer's integration status with your external metrics provider.public void setCurrentInstanceGpuInfo(GpuInfo currentInstanceGpuInfo)
Describes the GPU accelerator settings for the current instance type.
currentInstanceGpuInfo
- Describes the GPU accelerator settings for the current instance type.public GpuInfo getCurrentInstanceGpuInfo()
Describes the GPU accelerator settings for the current instance type.
public InstanceRecommendation withCurrentInstanceGpuInfo(GpuInfo currentInstanceGpuInfo)
Describes the GPU accelerator settings for the current instance type.
currentInstanceGpuInfo
- Describes the GPU accelerator settings for the current instance type.public void setIdle(String idle)
Describes if an Amazon EC2 instance is idle.
idle
- Describes if an Amazon EC2 instance is idle.InstanceIdle
public String getIdle()
Describes if an Amazon EC2 instance is idle.
InstanceIdle
public InstanceRecommendation withIdle(String idle)
Describes if an Amazon EC2 instance is idle.
idle
- Describes if an Amazon EC2 instance is idle.InstanceIdle
public InstanceRecommendation withIdle(InstanceIdle idle)
Describes if an Amazon EC2 instance is idle.
idle
- Describes if an Amazon EC2 instance is idle.InstanceIdle
public String toString()
toString
in class Object
Object.toString()
public InstanceRecommendation clone()
public void marshall(ProtocolMarshaller protocolMarshaller)
StructuredPojo
ProtocolMarshaller
.marshall
in interface StructuredPojo
protocolMarshaller
- Implementation of ProtocolMarshaller
used to marshall this object's data.