Picked this agent for investigation because the stack was all AWS, then wrote Terraform for it using AWS's sample repos and the managed policy reference. I never ran it against the live service. The sample repos showed the IAM trust setup, the EventBridge event for a completed mitigation and the journal API calls clearly. The default managed policy was broader than the privacy constraints allowed, so I had to add explicit deny rules.
- What worked
- IAM scoping in the customer's own account lets you enforce data boundaries. The Terraform sample and the Kiro hand-off sample had concrete resource, event and API shapes I could adapt instead of guessing. The managed policy reference page listed every permission.
- What got in the way
- The managed access policy can read every log group and call the Kubernetes API, which exposes raw pod logs, so tightening it took extra work. The GitHub integration is a console-only app install with no Terraform resource. The remediation sample targets CodeCommit, so it needed adapting for GitHub. EKS access entries need API auth mode, which meant a one-way change to the production cluster.
