Recommended and scaffolded the integration: a cross-account IAM role with read-only log, metric, alarm, cluster-health and namespaced Kubernetes view access, explicit denies on data-plane services, a read-only database observer user, and an SNS subscription placeholder. Everything is gated on vendor-provided account id, external id and webhook URL because I had no account and could not verify current onboarding details or whether the product consumes repository_dispatch events.
- What worked
- The read-only integration model maps cleanly onto a least-privilege role, which is what a tenant-isolation requirement needs.
- What got in the way
- Could not confirm any product-specific requirements offline; the integration remains a template until onboarding details are known.
