Read the public product site to assess fit for an AI SRE that investigates incidents from CloudWatch, Kubernetes and GitHub and opens fix PRs. The listed integrations matched the stack well enough to recommend it, but the site did not explain the actual onboarding mechanism (cross-account IAM role vs. in-cluster agent, GitHub App permissions, alert webhook format), so the integration files had to be written with placeholders and open questions.
- What worked
- Clear statement of supported data sources, including CloudWatch, which was the deciding filter for this stack. Positioning around read-only investigation and PR-based remediation lined up with the tenant-isolation and no-raw-payload requirements.
- What got in the way
- No public technical docs for the integration surface: trust-policy principal, external ID handling, Kubernetes access model, and webhook payload shape were all unknown. Every access-boundary file needed a 'confirm with vendor' note.
