Archive
5 posts, newest first. Nothing is removed; corrections are dated in place.
2026
-
The true cost of building your own landing zoneArchitecture 10 min
A cloud foundation built in-house costs far more than the estimate says. Here is the work nobody scopes, and when building it yourself is still right.
-
SOC 2: what your infrastructure has to produceCompliance 6 min
An audit is an evidence problem. Here are the evidence sources cloud infrastructure should generate on its own, and why readiness is not certification.
-
Zero long-lived cloud credentials: OIDC in CI/CDSecurity 6 min
Static cloud keys in CI are a liability you chose to keep. OIDC federation replaces them with short-lived tokens your pipeline requests per job.
-
The multi-account landing zone, explainedArchitecture 6 min
Account boundaries are the first security control you get and the hardest to add later. Here is what each account in a landing zone is for, and why.
-
Backups you haven't restored are assumptionsReliability 7 min
A backup nobody has restored is a hypothesis, not a control. Here is how to run a restore drill and set an RTO and an RPO you can defend.
By subject area
By tag
Scheduled
Written, reviewed and merged. Each goes live on the first build after its date — the site rebuilds on a schedule, so no one has to press anything.
- What production-ready actually means
- If deployment requires a hero, it isn't automated
- Multi-account strategy for enterprises
- Control Tower vs a code-owned landing zone
- Drift is a fact, not a failure
- Service control policies that hold
- Permission sets that survive an audit
- Hub and spoke networking with Transit Gateway
- IP address planning that survives growth
- Production readiness is a velocity multiplier
- Nine security services, one account
- Tamper-resistant audit logging, honestly
- Secrets management without a vault cluster
- Built for 3 AM: the operability properties
- Zero trust access for engineers
- HIPAA on AWS: what the foundation must carry
- PCI DSS 4.0: scope reduction by account
- CMMC 2.0 for defense suppliers
- Answering a 300-question security questionnaire
- Infrastructure due diligence: what buyers look for
- Evidence automation beats screenshot season
- OpenTofu and Terragrunt for enterprise IaC
- Terraform state at enterprise scale
- The golden path for new services
- An EKS platform without a platform team
- Data platform governance with Lake Formation
- Cost governance that engineers accept
- Disaster recovery you can prove
- Day 2 operations: who owns production
- From ClickOps to infrastructure as code
- Scaling to a new region without a redesign
- What handover should look like
- Choosing a cloud foundation partner
- The GuardDuty findings that deserve a page
- A KMS key strategy for multi-account AWS
- AWS WAF rules that do not break your app
- Securing the CI/CD supply chain
- VPC flow logs: what to do with them
- Incident response for cloud infrastructure
- FedRAMP and NIST 800-53: what actually maps
- Data residency is an architecture problem
- Twelve weeks to an audit, week by week
- The healthtech path to enterprise readiness
- Fintech infrastructure under two frameworks
- Surviving a vendor security review
- Do you actually need Kubernetes?
- ECS versus EKS for enterprise workloads
- ArgoCD patterns that scale
- Karpenter versus Cluster Autoscaler
- Pod security in practice
- Multi-tenancy in a shared cluster
- A data lake an auditor accepts
- Glue, EMR or Lambda for ETL
- Data classification that holds
- AI workloads on a governed foundation
- GPU capacity without a blank check
- The analytics account pattern
- SLOs for infrastructure teams
- Multi-AZ is not a disaster recovery plan
- Chaos testing your landing zone
- Observability without a six-figure bill
- The four hundred alerts problem
- Capacity planning for accounts and regions
- Pull request workflows for infrastructure
- Testing infrastructure code without theater
- Module design that survives upgrades
- Environment parity that is worth paying for
- CI secrets without long-lived keys
- Provider and module upgrades without fear
- The CTO case for buying your foundation
- Platform team sizing and structure
- Your first 90 days as head of platform
- Build versus buy after a funding round
- The hidden cost of cheap contractors
- Infrastructure decisions that affect valuation
- When to hire your first platform engineer
- Migrating off a platform as a service
- From one AWS account to many
- Onboarding engineers to a new platform
- Runbooks people actually use
- Change management without a change board
- Access reviews that are not theater
- When your infrastructure lead quits
Find out what production would take.
Tell us what you are running and what is coming: a funding round, an audit, a first enterprise customer, a migration. We will tell you what we would build, what it costs, and whether we are the right fit.