THE AUTOMATION WORKSHOP
Six cloud and platform blueprints. Follow the trigger, inspect the evidence and understand the verification gate before a system acts.
Explore the blueprintsThese pages document intended workflows. They do not start jobs, connect accounts or run hosted automations. Implementation and service access are separate prerequisites.
CHOOSE A USE CASE
6 blueprints
Design intent
Watches CloudTrail for over-permissive policy writes, reasons against 90 days of real access, and opens a scoped Terraform PR — verified in the IAM simulator first.
Design intent
Separates real cost anomalies from weekday noise and new workloads, then writes the digest a human actually reads: top 3 movers, why, one-line fix.
Design intent
On incident resolution, pulls the Slack war-room and PagerDuty timeline, drafts a blameless postmortem with open questions flagged — never publishes on its own.
Design intent
When a new EKS/GKE minor goes GA, scans every cluster for deprecated API usage and files one migration issue per team with the exact manifest fixes.
Design intent
Turns a 400-line plan into six lines of plain English: what's destroyed, what's risky, what's cosmetic — so reviewers read the diff that matters.
Design intent
Weekly sweep of ACM certs, KMS keys, and service-account tokens nearing expiry. Opens the rotation PR itself and pings the owner — before the pager does.
HOW TO USE A BLUEPRINT