Cedar Cloud Storage Usage
Cedar Cloud’s storage chart divides capacity by account and then by service. The inner ring answers who owns the storage, while the outer ring shows whether backups, media, logs or warehouse data drive the total. This hierarchy is useful in a cost review because it points teams toward the areas worth investigating before applying retention or lifecycle policies. The figures are in terabytes and should come from a dated inventory snapshot in a working report. Do not use the chart alone to decide what can be deleted: backups and logs may have recovery or compliance requirements. Pair it with retention rules and cost information. If there are dozens of buckets or folders, aggregate them before making a sunburst so the visual remains readable.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
Cloud-cost and capacity review.
Key decisions
- Identify ownership: use account names as the inner categories.
- Target the largest child: backups are the first storage-reduction candidate.
- Refresh snapshots: storage totals change, so date the source data.
When to reuse this
Use for a limited set of cloud accounts and storage services with a common unit.
Frequently asked questions
Why group by account first?
Can values be costs instead of terabytes?
Should temporary data be separate?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.