IT OPS
AWS Access Key and Secret Rotation Age Audit
Inventories IAM access keys and stored secrets, flags any credential older than your rotation policy.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule (security audit cadence)
- ActionRead credential inventory manifest from S3AWS S3
- LogicCompute key age and flag past rotation SLA
- LogicFilter to overdue credentials, group by owner
- ActionCreate one Linear rotation issue per ownerLinear
- OutputPost overdue-by-team digest to SlackSlack
What it does
Walks your AWS account's IAM access keys and the secrets you track in an inventory, computes each credential's age, and compares it against your rotation SLA. Anything past due is grouped by owner and turned into actionable rotation work rather than a one-off alert that gets ignored.
When to use it
When compliance or security requires rotating long-lived credentials on a schedule (for example, every 90 days) and you need an auditable record that overdue keys were caught and assigned. Good for SOC 2 and ISO evidence trails.
How it works
- 1A weekly schedule starts the audit.
- 2The flow reads the credential inventory manifest from an S3 bucket and lists active access keys.
- 3For each credential it calculates age in days and marks it overdue when it exceeds the policy threshold.
- 4A filter drops compliant credentials and keeps only the overdue set, grouped by owning team.
- 5One Linear issue per owner is created with the affected key IDs, ages, and the rotation runbook link.
- 6A digest of overdue counts by team is posted to Slack for visibility at the next security standup.
Set it up
What you configure once, before turning it on.
- 1Connect AWS S3Buckets, objects, signed URLs.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
Self-Service Reclaim Email for Idle Users
Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.
Reconcile SSO logins against expense spend to find unmanaged tools
Joins SSO usage data with expense/payment records in Snowflake to surface tools that are being used but not paid for, or paid for but never logged.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
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.