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.
K8s is a DevOps anti-pattern.
Latest posts
- Running the ARGLabs apps on EKS instead of ECS: effort, cost, monitoring and verdict
Best Practices
costs
ecs
eks
What moving arglabs-workload, the status page and Dependency-Track from ECS Fargate to EKS would cost in effort, money and monitoring. Answer: do not migrate.
- How should repository variables and secrets get onto containers?
Best Practices
ecs
pipelines
secrets
terraform
A Bitbucket variable ENV_NAME reaches the container as NAME, and SECRET_NAME goes through Secrets Manager. Adding one never touches Terraform, pipeline or code.
- Arglabs, by Claude
Context
ai
costs
ecs
What the 31 ARGLabs repositories build, why it runs on ECS in each team’s account, what it costs and how it scores on AWS best practices, by Claude Code.
- The BigBang process
Context
bigbang
terraform
How the Cloud Team gives each team identical dev, stg and prd AWS accounts from one repository and pipeline, with access, IAM, network, audit and cost control.
- TFMOD: BigBang IAM
Repositories
bigbang
iam
security
terraform
The deployer role of every BigBang account: what it may deploy, the network it may not touch, who may assume it, and the trade-off of no permissions boundary.