AWS compute-optimizer documentation change
Summary
Added 6 new resource types to idle recommendations (DynamoDB, ElastiCache, MemoryDB, DocumentDB, WorkSpaces, SageMaker), extended lookback periods, and added resource-specific idle criteria and action recommendations
Security assessment
Expands idle resource detection capabilities but contains no security vulnerability fixes. Recommendations focus on cost optimization ('verify if unused', 'delete if not needed') without security hardening guidance.
Diff
diff --git a/compute-optimizer/latest/ug/view-idle-recommendations.md b/compute-optimizer/latest/ug/view-idle-recommendations.md index 0a0e337dd..42f8b932e 100644 --- a//compute-optimizer/latest/ug/view-idle-recommendations.md +++ b//compute-optimizer/latest/ug/view-idle-recommendations.md @@ -24,0 +25,12 @@ Compute Optimizer helps you identify idle resources that can be deleted or stopp + * Amazon DynamoDB + + * Amazon ElastiCache + + * Amazon MemoryDB + + * Amazon DocumentDB + + * Amazon WorkSpaces + + * Amazon SageMaker endpoints + @@ -32 +44 @@ 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. For WorkSpaces, we analyze user connection activity over a 63-day lookback period. @@ -35,0 +48,2 @@ The recommendations are refreshed daily. These recommendations are generated by + * For ElastiCache, it may take up to 48 hours for recommendations to appear after opting in to Compute Optimizer. + @@ -86,0 +101,6 @@ Amazon NAT Gateway | Active connection count, Packets in from source, Packets i +Amazon DynamoDB | Consumed read capacity units and consumed write capacity units | Applies to provisioned tables only. A table is considered idle when there are no consumed read or write capacity units at both the table level and all Global Secondary Index (GSI) levels over the 14-day lookback period. | Verify whether this table is unused. Consider switching to on-demand mode or minimize provisioned capacity. If no longer needed, consider exporting data to S3 and deleting the resource. +Amazon ElastiCache | New connections, engine CPU utilization, cache hits, cache misses, get commands, and set commands | Applies to Redis and Valkey engines only. **Node-based (provisioned)** The cluster has no new connections, engine CPU utilization is below 1%, and no cache hits, misses, get commands, or set commands over the 14-day lookback period. Metrics are evaluated at the node level; a cluster is idle only if all nodes are idle. **Serverless** The cluster has no processing units consumed, no current or new connections, and no cache hits, misses, get commands, or set commands over the 14-day lookback period. | Verify whether your application still requires this caching layer. For provisioned clusters, consider switching to ElastiCache Serverless for variable workloads. If not required, consider deleting the resource. +Amazon MemoryDB | New connections, engine CPU utilization, keyspace hits, and keyspace misses | The cluster has no new connections, engine CPU utilization is below 1%, and no keyspace hits or misses over the 14-day lookback period. The cluster must be in available status. | Verify whether your application still requires this caching layer. If not required, consider deleting the resource. +Amazon DocumentDB | Database connections | Applies to both provisioned and serverless clusters. Elastic clusters are excluded. The cluster has no database connections over the 14-day lookback period. The cluster must be in available status. | **Provisioned** Verify whether you need this cluster. If not needed temporarily, you can stop the resource for up to 7 days or consider switching to DocumentDB Serverless. If no longer needed, create a DB snapshot and delete the resource. **Serverless** Verify whether you need this cluster. If not needed temporarily, you can stop the resource for up to 7 days. If no longer needed, create a DB snapshot and delete the resource. +Amazon WorkSpaces | User connection activity | Applies to Always On WorkSpaces only. Auto Stop and Standby WorkSpaces are excluded. No user has connected to the WorkSpace over the 63-day lookback period. | Verify whether this WorkSpace is still needed by the assigned user. If temporarily not needed, consider switching to Auto Stop mode. If the user no longer requires access, consider deleting the resource. +Amazon SageMaker endpoints | Invocations | The endpoint had zero invocations over the 14-day lookback period. | Verify whether this endpoint is still in use. If infrequently used, consider enabling scale-to-zero functionality for inference components if supported. If no longer required, consider deleting the resource.