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
Cloud Resource Monitoring Dashboard Example
PostedMarch 29, 2025
UpdatedMarch 29, 2025
ByKevin McCaffrey
ID: SUS_SUS2_4_cloud-resource-monitoring-dashboard
Code: SUS2_4
Overview
This example dashboard focuses on identifying and decommissioning unused or underutilized cloud resources. By actively monitoring resource usage, you can align capacity with actual demand, reduce operational costs, and improve sustainability. Below is an example approach for a monitoring dashboard to ensure you are utilizing resources effectively.
Key Components
- Resource Inventory: Collect a list of all active compute instances, storage volumes, and other resources to establish a baseline. This could be done using AWS services such as AWS Config, AWS Resource Access Manager, or AWS Organizations.
- Metrics Collection: Utilize CloudWatch metrics to track CPU and memory utilization, network usage, and storage I/O. Compare historical usage patterns to determine stagnant or under-used resources.
- Threshold Alarms: Set up overhead thresholds that automatically highlight resources that remain idle or below a set utilization level over a given time (e.g., instances running at CPU usage under 5% for consecutive days).
- Cost Reports: Integrate AWS Cost Explorer data to reveal cost trends and correlate them with usage metrics. This helps pinpoint areas where potential cost savings can be achieved by decommissioning or rightsizing instances.
- Automated Recommendations: Leverage AWS Instance Scheduler and AWS Auto Scaling to match capacity with demand. For non-critical workloads, schedule off-hours to reduce run time and resources used.
- Actionable Insights: Design the dashboard to offer next steps, such as archiving data to lower-cost storage tiers or shutting down resources that are no longer needed.
Implementation Considerations
- Use tags to categorize resources by environment, owner, or project, making it easier to identify and decommission underutilized assets.
- Ensure all stakeholders (e.g., application owners, finance teams) have visibility into usage reports and cost breakdowns.
- Regularly review the dashboard to confirm that resources continue to align with changing demand profiles.
By following these steps and maintaining a proactive decommissioning process, you can minimize resource waste, reduce costs, and support your sustainability objectives.
Table of Contents