SyncAwsEc2Volume: Attached and Unattached time

Business Case

We are requesting a Cloudability enhancement to expose attached time and unattached time for EC2Volume resources. Today, storage cost visibility shows what we are spending, but not how long a volume was actually in use versus sitting idle. That gap limits our ability to accurately identify waste, improve allocation decisions, and automate cleanup of orphaned storage.

This feature would create value in four ways:

• Cost optimization: Unattached EBS volumes continue to incur charges. Tracking unattached duration would help us identify persistent waste instead of relying on one-time snapshots.
• Better prioritization: A volume unattached for 2 hours is very different from one unattached for 30 days. Time-based visibility helps teams focus on the highest-value cleanup opportunities.
• Improved governance: Attached/unattached duration supports stronger policies for retention, cleanup, and exception handling across engineering and operations teams.
• More accurate showback/chargeback: Knowing when storage was actively attached helps allocate cost more fairly to applications, teams, and environments.

Why Current Reporting Is Not Enough

Current cost and inventory views answer what exists and what it costs, but not how long it was useful. For EBS volumes, the duration of unattached state is often the key signal for waste, compliance risk, and operational hygiene.

Requested Capability

Add resource-level reporting for EC2Volume/EBS that includes:

• Total attached duration over a selected reporting period
• Total unattached duration over a selected reporting period
• Timestamp of last attach and last detach event
• Ability to filter, group, and alert on unattached duration thresholds

Business Impact

This would help us:

• Reduce persistent storage waste
• Improve storage lifecycle management
• Support automated remediation workflows
• Strengthen FinOps reporting with more actionable metrics
• Give engineering leaders clearer evidence for cleanup and optimization

Summary of the Feature Requirement:

We would like Cloudability to provide attached and unattached time metrics for AWS EC2Volume/EBS resources. This would materially improve our ability to identify idle storage, prioritize remediation, enforce governance policies, and allocate storage costs more accurately. Cost alone does not distinguish between temporarily detached volumes and long-running orphaned volumes; duration-based state tracking would make Cloudability significantly more actionable for FinOps and infrastructure operations.