We too at first thought that letting an LLM manage your AWS account must be a bad idea. What could possibly go wrong?? However we couldn’t resist building it, and when we did, we were surprised how much it can do even in plain vanilla form, which currently is just the ai-sdk frontend with some aws sdk code generation (inspared by aws-mcp). We all but stopped using the AWS console internally and switched to Infrabase - a lot of the time it’s much faster to prompt than to click around in AWS console, especially for things that involve multiple steps, IAM roles, etc.
So we started to think of making a publicly-launchable product out of it. Some of the things that were missing:
- Auth
- Some form of checking / validation of the generated aws-sdk code
- OIDC or cloudformation template instead of keys to connect AWS accounts
- Support more infra tools, not just AWS (datadog, github, sentry, …)
- User actions for tool use / explicit approval of risky operations
- Export to Terraform / OpenTofu
But then we thought, the only thing that is really missing is auth; the rest of the list would still be a blocker for many people, but not for everyone. So we shipped auth and here we are - perhaps someone is crazy enough to try it as-is and sharing your thoughts!
0 comments
—
Show HN: Infrabase – Prompt-Ops for AWS · HackerTrans
So we started to think of making a publicly-launchable product out of it. Some of the things that were missing:
- Auth - Some form of checking / validation of the generated aws-sdk code - OIDC or cloudformation template instead of keys to connect AWS accounts - Support more infra tools, not just AWS (datadog, github, sentry, …) - User actions for tool use / explicit approval of risky operations - Export to Terraform / OpenTofu
But then we thought, the only thing that is really missing is auth; the rest of the list would still be a blocker for many people, but not for everyone. So we shipped auth and here we are - perhaps someone is crazy enough to try it as-is and sharing your thoughts!