Back to Home
sakthisundar-16 icon

ai-infrastructure-agent

by sakthisundar-16

Overview

Manage AWS infrastructure using natural language commands with AI.

Installation

Run Command
docker run -d --name ai-infrastructure-agent -p 8080:8080 -v $(pwd)/config.yaml:/app/config.yaml:ro -v $(pwd)/states:/app/states -e OPENAI_API_KEY="your-openai-api-key-here" -e AWS_ACCESS_KEY_ID="your-aws-access-key" -e AWS_SECRET_ACCESS_KEY="your-aws-secret-key" -e AWS_DEFAULT_REGION="us-west-2" ghcr.io/versuscontrol/ai-infrastructure-agent

Environment Variables

  • OPENAI_API_KEY
  • GEMINI_API_KEY
  • ANTHROPIC_API_KEY
  • AWS_ACCESS_KEY_ID
  • AWS_SECRET_ACCESS_KEY
  • AWS_DEFAULT_REGION

Security Notes

CRITICAL: The web server's WebSocket handler (`pkg/api/server.go`) explicitly sets `upgrader.CheckOrigin: func(r *http.Request) bool { return true }` and the `corsMiddleware` sets `Access-Control-Allow-Origin: *`. This means the web UI is vulnerable to Cross-Site Request Forgery (CSRF) and Cross-Origin Attacks if exposed publicly in production without modification. IAM permissions provided in the example (`ec2:*`, `vpc:*`, etc.) are broad, granting extensive control over AWS resources. This high level of access, combined with potential web UI vulnerabilities and the LLM's susceptibility to prompt injection, presents significant risks if not managed with extreme care. While the documentation correctly advises using environment variables for API keys and `dry_run` is enabled by default, the default web server configuration makes it unsafe for general deployment without immediate security hardening.

Similar Servers

Stats

Interest Score30
Security Score4
Cost ClassMedium
Avg Tokens4000
Stars1
Forks1
Last Update2026-01-19

Tags

AI AgentAWSInfrastructure-as-CodeDevOpsCloud Management