Search for the Right Document
-
Planning and Strategy
-
Requirements
-
- Customer Feedback Report
- Capacity Planning Report
- Stakeholder Input Record Example
- List of Customer Journeys
- Reverse Engineering: Legacy Inventory Management System
- Task Analysis: Customer Support Ticketing System
- Requirements Workshop: Employee Onboarding System
- Mind Mapping Session: Mobile Travel Planning App
- SWOT Analysis: New Food Delivery App
- Storyboarding Session: Mobile Health & Fitness App
- User Story Mapping Session: Online Grocery Shopping Platform
- Focus Group: Requirements Gathering for Fitness Tracking App
- Prototyping Session Example: E-Commerce Website
- Document Analysis Example: Hospital Management System Requirements
- Observation Session: Warehouse Operations
- Survey: E-Learning Platform Requirements
- Workshop Session Example: Requirements Gathering for Mobile Banking App
- Interview Session Example: Requirements Gathering for CRM System
- Event Storming Session: Retail Order Management System
- Generate Requirements from Meeting Transcripts
- Requirements Definition Process Example
- ISO/IEC/IEEE 29148 Systems and Software Requirements Specification (SRS) Example Template
- Show all articles ( 7 ) Collapse Articles
-
- Customer Requirement Document (CRD)
- Customer Journey Map
- Internal Stakeholder Requirement Document (ISRD)
- Internal System Use Case Example: CI/CD System
- User Stories & Acceptance Criteria
- Technical Specification Document Example
- BDD Scenarios Example for User Login
- Non-Functional Requirements Example
- Functional Requirements Specification Example
- Use Case Example: User Login
-
-
Communication
-
Design
- Functional Specification for Inventory Management Workload
- Technical Specification for Inventory Management System
-
- Overview of Design Diagrams
- High-Level System Diagram Standards
- User-Flow Diagram Standards
- System Flow Diagram Standards
- Data-Flow Diagram (DFD) Standards
- Sequence Diagram Standards
- State Diagram Standards
- Flowchart Standards
- Component Diagram Standards
- Network Diagram Standards
- Deployment Diagram Standards
- Entity-Relationship Diagram (ERD) Standards
- Block Diagram Standards
-
Operations
-
-
- Creating a Visualization Dashboard Guide
- Business Outcome Metrics Dashboard Guide
- Trace Analysis Dashboard
- Dependency Health Dashboard
- Guidelines for Creating a Telemetry Dashboard
- Guidelines for Creating a User Behavior Dashboard
- Improvement Tracking Dashboard
- Customer Status Page Overview
- Executive Summary Dashboard Overview
- Operations KPI Dashboard Example
- Stakeholder-Specific Dashboard Example
- Business Metrics Dashboard Example
- System Health Dashboard Example
- Guide for Creating a Dependency Map
-
-
-
- Event Management Policy Example
- Incident Management Policy
- Problem Management Policy
- Example Training Materials for Escalation
- Runbook Example: Incident Management with Escalation Paths
- Escalation Path Document Example
- Incident Report Example: Failed Deployment Investigation
- Incident Playbook Example: Investigating Failed Deployments
- Contingency Plan for Service Disruptions
-
-
-
Testing
-
Development
< All Topics
Print
Unused Assets Decommissioning Checklist Example
PostedMarch 29, 2025
UpdatedMarch 29, 2025
ByKevin McCaffrey
ID: SUS_SUS2_4_unused-assets-decommissioning-checklist
Code: SUS2_4
Overview
Decommissioning unused assets in your workload is essential to minimize resource waste, reduce operational costs, and enhance your sustainability efforts. By identifying and removing these unnecessary resources, you help ensure that only the required assets remain in service. This approach aligns with AWS Well-Architected best practices for sustainable resource management.
Checklist Steps
- Resource Inventory: Begin by generating an inventory of all running resources, such as EC2 instances, RDS databases, and unused EBS volumes.
- Usage Analysis: Investigate resource metrics (CPU, memory, and storage utilization) and identity access patterns to detect underutilized or obsolete items.
- Tagging and Identification: Apply consistent naming and tagging conventions to make it easier to track ownership, purpose, and relevance of each asset.
- Review and Approval: Develop a formal process for stakeholders to review and confirm whether an asset is truly unnecessary before you decommission it.
- Automated Alerts: Configure alerts or automated scripts to detect idle resources regularly and escalate for decommissioning.
- Document Decommissioning: Maintain records of assets you remove to allow auditing, cost analysis, and better decision-making.
Implementation Tips
- Scheduling: Schedule routine assessments (e.g., monthly or quarterly) to identify and decommission unused assets in a consistent manner.
- Automation: Use AWS tools like AWS Config, AWS Lambda, or AWS Systems Manager to automate detection and removal of obsolete resources.
- Policy Enforcement: Enforce policies that require regular tag validation, cost monitoring, and justification for underutilized or idle assets.
This example checklist helps you systematically reduce waste and maintain resources that align with your demand. Adopting a structured decommissioning process fosters a culture of sustainability and cost-awareness within your organization.
Table of Contents