Skip to content

Archive

32 posts, newest first. Nothing is removed; corrections are dated in place.

2026

  1. Cost governance that engineers accept

    Cloud cost is an architectural property, not a monthly report. Tags that hold, priced switches, endpoint arithmetic and a cost comment on every pull request.

    Cost 12 min
  2. Data platform governance with Lake Formation

    A three-zone lake, LF-Tags and a deny-direct-S3 policy turn data governance into something enforced at query time instead of described in a spreadsheet.

    Platform 9 min
  3. An EKS platform without a platform team

    A worked EKS golden path: a managed node group with Karpenter, ArgoCD, External Secrets, promotion by approval, and what Kubernetes costs you to operate.

    Platform 11 min
  4. The golden path for new services

    A golden path turns a platform team from a ticket queue into a paved road: what it must include, the new-repository flow, and the 18 pitfalls to design out.

    Platform 12 min
  5. Terraform state at enterprise scale

    Terraform state is a production system: one key per unit, a real lock, versioning, and a restore drill. Here is what to do when state and reality diverge.

    Delivery 12 min
  6. OpenTofu and Terragrunt for enterprise IaC

    OpenTofu and Terragrunt give enterprise IaC a license you control and a dependency graph that plans an entire new environment before any of it exists.

    Delivery 11 min
  7. Evidence automation beats screenshot season

    Audit evidence has a shelf life, and most findings services keep only 90 days. Here is how to make infrastructure produce evidence that survives the period.

    Compliance 9 min
  8. Infrastructure due diligence: what buyers look for

    Investors, acquirers and enterprise procurement inspect the same six things. Here is what each finding signals, and a self-audit to run before they arrive.

    Compliance 10 min
  9. Answering a 300-question security questionnaire

    A security questionnaire is a revenue blocker answered by your most expensive engineers. Here is how to answer with evidence and never write the answer twice.

    Compliance 9 min
  10. CMMC 2.0 for defense suppliers

    CMMC Level 1 and Level 2 decide whether a supplier can hold the contract. Here is what infrastructure covers, what it cannot, and where it gets hard.

    Compliance 9 min
  11. PCI DSS 4.0: scope reduction by account

    Account isolation is the cheapest PCI scope reduction available, and the most over-claimed. Here is what it removes, what stays in scope, and what proves it.

    Compliance 9 min
  12. HIPAA on AWS: what the foundation must carry

    The HIPAA Security Rule splits across your policies, your cloud provider and your infrastructure. Here is the part infrastructure owns, and how it is proven.

    Compliance 9 min
  13. Zero trust access for engineers

    How people should reach production: federated sessions instead of users, no long-lived keys anywhere, and access that ends the day someone leaves.

    Security 9 min
  14. Built for 3 AM: the operability properties

    Operability is what a system needs before it has an incident. Here are the properties that decide whether the second-best engineer can run it alone.

    Operations 7 min
  15. Secrets management without a vault cluster

    Encrypted secrets in Git, one key per stage, and a sync to parameter storage: why repository write access still does not let anyone read production.

    Security 10 min
  16. Tamper-resistant audit logging, honestly

    A separate account, an organization-wide trail with file validation, and a policy that forbids stopping it — plus what tamper-resistant does not mean.

    Compliance 10 min
  17. Nine security services, one account

    What GuardDuty, Security Hub, Config, CloudTrail and their siblings each actually catch, what they cost, and the order to switch them on.

    Security 9 min
  18. Production readiness is a velocity multiplier

    Production engineering is usually sold as risk reduction. The stronger argument is speed: teams without a foundation spend their capacity on rework.

    Cost 6 min
  19. IP address planning that survives growth

    Overlapping CIDRs are the cheapest mistake to make and one of the most expensive to fix. Here is how to plan an address space once and enforce it in CI.

    Architecture 9 min
  20. Hub and spoke networking with Transit Gateway

    Spoke VPCs with no NAT, one centralized egress path, and blackhole routes between production and non-production: what a hub and spoke topology buys.

    Architecture 10 min
  21. Permission sets that survive an audit

    Least privilege fails when people cannot do their jobs. Here is an identity model with read-only production and an access review that produces evidence.

    Security 9 min
  22. Service control policies that hold

    A guardrail works only if engineers cannot route around it. Here is how to design, exempt and test a service control policy before it blocks production.

    Security 9 min
  23. Drift is a fact, not a failure

    Infrastructure drift is not a sign of a broken team. It is information about what your environment needs. Detect it, triage it, and never auto-revert it.

    Platform 7 min
  24. Control Tower vs a code-owned landing zone

    AWS Control Tower gives you the account and guardrail layer at no license fee. Here is where a code-owned foundation wins, and where it honestly does not.

    Architecture 9 min
  25. Multi-account strategy for enterprises

    The account boundary is the first security control you get. Here is how to decide what deserves its own account, and how the structure survives growth.

    Architecture 9 min
  26. If deployment requires a hero, it isn't automated

    A deploy that needs the right person, the right laptop or the right afternoon is a manual process with a script attached. Here is the difference.

    Delivery 6 min
  27. What production-ready actually means

    Production-ready is not a feeling. It is eight properties, each with a question you can answer about your own estate this week, with evidence.

    Architecture 8 min
  28. The true cost of building your own landing zone

    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.

    Architecture 10 min
  29. SOC 2: what your infrastructure has to produce

    An audit is an evidence problem. Here are the evidence sources cloud infrastructure should generate on its own, and why readiness is not certification.

    Compliance 7 min
  30. Zero long-lived cloud credentials: OIDC in CI/CD

    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.

    Security 6 min
  31. The multi-account landing zone, explained

    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.

    Architecture 7 min
  32. Backups you haven't restored are assumptions

    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.

    Reliability 8 min

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.

  • 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.

A 30 minutes call with an engineer who scopes engagements, not a salesperson. Tell us what you run and what is coming: a funding round, an audit, a first enterprise customer, a migration. You leave with a next step, a fixed fee, or an honest no.

The invite goes to this address. Prefer to write? Send a message.