Fractional Infrastructure Architecture
Single-account blast radius. IAM complexity that’s become unmanageable. Terraform partially adopted but nobody owns the state.
I build the architecture that fixes this — 10–20 hrs/week, 3–6 months.
AI-assisted workflows fit when they reduce platform friction: Terraform review, runbooks, repo context, and operational handoff. Not demos.
Currently accepting fractional engagements — reach out to discuss timing.
Recent outcomes
When This Is a Fit
If two or more of these are true, let’s talk →
Mid-Market Media Company
Built 6-account AWS foundation with Transit Gateway, production EKS, and Terraform IaC. Reduced provisioning from 3 weeks to 2 days.
Aerospace Defense Contractor
Designed and built a multi-account AWS GovCloud (US) foundation for a NASA mission support program. STIG-hardened, NIST 800-53 compliant, zero public internet exposure.
ECS Fargate egress through an inspection VPC cost ~$1,300/day. The fix: public subnets and a local IGW. The Terraform changes, apply sequence, and the gotcha.
Changed-files detection in Terraform CI silently skips stacks that consume modified modules. Here's the pattern that actually works, plus three supporting fixes.
ECS vs EKS isn't a features comparison — it's an operational capacity question. Decision framework including ECS Anywhere, with real production examples.
10–20 hours per week. Not a full-time hire, not a one-off audit. Senior infrastructure architecture expertise for 3–6 months while your team builds the foundation and learns to operate it.