AHMAD HASSAN
GitHub
ALL PROJECTS
01 / AWS / AGENTIC OPERATIONSSOURCE AVAILABLE

OpsPilot AI.

Investigate the cloud. Keep the evidence.

A read-only AWS resource and cost investigation workspace. A Next.js galaxy view, FastAPI routes, an OpenAI Agents SDK investigator and token-gated MCP tools all draw from the same service layer.

01 / THE PROBLEM

Cloud costs need context.

An AWS cost question spans inventory, idle signals, prices and dependencies. OpsPilot brings those observations into one investigation while making the agent's tool calls and findings inspectable.

02 / ARCHITECTURE

How the system moves.

  1. 01

    Inspect

    The Next.js galaxy and chat surface selected account resources and the investigation trace.

  2. 02

    Orchestrate

    FastAPI passes a chat turn to an OpenAI Agents SDK runner with bounded provider fallback.

  3. 03

    Use shared tools

    Thin agent and MCP tools call the same scan, waste, cost and impact services as API routes.

  4. 04

    Read AWS

    Services call boto3 through a read-only client; concurrent collectors isolate failures and reuse cached scans.

  5. 05

    Retain evidence

    Tool results return to the trace, while investigations can be embedded and stored in DynamoDB for recall.

03 / ENGINEERING DECISIONS

Why these boundaries matter.

01

One source of cloud logic

API routes, agent tools and token-gated MCP tools share services rather than maintaining separate AWS calculations.

02

Analysis without mutation

The deletion-impact path inspects EC2, RDS and EBS relationships. It does not terminate resources.

03

Deterministic checks

A moto-backed golden account lets the evaluation harness compare answers and traces with service-derived facts.

04 / SOURCE EVIDENCE

What the repository shows.

  • Collectors for 15 AWS resource types and seven waste checks
  • Moto fixtures and a service-layer oracle for deterministic evaluation
  • Read-only deletion-impact analysis that does not delete resources

Selected files from the public repository, pinned to the revision reviewed for this case study.

EXPLORE THE REPOSITORY

HONEST BOUNDARY

The public source supports these components and evaluation methods. This review did not run a live AWS account, verify savings or confirm production adoption. The documented single-admin and static IAM-key model is not presented as a multi-tenant production security design.