DEVOPS
Attribute S3 storage-cost surges to the bucket, prefix, and owning repo
On a schedule, this workflow finds S3 buckets whose storage cost jumped, identifies the fastest-growing prefixes, traces each bucket to its owning GitHub repo via tags.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled S3 storage-cost sweep
- ActionPull per-bucket cost deltas from DatadogDatadog
- ActionFind fastest-growing prefixes in flagged bucketsAWS S3
- LogicMap bucket to owning repo via tagsGitHub
- OutputAlert owning team in Slack with attributionSlack
What it does
Narrows an S3 storage-cost surge down to the exact bucket and prefix driving it, then attributes ownership. It reads per-bucket cost and size metrics, locates the prefixes that grew most, maps each bucket to its provisioning repo from resource tags, and notifies the responsible team.
When to use it
Use it when S3 line items creep up and nobody knows which bucket or which job is writing the data. Best for teams with many shared buckets tagged with an owning repo or team.
How it works
- 1A schedule kicks off the storage-cost sweep on a regular cadence.
- 2The flow pulls per-bucket cost deltas from Datadog cloud-cost metrics.
- 3For each flagged bucket it inspects S3 to find the prefixes with the largest size growth.
- 4A logic step maps the bucket to its owning GitHub repo using the bucket's tags.
- 5It composes an attribution summary: bucket, top prefixes, dollar delta, owning repo.
- 6The summary posts to the owning team's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect AWS S3Buckets, objects, signed URLs.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.