AWS compute-optimizer documentation change
Summary
Expanded idle resource detection criteria for EC2 instances and Auto Scaling groups to include GPU metrics (utilization, encoder usage, memory usage). Updated references from 'RDS databases' to 'Aurora and RDS databases'.
Security assessment
Changes focus on improving resource optimization by adding GPU-related idle metrics. No evidence of addressing security vulnerabilities or weaknesses. While deleting idle resources improves security hygiene, the documentation change itself doesn't directly reference security risks.
Diff
diff --git a/compute-optimizer/latest/ug/view-idle-recommendations.md b/compute-optimizer/latest/ug/view-idle-recommendations.md index 3fa3fde42..093d8dede 100644 --- a//compute-optimizer/latest/ug/view-idle-recommendations.md +++ b//compute-optimizer/latest/ug/view-idle-recommendations.md @@ -19 +19 @@ Compute Optimizer helps you identify idle resources that can be deleted or stopp - * Amazon RDS databases + * Amazon Aurora and RDS databases @@ -45,2 +45,18 @@ Resource | Metric analyzed | Idle criteria | Recommended action -Amazon EC2 instances | CPU utilization and network IO | The peak CPU utilization is below 5% and your network I/O is less than 5MB/day over the 14-day lookback period. | Verify whether you need this instance. If you don't need it, consider deleting this instance. -EC2 Auto Scaling groups | CPU utilization and network IO | The EC2 Auto Scaling group has no instances with more than 5% peak CPU utilization or 5MB/day network utilization over the 14-day lookback period. | Verify whether you need this group. Consider scaling down this group to one instance or consider deleting it. +Amazon EC2 instances | CPU utilization, network IO, GPU utilization, GPU encoder usage, and GPU memory usage | The peak CPU utilization is below 5% and your network I/O is less than 5MB/day over the 14-day lookback period. G or P instance types are considered idle if they meet the following criteria over the 14-day lookback period: + + * GPU isn’t actively working for more than 99% of the lookback period + * GPU encoder isn't used for 99% or more of the instance's runtime + * GPU memory usage at instance level is less than 5% + * CPU maximum utilization is less than 5% + * Network utilization is less than 5 MB/day + +| Verify whether you need this instance. If you don't need it, consider deleting this instance. +EC2 Auto Scaling groups | CPU utilization, network IO, GPU utilization, GPU encoder usage, and GPU memory usage | The EC2 Auto Scaling group has no instances with more than 5% peak CPU utilization or 5 MB/day network utilization over the 14-day lookback period. EC2 Auto Scaling groups that use G or P instance types are considered idle if the instances meet the following criteria over the 14-day lookback period: + + * GPU isn’t actively working for more than 99% of the lookback period + * GPU encoder isn't used for 99% or more of the instance's runtime + * GPU memory usage at instance level is less than 5% + * CPU maximum utilization is less than 5% + * Network utilization is less than 5 MB/day + +| Verify whether you need this group. Consider scaling down this group to one instance or consider deleting it. @@ -54 +70 @@ Amazon ECS services on Fargate | CPU utilization and memory utilization | The -Amazon RDS databases | Database connections, read/write IOPS, and CPU utilization | **RDS for MySQL and RDS for PostgreSQL** The DB instance is not a read replica, and had no database connections, low CPU usage, and low read/write activity over the lookback period. **Aurora MySQL and Aurora PostgreSQL** The DB instance is not part of a secondary cluster in an Aurora Global Database, and had no database connections, low CPU usage, and low read/write activity over the lookback period. | Verify whether you need this DB instance. If you don’t need this instance temporarily, you can stop RDS MySQL and RDS PostgreSQL DB instances for up to 7 days. If you no longer need this instance, you can create a DB snapshot and delete the instance. For idle Aurora MySQL and Aurora PostgreSQL instances, you can also change the DB instance class to db.serverless. +Amazon Aurora and RDS databases | Database connections, read/write IOPS, and CPU utilization | **RDS for MySQL and RDS for PostgreSQL** The DB instance is not a read replica, and had no database connections, low CPU usage, and low read/write activity over the lookback period. **Aurora MySQL and Aurora PostgreSQL** The DB instance is not part of a secondary cluster in an Aurora Global Database, and had no database connections, low CPU usage, and low read/write activity over the lookback period. | Verify whether you need this DB instance. If you don’t need this instance temporarily, you can stop RDS MySQL and RDS PostgreSQL DB instances for up to 7 days. If you no longer need this instance, you can create a DB snapshot and delete the instance. For idle Aurora MySQL and Aurora PostgreSQL instances, you can also change the DB instance class to db.serverless.