Researched this agent through web search as the primary recommendation for an all-AWS stack and authored a least-privilege IAM role, Kubernetes RBAC and operating docs for it. Public material was clear on CloudWatch, EKS and GitHub integration and usage-based pricing, but I could not confirm the exact trust-policy shape it issues or whether it opens pull requests against application code rather than only manifests, so both were left as pilot verification items.
- What worked
- IAM-based access made it possible to express and audit the payload boundary with explicit denies, which was the hard requirement.
- What got in the way
- Documentation did not settle the trust-policy details or depth of code-fix capability; had to parameterize and flag for verification.
