AWS compute-optimizer documentation change
Summary
Clarified EBS volume idle detection logic by adding notes that changing the lookback period doesn't affect the 32-day unattached volume check, and standardized lookback period terminology across services.
Security assessment
Changes only refine idle resource detection criteria and documentation clarity. No security vulnerabilities, mitigations, or security features are mentioned.
Diff
diff --git a/compute-optimizer/latest/ug/view-idle-recommendations.md b/compute-optimizer/latest/ug/view-idle-recommendations.md index fb6b0684a..0a0e337dd 100644 --- a//compute-optimizer/latest/ug/view-idle-recommendations.md +++ b//compute-optimizer/latest/ug/view-idle-recommendations.md @@ -32 +32,6 @@ The recommendations are refreshed daily. These recommendations are generated by -For EBS volumes and NAT Gateway we analyze the attachment status over a 32-day lookback period. + * For EBS volumes and NAT Gateway we analyze the attachment status over a 32-day lookback period. + + * Changing the lookback period for EBS volume recommendations to 14 days does not affect the 32-day lookback period used to determine whether an EBS volume is unattached. + + + @@ -69 +74 @@ Amazon EBS volumes | Read/Write operations and attachment status | Compute Opt - * **Idle** — If the sum of read/write operations is less than 1 per day over the 14-day lookback period, and the volume is not a root volume. + * **Idle** — If the sum of read/write operations is less than 1 per day over the look-back period, and the volume is not a root volume. The default look-back period is 14 days, which you can extend up to 32 days. @@ -71,0 +77,6 @@ Amazon EBS volumes | Read/Write operations and attachment status | Compute Opt + + +###### Note + + * Changing the lookback period for EBS volume recommendations to 14 days does not affect the 32-day lookback period used to determine whether an EBS volume is unattached. + @@ -73 +84 @@ Amazon EBS volumes | Read/Write operations and attachment status | Compute Opt -Amazon ECS services on Fargate | CPU utilization and memory utilization | The peak CPU and memory utilization is below 1% over the 14-day lookback period. | Verify whether your containerized application is running as expected. If the application is not running, consider deleting this service. +Amazon ECS services on Fargate | CPU utilization and memory utilization | The peak CPU and memory utilization is below 1% over the lookback period. The default lookback period is 14 days, which you can extend up to 32 days. | Verify whether your containerized application is running as expected. If the application is not running, consider deleting this service.