/

/

Find unattached volumes, underused disks and growing backups

Find unattached volumes, underused disks and growing backups

Find unattached volumes, underused disks and growing backups

Surface storage waste and idle resources by owner, so each team gets a short cleanup list with the cost of doing nothing.

Runs in

Claude · Slack

First optimization recommendation

The next day

ROI

Pays for itself with the first recommendation you act on

List unattached volumes and underused disks by team with their monthly cost.

› get_context

› get_context

› query ↗ Explorer

› query ↗ Explorer

Unattached EBS volumes: 37, €1,940/month, 21 of them owned by Data (left over from the Spark migration). Snapshot spend tripled in 6 months in the backups account.

Owners delete, archive or keep each item.

Playbook

What the agent does

From what Costory notices to what you decide. Costory suggests the next step in conversation, and you decide whether to go ahead.

Costory notices

Unattached volumes or growing snapshots are detected.

Costory investigates

01

Use the storage template

Unattached volumes, underused disks, backup growth and high-cost storage classes in one dashboard.

02

Attach owners

Virtual Dimensions route each item to a team.

03

Claude shortlists

A cleanup list per team with the monthly cost of each item.

04

Post to the team

The list lands in the team's Slack channel.

Where you see it

Claude

You decide

Owners delete, archive or keep each item.

Why it matters

Orphaned disks and forgotten snapshots grow quietly. No single item is big enough to notice; together they are.

Who it’s for

Platform engineers, engineering managers

Where it runs

Claude · Slack

What you get

What lands in front of your team

Owned cleanup lists

Each team sees only its own waste.

Cost of inaction

Monthly cost on every item.

Recurring hygiene

A monthly reminder in Slack.

Sources and assistants

What it connects

The billing data, context and assistants this playbook uses. Each links to its setup page.

The billing data, context and assistants this playbook uses. Each links to its setup page.

Example prompts

Or drive it yourself

The agent runs this on its own once set up. These prompts open in Claude, pre-filled, to set it up, review it or dig into a result.

The agent runs this on its own once set up. These prompts open in Claude, pre-filled, to set it up, review it or dig into a result.

Find

List unattached volumes and underused disks by team with their monthly cost.

Trend

Which backup and snapshot costs grew the most over the last 6 months, and who owns them?

FAQ

Questions about this playbook

Does Costory guarantee savings?

No. The agent investigates and recommends with the evidence attached; your team decides what to change. Impact figures are estimates based on your own data.

How long does this playbook take to set up?

Connecting your billing data and the Costory MCP takes under 30 minutes with Terraform or CloudFormation. The playbook itself takes minutes: pick the scope, the trigger and the Slack channel. The first billing data lands the next day, and the agent starts from there.

Can we adjust what the agent does?

Yes. You choose the trigger, the scope (team, service, environment), the channel and the format, and you can pause or change it at any time.

Does Costory change anything in our cloud accounts?

No. Costory reads billing exports and the metrics you connect, and has no write access to your cloud. Actions it takes create Costory objects only: alerts, reports, dashboards and events. Your team stays in control of every change.

Step-by-step guide in the Costory docs

Put this playbook on call

Included in every plan, from €250/month. 30-day free trial: connect in under 30 minutes, get your first optimization recommendation the next day.

First optimization recommendation

The next day

ROI

Pays for itself with the first recommendation you act on

Setup

About 30 minutes

Data residency

EU

Access

Read-only on your cloud