Struct aws_sdk_computeoptimizer::model::EcsServiceRecommendation

source ·

#[non_exhaustive]
pub struct EcsServiceRecommendation { /* private fields */ }

Expand description

Describes an Amazon ECS service recommendation.

Implementations§

source §

impl EcsServiceRecommendation

source

pub fn service_arn(&self) -> Option<&str>

The Amazon Resource Name (ARN) of the current ECS service.

The following is the format of the ARN:

arn:aws:ecs:region:aws_account_id:service/cluster-name/service-name

source

pub fn account_id(&self) -> Option<&str>

The Amazon Web Services account ID of the ECS service.

source

pub fn current_service_configuration(&self) -> Option<&ServiceConfiguration>

The configuration of the current ECS service.

source

pub fn utilization_metrics(&self) -> Option<&[EcsServiceUtilizationMetric]>

An array of objects that describe the utilization metrics of the ECS service.

source

pub fn lookback_period_in_days(&self) -> f64

The number of days the ECS service utilization metrics were analyzed.

source

pub fn launch_type(&self) -> Option<&EcsServiceLaunchType>

The launch type the ECS service is using.

Compute Optimizer only supports the Fargate launch type.

source

pub fn last_refresh_timestamp(&self) -> Option<&DateTime>

The timestamp of when the ECS service recommendation was last generated.

source

pub fn finding(&self) -> Option<&EcsServiceRecommendationFinding>

The finding classification of an ECS service.

Findings for ECS services include:

Underprovisioned — When Compute Optimizer detects that there’s not enough memory or CPU, an ECS service is considered under-provisioned. An under-provisioned ECS service might result in poor application performance.
Overprovisioned — When Compute Optimizer detects that there’s excessive memory or CPU, an ECS service is considered over-provisioned. An over-provisioned ECS service might result in additional infrastructure costs.
Optimized — When both the CPU and memory of your ECS service meet the performance requirements of your workload, the service is considered optimized.

source

pub fn finding_reason_codes(
&self
) -> Option<&[EcsServiceRecommendationFindingReasonCode]>

The reason for the finding classification of an ECS service.

Finding reason codes for ECS services include:

CPUUnderprovisioned — The ECS service CPU configuration can be sized up to enhance the performance of your workload. This is identified by analyzing the CPUUtilization metric of the current service during the look-back period.
CPUOverprovisioned — The ECS service 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 service during the look-back period.
MemoryUnderprovisioned — The ECS service memory configuration can be sized up to enhance the performance of your workload. This is identified by analyzing the MemoryUtilization metric of the current service during the look-back period.
MemoryOverprovisioned — The ECS service memory configuration can be sized down while still meeting the performance requirements of your workload. This is identified by analyzing the MemoryUtilization metric of the current service during the look-back period.

source

pub fn service_recommendation_options(
&self
) -> Option<&[EcsServiceRecommendationOption]>

An array of objects that describe the recommendation options for the ECS service.

source

pub fn current_performance_risk(&self) -> Option<&CurrentPerformanceRisk>

The risk of the current ECS service not meeting the performance needs of its workloads. The higher the risk, the more likely the current service can't meet the performance requirements of its workload.

source §