Identifying unused resources

5 minutes 5 Questions

Identifying unused resources is a critical practice for AWS Solutions Architects focused on continuous improvement and cost optimization. This process involves systematically discovering and analyzing AWS resources that are provisioned but not actively utilized, leading to unnecessary costs and operational overhead. AWS provides several native tools for this purpose. AWS Cost Explorer offers usage reports and recommendations for underutilized resources. AWS Trusted Advisor scans your infrastructure and identifies idle load balancers, unassociated Elastic IP addresses, and underutilized EC2 instances. AWS Compute Optimizer analyzes utilization metrics to recommend optimal resource configurations. Key resources to monitor include: EC2 instances with consistently low CPU and network utilization, unattached EBS volumes that remain after instance termination, unused Elastic IP addresses incurring hourly charges, idle RDS instances with minimal connections, obsolete EBS snapshots and AMIs, unused NAT Gateways, and dormant Lambda functions. Implementation strategies involve setting up CloudWatch alarms for utilization thresholds, creating custom dashboards to visualize resource consumption patterns, and leveraging AWS Config rules to detect non-compliant or unused resources. Organizations should establish tagging strategies to track resource ownership and purpose, making it easier to identify orphaned assets. Automation plays a vital role through scheduled Lambda functions that query resource utilization metrics and generate reports. AWS Systems Manager Automation can remediate by stopping or terminating unused resources based on predefined criteria. Best practices include conducting regular monthly audits, implementing lifecycle policies for storage resources, using Reserved Instance utilization reports, and establishing governance frameworks with clear resource ownership. Teams should create runbooks for decommissioning processes and maintain documentation of resource dependencies. The financial impact can be substantial, as studies show organizations typically waste 30-35% of cloud spend on unused or underutilized resources. Continuous monitoring and optimization ensure infrastructure remains aligned with actual business requirements while maximizing return on cloud investments.

Identifying Unused Resources - AWS Solutions Architect Professional Guide

Why Identifying Unused Resources is Important

Identifying unused resources is a critical practice for cloud cost optimization and operational efficiency. Organizations often accumulate resources over time that are no longer serving their intended purpose, leading to unnecessary costs that can represent 20-30% of cloud spending. Beyond cost implications, unused resources create security vulnerabilities, complicate infrastructure management, and contribute to configuration drift.

What Are Unused Resources?

Unused resources in AWS include:

• Unattached EBS Volumes - Storage volumes that exist but are not connected to any EC2 instance
• Idle EC2 Instances - Instances running with minimal or no CPU/network utilization
• Unused Elastic IP Addresses - EIPs allocated but not associated with running instances
• Orphaned Snapshots - EBS snapshots whose source volumes have been deleted
• Unused Load Balancers - ALBs/NLBs with no healthy targets or zero traffic
• Idle RDS Instances - Database instances with no connections over extended periods
• Unattached NAT Gateways - NAT Gateways in subnets with no active routes
• Unused Lambda Functions - Functions that have not been invoked for extended periods

How to Identify Unused Resources

AWS Cost Explorer
Provides usage reports and recommendations for rightsizing. Use the Resource Optimization feature to find underutilized resources based on CPU, memory, and network metrics.

AWS Trusted Advisor
Offers checks for idle resources including:
- Low utilization EC2 instances
- Underutilized EBS volumes
- Idle load balancers
- Unassociated Elastic IP addresses

AWS Compute Optimizer
Analyzes utilization metrics and provides recommendations for EC2 instances, Auto Scaling groups, EBS volumes, and Lambda functions.

Amazon CloudWatch
Set up custom dashboards and alarms to monitor utilization metrics. Key metrics include:
- CPUUtilization for EC2
- VolumeReadOps/VolumeWriteOps for EBS
- DatabaseConnections for RDS
- Invocations for Lambda

AWS Config Rules
Create custom or managed rules to detect unused resources automatically. Examples include checking for unattached EBS volumes or instances missing required tags.

AWS Cost and Usage Reports (CUR)
Generate detailed reports that can be analyzed with Athena or QuickSight to identify patterns of unused resources.

Best Practices for Managing Unused Resources

1. Implement Tagging Strategies - Enforce mandatory tags for owner, project, and expiration date
2. Automate Cleanup - Use Lambda functions triggered by CloudWatch Events to terminate or snapshot idle resources
3. Regular Audits - Schedule weekly or monthly reviews using Trusted Advisor and Cost Explorer
4. Set Budget Alerts - Configure AWS Budgets to notify when spending exceeds thresholds
5. Use Resource Groups - Organize resources for easier tracking and lifecycle management

Exam Tips: Answering Questions on Identifying Unused Resources

• When a question mentions cost optimization and finding idle resources, think AWS Trusted Advisor and AWS Compute Optimizer first

• For questions about automated detection of unused resources, AWS Config Rules combined with Lambda remediation is typically the preferred solution

• If the scenario involves analyzing historical usage patterns, consider Cost and Usage Reports with Athena for complex queries

• Questions mentioning rightsizing recommendations specifically point toward AWS Compute Optimizer

• For real-time monitoring of resource utilization, CloudWatch metrics and alarms are the answer

• When asked about enterprise-wide visibility across multiple accounts, think AWS Organizations with consolidated Trusted Advisor or Cost Explorer

• Remember that Trusted Advisor checks vary by support plan - Business and Enterprise support provide more checks

• For questions involving automatic remediation, the pattern is typically: CloudWatch Event/EventBridge → Lambda → Resource Action

• If a question asks about identifying unused resources at scale, consider AWS Systems Manager Inventory combined with Config Rules
Test mode:
More Identifying unused resources questions
29 questions (total)

Other Continuous Improvement for Existing Solutions concepts

Alerting and automatic remediationAll-at-once deployment strategiesAmazon CloudFrontAmazon CloudWatch monitoring and loggingApplication growth and usage trendsAutomated security remediationAutomated vulnerability responseAutomation opportunities in solutionsAuto scaling and instance fleetsAuto scaling strategiesAWS Config rules for monitoringAWS Global AcceleratorAWS Lambda for automated remediationAWS solutions for configuration automationAWS WavelengthBackup practices and methodsBilling alarm designBlue/green deployment strategiesBusiness requirements to metrics translationChaos engineering practicesCloudWatch Logs InsightsCloudWatch metrics and monitoringCost allocation with taggingCost and Usage Reports analysisCost-conscious architecture choicesCost management and alertingData regulatory requirementsData replication methodsData retention requirementsData sensitivity classificationData transfer cost reductionDeployment process improvementsDisaster recovery methods and toolsDisaster recovery planningEC2 placement groupsEdge computing servicesElastic features and servicesElastic Load BalancingFailure scenario engineeringHigh availability patternsIdentifying underutilized resourcesKey performance indicators (KPIs)Load balancing strategiesNetworking cost optimizationNew technology and managed service adoptionOptimal logging and monitoring strategiesPatch and update processesPatching practices and automationPerformance bottleneck identificationPrinciple of least privilege auditingReliability gap evaluationReserved Instance planningResiliency patternsResource rightsizing for costRightsizing based on requirementsRolling deployment strategiesSavings Plans selectionScaling policies for cost optimizationSecrets Manager best practicesSecure secrets and credentials managementSecurity at every layer reviewSecurity remediation techniquesSecurity-specific AWS solutionsSelf-healing architecturesService level agreements (SLAs)Service quotas managementSingle point of failure remediationSpot Instance strategiesSystems Manager for configuration managementSystems Manager for secrets managementTesting remediation solutionsUsage report analysisUser and service traceability