ARGLabs
It's a fictitious company that aims to run everything in native cloud services doing everything as code to get the best results in culture, cost, support, technology and monitoring. We achieve that with no AWS Console access, no team lock-in by empowering dev teams while ensuring best practices and guardrails and...
No Kubernetes.
Latest posts
Running the ARGLabs apps on EKS instead of ECS: effort, cost, monitoring and verdict
What would change for arglabs-workload, the status page and Dependency-Track if they left ECS Fargate for an EKS cluster: the cluster's repository, the cost on EC2, Fargate and Auto Mode, the sidecars, and the monitoring arglabs-tfmod-ecs-app delivers today. Short answer: do not migrate.
How should repository variables and secrets get onto containers ?
A Bitbucket variable named ENV_NAME reaches the container as the plain variable NAME; one named SECRET_NAME is stored in Secrets Manager and injected as NAME. The whole chain on arglabs-workload, with real output from dev, and why it means adding or removing a variable never touches Terraform, …
Arglabs, by Claude
Everything the 31 ARGLabs repositories build, why the platform is ECS in each team’s own account, what it costs, and how it measures against AWS best practices. Written by Claude Code from the repositories on 2026-09-27.
The BigBang process
Every team at ARGLabs needs its own AWS accounts, and they all need to look the same: the same access controls, the same network baseline, the same security guardrails. Doing that by hand, account after account, environment after environment, is how drift and mistakes creep in. BigBang is the answer …
TFMOD: BigBang IAM
Creating a BigBang member account is only half the job. Once the account exists, something has to deploy applications into it without handing out account-wide admin rights. This Terraform module owns the IAM side of every BigBang-generated account: it is meant to be the single place where all …
Last updated on