Search for Well Architected Advice
-
Operational Excellence
-
- Resources have identified owners
- Processes and procedures have identified owners
- Operations activities have identified owners responsible for their performance
- Team members know what they are responsible for
- Mechanisms exist to identify responsibility and ownership
- Mechanisms exist to request additions, changes, and exceptions
- Responsibilities between teams are predefined or negotiated
-
- Executive Sponsorship
- Team members are empowered to take action when outcomes are at risk
- Escalation is encouraged
- Communications are timely, clear, and actionable
- Experimentation is encouraged
- Team members are encouraged to maintain and grow their skill sets
- Resource teams appropriately
- Diverse opinions are encouraged and sought within and across teams
-
- Use version control
- Test and validate changes
- Use configuration management systems
- Use build and deployment management systems
- Perform patch management
- Implement practices to improve code quality
- Share design standards
- Use multiple environments
- Make frequent, small, reversible changes
- Fully automate integration and deployment
-
- Have a process for continuous improvement
- Perform post-incident analysis
- Implement feedback loops
- Perform knowledge management
- Define drivers for improvement
- Validate insights
- Perform operations metrics reviews
- Document and share lessons learned
- Allocate time to make improvements
- Perform post-incident analysis
-
Security
-
- Separate workloads using accounts
- Secure account root user and properties
- Identify and validate control objectives
- Keep up-to-date with security recommendations
- Keep up-to-date with security threats
- Identify and prioritize risks using a threat model
- Automate testing and validation of security controls in pipelines
- Evaluate and implement new security services and features regularly
-
- Define access requirements
- Grant least privilege access
- Define permission guardrails for your organization
- Manage access based on life cycle
- Establish emergency access process
- Share resources securely within your organization
- Reduce permissions continuously
- Share resources securely with a third party
- Analyze public and cross-account access
-
- Perform regular penetration testing
- Deploy software programmatically
- Regularly assess security properties of the pipelines
- Train for Application Security
- Automate testing throughout the development and release lifecycle
- Manual Code Reviews
- Centralize services for packages and dependencies
- Build a program that embeds security ownership in workload teams
-
-
Reliability
-
- Be aware of service quotas and constraints in Cloud Services
- Manage service quotas across accounts and Regions
- Accommodate fixed service quotas and constraints through architecture
- Monitor and manage quotas
- Automate quota management
- Ensure sufficient gap between quotas and usage to accommodate failover
-
- Use highly available network connectivity for your workload public endpoints
- Provision Redundant Connectivity Between Private Networks in the Cloud and On-Premises Environments
- Ensure IP subnet allocation accounts for expansion and availability
- Prefer hub-and-spoke topologies over many-to-many mesh
- Enforce non-overlapping private IP address ranges in all private address spaces where they are connected
-
- Monitor end-to-end tracing of requests through your system
- Conduct reviews regularly
- Analytics
- Automate responses (Real-time processing and alarming)
- Send notifications (Real-time processing and alarming)
- Define and calculate metrics (Aggregation)
- Monitor End-to-End Tracing of Requests Through Your System
- Define and calculate metrics
- Send notifications
- Automate responses
-
- Monitor all components of the workload to detect failures
- Fail over to healthy resources
- Automate healing on all layers
- Rely on the data plane and not the control plane during recovery
- Use static stability to prevent bimodal behavior
- Send notifications when events impact availability
- Architect your product to meet availability targets and uptime service level agreements (SLAs)
-
-
Cost Optimization
-
- Establish ownership of cost optimization
- Establish a partnership between finance and technology
- Establish cloud budgets and forecasts
- Implement cost awareness in your organizational processes
- Monitor cost proactively
- Keep up-to-date with new service releases
- Quantify business value from cost optimization
- Report and notify on cost optimization
- Create a cost-aware culture
-
- Perform cost analysis for different usage over time
- Analyze all components of this workload
- Perform a thorough analysis of each component
- Select components of this workload to optimize cost in line with organization priorities
- Perform cost analysis for different usage over time
- Select software with cost effective licensing
-
-
Performance
-
- Learn about and understand available cloud services and features
- Evaluate how trade-offs impact customers and architecture efficiency
- Use guidance from your cloud provider or an appropriate partner to learn about architecture patterns and best practices
- Factor cost into architectural decisions
- Use policies and reference architectures
- Use benchmarking to drive architectural decisions
- Use a data-driven approach for architectural choices
-
- Use purpose-built data store that best support your data access and storage requirements
- Collect and record data store performance metrics
- Evaluate available configuration options for data store
- Implement Strategies to Improve Query Performance in Data Store
- Implement data access patterns that utilize caching
-
- Understand how networking impacts performance
- Evaluate available networking features
- Choose appropriate dedicated connectivity or VPN for your workload
- Use load balancing to distribute traffic across multiple resources
- Choose network protocols to improve performance
- Choose your workload's location based on network requirements
- Optimize network configuration based on metrics
-
- Establish key performance indicators (KPIs) to measure workload health and performance
- Use monitoring solutions to understand the areas where performance is most critical
- Define a process to improve workload performance
- Review metrics at regular intervals
- Load test your workload
- Use automation to proactively remediate performance-related issues
- Keep your workload and services up-to-date
-
-
Sustainability
-
- Scale workload infrastructure dynamically
- Align SLAs with sustainability goals
- Optimize geographic placement of workloads based on their networking requirements
- Stop the creation and maintenance of unused assets
- Optimize team member resources for activities performed
- Implement buffering or throttling to flatten the demand curve
-
- Optimize software and architecture for asynchronous and scheduled jobs
- Remove or refactor workload components with low or no use
- Optimize areas of code that consume the most time or resources
- Optimize impact on devices and equipment
- Use software patterns and architectures that best support data access and storage patterns
- Remove unneeded or redundant data
- Use technologies that support data access and storage patterns
- Use policies to manage the lifecycle of your datasets
- Use shared file systems or storage to access common data
- Back up data only when difficult to recreate
- Use elasticity and automation to expand block storage or file system
- Minimize data movement across networks
- Implement a data classification policy
- Remove unneeded or redundant data
-
- Articles coming soon
< All Topics
Print
Stop the creation and maintenance of unused assets
PostedDecember 20, 2024
UpdatedMarch 29, 2025
ByKevin McCaffrey
ID: SUS_SUS2_4
Decommissioning unused assets in your workload is essential to minimize resource waste, reduce operational costs, and enhance your sustainability efforts. By identifying and eliminating such assets, you ensure that only necessary resources are in use, which aligns with best practices for sustainable resource management.
Best Practices
Conduct Regular Resource Inventory Audits
- Perform scheduled evaluations of all cloud resources to identify assets that are unused or underutilized.
- Document and track the purpose, ownership, and usage metrics of each resource, ensuring you have clear visibility into their status.
- Retire or resize resources that are no longer necessary to eliminate waste and maintain a lean inventory.
Automate Unused Resource Detection
- Leverage monitoring and governance tools to detect idle resources (such as EC2 instances with low CPU utilization).
- Automate notifications and trigger workflows that initiate the decommissioning process upon detection of unused resources.
- Ensure scheduled scripts or functions run regularly to minimize the chance of overlooked waste.
Implement Lifecycle Management Policies
- Define policies for creating, reviewing, and retiring resources in line with organizational needs.
- Use tagging standards to designate each resource’s purpose, department, and lifecycle stage to simplify tracking.
- Incorporate cost, usage, and sustainability metrics into your lifecycle policies to promote efficient resource usage.
Educate and Empower Teams on Resource Efficiency
- Train teams on best practices for cloud resource provisioning, emphasizing the importance of sustainable deployment patterns.
- Share guidelines on requesting, sizing, and decommissioning resources, ensuring all stakeholders maintain minimal waste.
- Foster a culture of ownership and accountability, rewarding initiatives that proactively reduce unused resources and drive sustainable outcomes.
Questions to ask your team
- Do you periodically review your environment for unused or idle resources and decommission them promptly?
- Have you established automated mechanisms (e.g., scripts or tools) to detect and remove underutilized cloud assets, such as stopped instances, stale backups, or unattached volumes?
- Are there policies or processes in place to ensure new resources are only provisioned when strictly needed and decommissioned as soon as they become unnecessary?
- Do you maintain an updated inventory of all cloud resources to identify and act on orphaned or obsolete assets regularly?
- Have you implemented tagging strategies to help track resource ownership and usage, enabling you to spot and eliminate unused resources more effectively?
Who should be doing this?
Governance and Compliance Lead
- Establish policies and standards to prevent unused asset creation
- Monitor compliance with resource usage guidelines
- Review and approve decommissioning plans
DevOps Engineer
- Implement automation to detect and remove unused resources
- Manage infrastructure as code for efficient provisioning and decommissioning
- Collaborate with teams to ensure new builds do not introduce unnecessary resources
Solutions Architect
- Design scalable architectures that only provision required resources
- Evaluate resource utilization to identify potential areas for optimization
- Advise on right-sizing and decommissioning strategies
IT Procurement Manager
- Oversee asset procurement requests to align with usage requirements
- Collaborate with technical teams to ensure no overprovisioning occurs
- Track lifecycle of assets to confirm timely decommissioning and cost savings
What evidence shows this is happening in your organization?
- Unused Asset Decommissioning Checklist: A structured checklist that guides teams in identifying and retiring unused or underutilized resources to reduce waste.
- Resource Usage Policy: A policy document outlining standards and guidelines for continuous assessment of resource usage, ensuring no excess assets are created or maintained.
- Cloud Resource Utilization Dashboard: A real-time dashboard for monitoring provisioned cloud resources, highlighting idle or underutilized instances to prompt timely decommissioning.
- Asset Cleanup Runbook: An operational guide providing detailed procedures for identifying, reviewing, and removing obsolete assets within the cloud environment.
Cloud Services
AWS
- AWS Trusted Advisor: Helps identify unused or underutilized resources and provides recommendations to reduce waste.
- AWS Cost Explorer: Analyzes cost and usage to detect areas of over-provisioning and highlight idle resources.
- AWS Compute Optimizer: Provides recommendations to right-size or terminate underutilized AWS resources based on usage metrics.
Azure
- Azure Advisor: Evaluates resource configuration and usage, and suggests ways to reduce impact by removing unused resources.
- Azure Monitor: Collects and analyzes data on resource performance, helping identify and decommission idle assets.
- Azure Resource Graph: Enables exploration of resources across subscriptions to identify unused assets for decommissioning.
Google Cloud Platform
- Cloud Recommender: Offers sizing recommendations and identifies idle or underutilized resources to reduce waste.
- Cloud Monitoring: Provides metrics and alerts that help pinpoint underused resources and optimize usage.
- Cloud Logging: Logs resource usage and helps identify unused assets that can be shut down or decommissioned.
Table of Contents