Bridging the Infrastructure Scaffolding Gap with ois
Moving from a manual copy-paste workflow to an orchestrated foundation in 60 seconds. A deep dive into building ois with Go, Cobra, Survey and Go embed, why it isolates Terraform state per service to limit the blast radius, and the path from ois init to a deployed AWS stack.
Read more
ois: Infrastructure Scaffolding CLI
Every new AWS Terraform project starts with the same chore: creating directories, wiring up remote state backends and copy-pasting modules from an old repository. ois is a Go command-line tool that turns that into a single command.
Running ois init sets up a multi-environment project, with pre-production and production separated from the start. ois add then scaffolds Lambda, DynamoDB, SQS and API Gateway services through interactive prompts, using Terraform modules built on best practices.
Each service gets its own backend and state file, so a change to one Lambda function can never touch a database. When you connect two services, ois generates the IAM policies, SSM parameter lookups and event triggers they need to work together.
All templates are compiled into a single binary with Go embed, so it runs anywhere with no external files. It installs through Homebrew, and ois estimate prices a Terraform plan with OpenInfraQuote.



