Visit https://arglabs.org !!!

Latest posts:

• 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, pipeline or code.
• 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 to that problem. It is … Continue reading The BigBang process
• 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 identity and access for those accounts is … Continue reading TFMOD: BigBang IAM
• 002 – Shared network account
  The Shared Network account is owned by the Cloud Team and exists to do one thing well: provide shared connectivity that the rest of the ARGLabs organization can consume. Instead of every account building and maintaining its own network, this account builds the baseline once and shares it through AWS Resource Access Manager (RAM).