Scanned 14 accounts across 3 regions in 90 seconds.
3 items need attention before standup:
⚠ ALB target health: 3 unhealthy targets in prod
⚠ Backup job failed twice overnight (staging)
⚠ New AI agent appeared Saturday: full EC2 access, no owner
Correlated CloudTrail, deploys, and config changes.
Root cause: deploy v1.9.2 at 02:14 UTC removed the Lambda concurrency limit.
Blast radius: 3 downstream services. No data loss detected.
✓ Fix drafted. Awaiting your approval.
Traversed roles, policies, SCPs, and permission boundaries.
7 identities can delete: 2 direct, 4 role-assumed, 1 via a legacy exception.
⚠ Two are service accounts with no rotation in 14 months.
Queried CloudTrail, GitHub, Datadog, and PagerDuty.
4 changes across 3 services. One caused the Saturday cost spike.
✓ 2 clean deploys, 1 Terraform config change, 1 capacity rule update.
Walked the dependency graph two hops downstream.
orders-db connection pool saturates at 2.1x current load.
Redis cluster and NAT gateway need headroom before launch.
Checked sidecars, cron jobs, alarms, and IAM for this service.
4 things: a cron sidecar, 2 alarms pinned to instance IDs, an instance profile, a hardcoded EIP.
✓ Pre-flight checklist drafted for this migration.
42 services across 14 accounts. Ownership inferred from runtime behavior.
Tier 1: checkout, payments, auth. Platform team owns 60% of infra.
✓ Walkthrough generated. Ask me about any node.
Timeline reconstructed from 214 events across 4 systems.
Root cause, blast radius, and remediation steps drafted.
✓ 3 follow-up actions proposed. Ready to paste.