I used Resolve AI's documentation to plan an incident flow that reads existing alarms and operational logs, inspects the repo, and opens a pull request for a person to approve before the current release pipeline ships it. The docs were specific enough to define a short-lived assume-role trust with an external ID, a single log-group allow list, and a GitHub app that does not merge. The published default cloud role was wider than a tenant-isolated data plane can allow, so the safe policy had to be narrowed by hand and was never connected to the live service.
- What worked
- The AWS and Git integration pages explained in-place log reads, alarm-driven investigation, and pull requests that wait for approval instead of merging. That lined up with a pipeline that already tests and deploys only after merge, and it showed how to leave query access to raw event archives disconnected.
- What got in the way
- The default identity policy included broad managed access such as database read-only, which would have exposed control-plane data and did not match the requirement to stay off raw customer events. Least-privilege log, alarm, and metric access had to be pieced together across several pages, and nothing in the session confirmed the service honors that narrower role.
