git404hub

what is aws-side-cluster fr?

underpass-ai/aws-side-cluster — explained in plain English

Analysis updated 2026-05-18

0PythonAudience · ops devopsComplexity · 5/5Setup · hard

tl;dr

A proof-of-concept toolkit for extending a home Kubernetes GPU cluster into disposable AWS cloud workers, with tooling to audit AI decisions after the worker shuts down.

vibe map

mindmap
  root((aws-side-cluster))
    What it does
      Extends local cluster to AWS
      Disposable GPU workers
      Auditable decisions
    Tech stack
      Kubernetes
      Terraform
      WireGuard
      Helm
    Use cases
      Burst GPU capacity
      Cost control via auto-stop
      Post-hoc auditing
    Audience
      DevOps engineers
      Infra researchers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Burst a local GPU cluster into AWS for extra inference capacity on demand.

VIBE 2

Automatically shut down idle cloud GPU workers to control costs.

VIBE 3

Reconstruct and audit what an AI worker decided after it has already been shut down.

VIBE 4

Run coordinated multi-model workflows split across local and cloud GPUs.

what's the stack?

PythonKubernetesTerraformHelmWireGuardAWSPrometheusGrafana

how it stacks up fr

underpass-ai/aws-side-cluster0xallam/my-recipe0xhassaan/nn-from-scratch
Stars00
LanguagePythonPythonPython
Last pushed2022-11-22
MaintenanceDormant
Setup difficultyhardmoderatemoderate
Complexity5/52/54/5
Audienceops devopsgeneraldeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · hard time til it works · 1day+

Requires a local multi-GPU workstation, an AWS account, and hands-on Kubernetes and Terraform setup.

in plain english

This project is a proof of concept for stretching a home Kubernetes cluster into the cloud. A local workstation with four GPUs runs the main control plane and serves language models. When more capacity is needed, extra worker machines are started on AWS and connected back to the local network through WireGuard, a lightweight VPN tool. Those cloud workers can include plain CPU machines or a GPU machine running its own language models, and they join the same cluster as if they were sitting next to the local hardware. The idea driving the project is that cloud GPU workers should be disposable. They can be shut down after a few minutes of being idle to save money, then woken back up automatically when a request needs them. The author's companion article, linked in the README, frames the core tension the repo explores: even if a GPU worker turns itself off quickly, any decision it made while it was running still needs to be traceable afterward. So the repo also builds tooling to record and later reconstruct exactly what happened during a run, even after the machine that did the work is gone. Inside the repo you get the reproducible pieces of this setup: Terraform scripts to create the AWS network and machines, Helm charts to deploy everything onto Kubernetes, shell and Python scripts to manage the WireGuard connection and start or stop workers, a Grafana dashboard for monitoring, and a small terminal interface for replaying past decisions. There is also a component called a choreographer that runs multi model ceremonies, meaning coordinated tasks that involve several language models split between the local machines and the AWS worker, along with real logs of past runs. The documentation describes validated milestones dated between late June and early July 2026, including networking, GPU worker setup on an AWS L4 GPU instance, running two models on that single GPU at once, and automatic shutdown when idle. This is very much an experimental, hands on infrastructure project rather than a polished product, and it assumes familiarity with Kubernetes, Terraform, and cloud networking concepts.

prompts (copy fr)

prompt 1
Explain how the WireGuard networking in this repo connects a local Kubernetes control plane to AWS EC2 workers.
prompt 2
Walk me through the Terraform files in this repo and what AWS resources they create.
prompt 3
How does the auto-stop-on-idle mechanism for the AWS GPU worker work in this project?
prompt 4
Help me adapt the Helm charts in charts/local-llm to deploy a different model.

Frequently asked questions

what is aws-side-cluster fr?

A proof-of-concept toolkit for extending a home Kubernetes GPU cluster into disposable AWS cloud workers, with tooling to audit AI decisions after the worker shuts down.

What language is aws-side-cluster written in?

Mainly Python. The stack also includes Python, Kubernetes, Terraform.

How hard is aws-side-cluster to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is aws-side-cluster for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.