public static interface InstanceRecommendation.Builder extends SdkPojo, CopyableBuilder<InstanceRecommendation.Builder,InstanceRecommendation>
| Modifier and Type | Method and Description |
|---|---|
InstanceRecommendation.Builder |
accountId(String accountId)
The Amazon Web Services account ID of the instance.
|
InstanceRecommendation.Builder |
currentInstanceType(String currentInstanceType)
The instance type of the current instance.
|
InstanceRecommendation.Builder |
currentPerformanceRisk(CurrentPerformanceRisk currentPerformanceRisk)
The risk of the current instance not meeting the performance needs of its workloads.
|
InstanceRecommendation.Builder |
currentPerformanceRisk(String currentPerformanceRisk)
The risk of the current instance not meeting the performance needs of its workloads.
|
default InstanceRecommendation.Builder |
effectiveRecommendationPreferences(Consumer<EffectiveRecommendationPreferences.Builder> effectiveRecommendationPreferences)
An object that describes the effective recommendation preferences for the instance.
|
InstanceRecommendation.Builder |
effectiveRecommendationPreferences(EffectiveRecommendationPreferences effectiveRecommendationPreferences)
An object that describes the effective recommendation preferences for the instance.
|
default InstanceRecommendation.Builder |
externalMetricStatus(Consumer<ExternalMetricStatus.Builder> externalMetricStatus)
An object that describes Compute Optimizer's integration status with your external metrics provider.
|
InstanceRecommendation.Builder |
externalMetricStatus(ExternalMetricStatus externalMetricStatus)
An object that describes Compute Optimizer's integration status with your external metrics provider.
|
InstanceRecommendation.Builder |
finding(Finding finding)
The finding classification of the instance.
|
InstanceRecommendation.Builder |
finding(String finding)
The finding classification of the instance.
|
InstanceRecommendation.Builder |
findingReasonCodes(Collection<InstanceRecommendationFindingReasonCode> findingReasonCodes)
The reason for the finding classification of the instance.
|
InstanceRecommendation.Builder |
findingReasonCodes(InstanceRecommendationFindingReasonCode... findingReasonCodes)
The reason for the finding classification of the instance.
|
InstanceRecommendation.Builder |
findingReasonCodesWithStrings(Collection<String> findingReasonCodes)
The reason for the finding classification of the instance.
|
InstanceRecommendation.Builder |
findingReasonCodesWithStrings(String... findingReasonCodes)
The reason for the finding classification of the instance.
|
InstanceRecommendation.Builder |
inferredWorkloadTypes(Collection<InferredWorkloadType> inferredWorkloadTypes)
The applications that might be running on the instance as inferred by Compute Optimizer.
|
InstanceRecommendation.Builder |
inferredWorkloadTypes(InferredWorkloadType... inferredWorkloadTypes)
The applications that might be running on the instance as inferred by Compute Optimizer.
|
InstanceRecommendation.Builder |
inferredWorkloadTypesWithStrings(Collection<String> inferredWorkloadTypes)
The applications that might be running on the instance as inferred by Compute Optimizer.
|
InstanceRecommendation.Builder |
inferredWorkloadTypesWithStrings(String... inferredWorkloadTypes)
The applications that might be running on the instance as inferred by Compute Optimizer.
|
InstanceRecommendation.Builder |
instanceArn(String instanceArn)
The Amazon Resource Name (ARN) of the current instance.
|
InstanceRecommendation.Builder |
instanceName(String instanceName)
The name of the current instance.
|
InstanceRecommendation.Builder |
instanceState(InstanceState instanceState)
The state of the instance when the recommendation was generated.
|
InstanceRecommendation.Builder |
instanceState(String instanceState)
The state of the instance when the recommendation was generated.
|
InstanceRecommendation.Builder |
lastRefreshTimestamp(Instant lastRefreshTimestamp)
The timestamp of when the instance recommendation was last generated.
|
InstanceRecommendation.Builder |
lookBackPeriodInDays(Double lookBackPeriodInDays)
The number of days for which utilization metrics were analyzed for the instance.
|
InstanceRecommendation.Builder |
recommendationOptions(Collection<InstanceRecommendationOption> recommendationOptions)
An array of objects that describe the recommendation options for the instance.
|
InstanceRecommendation.Builder |
recommendationOptions(Consumer<InstanceRecommendationOption.Builder>... recommendationOptions)
An array of objects that describe the recommendation options for the instance.
|
InstanceRecommendation.Builder |
recommendationOptions(InstanceRecommendationOption... recommendationOptions)
An array of objects that describe the recommendation options for the instance.
|
InstanceRecommendation.Builder |
recommendationSources(Collection<RecommendationSource> recommendationSources)
An array of objects that describe the source resource of the recommendation.
|
InstanceRecommendation.Builder |
recommendationSources(Consumer<RecommendationSource.Builder>... recommendationSources)
An array of objects that describe the source resource of the recommendation.
|
InstanceRecommendation.Builder |
recommendationSources(RecommendationSource... recommendationSources)
An array of objects that describe the source resource of the recommendation.
|
InstanceRecommendation.Builder |
tags(Collection<Tag> tags)
A list of tags assigned to your Amazon EC2 instance recommendations.
|
InstanceRecommendation.Builder |
tags(Consumer<Tag.Builder>... tags)
A list of tags assigned to your Amazon EC2 instance recommendations.
|
InstanceRecommendation.Builder |
tags(Tag... tags)
A list of tags assigned to your Amazon EC2 instance recommendations.
|
InstanceRecommendation.Builder |
utilizationMetrics(Collection<UtilizationMetric> utilizationMetrics)
An array of objects that describe the utilization metrics of the instance.
|
InstanceRecommendation.Builder |
utilizationMetrics(Consumer<UtilizationMetric.Builder>... utilizationMetrics)
An array of objects that describe the utilization metrics of the instance.
|
InstanceRecommendation.Builder |
utilizationMetrics(UtilizationMetric... utilizationMetrics)
An array of objects that describe the utilization metrics of the instance.
|
equalsBySdkFields, sdkFieldscopyapplyMutation, buildInstanceRecommendation.Builder instanceArn(String instanceArn)
The Amazon Resource Name (ARN) of the current instance.
instanceArn - The Amazon Resource Name (ARN) of the current instance.InstanceRecommendation.Builder accountId(String accountId)
The Amazon Web Services account ID of the instance.
accountId - The Amazon Web Services account ID of the instance.InstanceRecommendation.Builder instanceName(String instanceName)
The name of the current instance.
instanceName - The name of the current instance.InstanceRecommendation.Builder currentInstanceType(String currentInstanceType)
The instance type of the current instance.
currentInstanceType - The instance type of the current instance.InstanceRecommendation.Builder finding(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.
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.
Finding,
FindingInstanceRecommendation.Builder finding(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.
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.
Finding,
FindingInstanceRecommendation.Builder findingReasonCodesWithStrings(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.
InstanceRecommendation.Builder findingReasonCodesWithStrings(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.
InstanceRecommendation.Builder findingReasonCodes(Collection<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.
InstanceRecommendation.Builder findingReasonCodes(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.
InstanceRecommendation.Builder utilizationMetrics(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.InstanceRecommendation.Builder utilizationMetrics(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.InstanceRecommendation.Builder utilizationMetrics(Consumer<UtilizationMetric.Builder>... utilizationMetrics)
An array of objects that describe the utilization metrics of the instance.
This is a convenience method that creates an instance of theUtilizationMetric.Builder avoiding the need to
create one manually via
UtilizationMetric.builder().
When the Consumer completes,
SdkBuilder.build() is called
immediately and its result is passed to #utilizationMetrics(List.
utilizationMetrics - a consumer that will call methods on
UtilizationMetric.Builder#utilizationMetrics(java.util.Collection) InstanceRecommendation.Builder lookBackPeriodInDays(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.InstanceRecommendation.Builder recommendationOptions(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.InstanceRecommendation.Builder recommendationOptions(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.InstanceRecommendation.Builder recommendationOptions(Consumer<InstanceRecommendationOption.Builder>... recommendationOptions)
An array of objects that describe the recommendation options for the instance.
This is a convenience method that creates an instance of theInstanceRecommendationOption.Builder avoiding
the need to create one manually via
InstanceRecommendationOption.builder().
When the Consumer completes,
SdkBuilder.build()
is called immediately and its result is passed to #recommendationOptions(List.
recommendationOptions - a consumer that will call methods on
InstanceRecommendationOption.Builder#recommendationOptions(java.util.Collection) InstanceRecommendation.Builder recommendationSources(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.InstanceRecommendation.Builder recommendationSources(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.InstanceRecommendation.Builder recommendationSources(Consumer<RecommendationSource.Builder>... recommendationSources)
An array of objects that describe the source resource of the recommendation.
This is a convenience method that creates an instance of theRecommendationSource.Builder avoiding the need
to create one manually via
RecommendationSource.builder().
When the Consumer completes,
SdkBuilder.build() is called
immediately and its result is passed to #recommendationSources(List.
recommendationSources - a consumer that will call methods on
RecommendationSource.Builder#recommendationSources(java.util.Collection) InstanceRecommendation.Builder lastRefreshTimestamp(Instant lastRefreshTimestamp)
The timestamp of when the instance recommendation was last generated.
lastRefreshTimestamp - The timestamp of when the instance recommendation was last generated.InstanceRecommendation.Builder currentPerformanceRisk(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,
CurrentPerformanceRiskInstanceRecommendation.Builder currentPerformanceRisk(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,
CurrentPerformanceRiskInstanceRecommendation.Builder effectiveRecommendationPreferences(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.default InstanceRecommendation.Builder effectiveRecommendationPreferences(Consumer<EffectiveRecommendationPreferences.Builder> effectiveRecommendationPreferences)
An object that describes the effective recommendation preferences for the instance.
This is a convenience method that creates an instance of theEffectiveRecommendationPreferences.Builder avoiding the need to create one manually via
EffectiveRecommendationPreferences.builder().
When the Consumer completes, SdkBuilder.build() is called
immediately and its result is passed to
effectiveRecommendationPreferences(EffectiveRecommendationPreferences).
effectiveRecommendationPreferences - a consumer that will call methods on EffectiveRecommendationPreferences.BuildereffectiveRecommendationPreferences(EffectiveRecommendationPreferences)InstanceRecommendation.Builder inferredWorkloadTypesWithStrings(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.
InstanceRecommendation.Builder inferredWorkloadTypesWithStrings(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.
InstanceRecommendation.Builder inferredWorkloadTypes(Collection<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.
InstanceRecommendation.Builder inferredWorkloadTypes(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.
InstanceRecommendation.Builder instanceState(String instanceState)
The state of the instance when the recommendation was generated.
instanceState - The state of the instance when the recommendation was generated.InstanceState,
InstanceStateInstanceRecommendation.Builder instanceState(InstanceState instanceState)
The state of the instance when the recommendation was generated.
instanceState - The state of the instance when the recommendation was generated.InstanceState,
InstanceStateInstanceRecommendation.Builder tags(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.InstanceRecommendation.Builder tags(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.InstanceRecommendation.Builder tags(Consumer<Tag.Builder>... tags)
A list of tags assigned to your Amazon EC2 instance recommendations.
This is a convenience method that creates an instance of theTag.Builder avoiding the need to create one
manually via Tag.builder().
When the Consumer completes,
SdkBuilder.build() is called immediately and
its result is passed to #tags(List.
tags - a consumer that will call methods on
Tag.Builder#tags(java.util.Collection) InstanceRecommendation.Builder externalMetricStatus(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.default InstanceRecommendation.Builder externalMetricStatus(Consumer<ExternalMetricStatus.Builder> externalMetricStatus)
An object that describes Compute Optimizer's integration status with your external metrics provider.
This is a convenience method that creates an instance of theExternalMetricStatus.Builder avoiding
the need to create one manually via ExternalMetricStatus.builder().
When the Consumer completes, SdkBuilder.build() is called immediately and
its result is passed to externalMetricStatus(ExternalMetricStatus).
externalMetricStatus - a consumer that will call methods on ExternalMetricStatus.BuilderexternalMetricStatus(ExternalMetricStatus)Copyright © 2023. All rights reserved.