Summary

It uses the credentials already in ~/.aws — no keys pasted into a config file.

That is the practical difference from most cloud bridges: profiles and SSO come from the setup you have, so switching accounts is picking a profile rather than editing secrets. The flip side is scope — it can modify resources, not just describe them, so pick the profile you point it at deliberately.

What it is

A server that lets an assistant query and modify AWS resources in conversation, running locally against your own AWS configuration.

What you get

Query and modify AWS resources by describing what you want
Multiple AWS profiles, with SSO authentication supported
Multi-region operation
Local execution using your own credentials — nothing is handed to an external service

Requirements

Node.js, and AWS credentials already configured locally in your ~/.aws directory. Clone the repository, install dependencies with pnpm or npm, then point the client at the project directory with the start script. MFA support and SSO credential caching are listed as still in development.