## Thinking Path
> - Paperclip is the open source app people use to manage AI agents for
work
> - The planned AWS connector gives each connection its own AWS identity
with no stored keys, using the workload identity issuer from #22083
> - The plan had open questions that only a real AWS account could
answer
> - This pull request records the answers from a spike against the
Paperclip dev AWS account
> - The benefit is that the connector build starts from proven facts,
and two design details are corrected
## Linked Issues or Issue Description
Refs #22083.
**Subsystem affected**
Connections (planned AWS connector), docs only.
**Problem or motivation**
The AWS plan assumed an `aws___call_aws` tool and a read-only session
policy with only `ReadOnlyAccess`. Neither had been tested.
**Proposed solution**
Record the spike results and correct the plan. The hosted server in the
test account offers `aws___run_script` but no `aws___call_aws`. A
read-only session also needs `AWSMCPSignInOAuthAccessPolicy`, or the
token exchange fails.
**Alternatives considered**
Leave the plan unchanged and find the differences during the build.
Rejected: the tool choice changes the governance design.
## What Changed
- `doc/plans/2026-11-17-aws-connector-and-minted-credentials.md`: a new
"Spike findings" section with results and timings, and corrections in
the minting, agent-call and governance sections. Phase 0 is marked done.
## Verification
- Spike against the dev AWS account. The issuer code from #22083 ran
locally behind a temporary public HTTPS tunnel. The spike verified these
items:
- AWS accepted a Paperclip-signed token.
- A token for another connection was denied.
- The bearer exchange worked.
- `tools/list` worked.
- A read and a write through `run_script` worked.
- A read-only session could read, and AWS refused its write.
- Both access-key paths worked.
- After the spike, a listing of roles, OIDC providers, users and buckets
with the spike prefix returned nothing.
- Docs only. No code changed.
## Risks
- Low risk. Docs only.
- The tool list was observed in one account on one day. AWS can change
the hosted server.
## Model Used
- Claude Opus 5.5 (`claude-opus-5-5`) in Claude Code, with tool use
(shell, AWS SDK for JavaScript, AWS CLI, a Cloudflare quick tunnel).
## Checklist
- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [ ] All Paperclip CI gates are green
- [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Paperclip <noreply@paperclip.ing>