Storage class and tiering recommendations for S3 and Cloud Storage
Find buckets in expensive storage classes, check access patterns, and get lifecycle and tiering suggestions per owner.
Runs in
Claude · Slack
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Which S3 buckets in Standard storage have very low request costs relative to storage cost? Group by owner.
events-archive (Data) holds 410 TB in S3 Standard with almost no GET requests in 90 days. A transition to Glacier Instant Retrieval after 30 days would lower storage cost on that bucket by roughly 60%.
The data owner approves lifecycle rules.
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
A bucket keeps growing in an expensive class with little access.
Costory investigates
01
Rank storage cost
By bucket, class and owner.
02
Check access
Request and retrieval costs show how often data is read.
03
Claude proposes
Lifecycle rules and target classes per bucket.
04
Owners decide
Recommendations go to the data owner.
Where you see it
Claude
You decide
The data owner approves lifecycle rules.
Why it matters
Data lands in standard storage and stays there. Moving cold data is easy once you know which buckets matter.
Who it’s for
Data engineers, platform teams
Where it runs
Claude · Slack
What you get
What lands in front of your team
Prioritized buckets
The few buckets that drive most storage cost.
Concrete lifecycle rules
Suggestions your team can apply.
Impact estimate
The expected monthly change, before you act.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Rank
Which S3 buckets in Standard storage have very low request costs relative to storage cost? Group by owner.
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
Related playbooks
Run these alongside it
Costory notices
Unattached volumes or growing snapshots are detected.
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.
See the playbook
Costory notices
A dbt model's cost jumps or a new expensive model appears.
BigQuery cost by dbt model, package and team
Label BigQuery jobs with dbt metadata and allocate processing and storage costs to models, packages and owners.
See the playbook
Costory notices
Cross-AZ or egress cost jumps on a service.
Understand cross-AZ and egress costs, then reduce them
The agent breaks down data transfer by provider, service, account and team, flags jumps and points to the architecture choices behind them.
See the playbook
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