Recent content on InfraHouse
We run OpenVPN so employees can reach internal resources. Authentication goes through Google Workspace. An employee with a Google account opens the VPN portal, downloads a config with a client certificate, and connects.
We shipped GPU autoscaling for our ECS module. Version 8.3.0 added a target-tracking policy that scales the service on GPU utilization, and a CloudWatch dashboard to watch it work. I opened the dashboard on a live fleet, and every GPU panel said the same thing: No data available. The scaling policy that reads the same metric sat in INSUFFICIENT_DATA . The alarm had never seen a single datapoint.
The last post ended with a number and a promise. We had measured three ways to hand a 16 GiB model to a fleet; pointing every node at S3 won, flat at ~207 s whether the fleet was 4 nodes or 32. Then we took the artificial cap off to see how fast a node really pulls, and it stopped at 1.05 Gbit/s — which is 131 MB/s, which is the default throughput of a gp3 root volume. We had spent the whole…
An AI coding agent gives you velocity: ship the feature, reshape the schema, keep moving. A relational database gives you consistency: ACID guarantees — every row valid, every constraint held, no matter how the writes arrive. They are good at different things by nature, and that difference is something a working engineer can use on purpose: move fast with the agent, then lean on the database to…
The last post ended with a loose thread. The fetch step downloads the whole model to every node, every time a node comes up. That is fine for two nodes. It is not fine for 100.
An ML developer came to me with a model to serve. He had already made the decisions that matter most: an open model tuned for his use case, a vLLM container to run it, and a response-time target the product depended on. That combination is the reason you self-host in the first place. A hosted inference API gives you someone else’s general model on someone else’s schedule. Running your…
On January 30 this year, I filed an issue against our self-hosted GitHub Actions runner module infrahouse/terraform-aws-actions-runner . The title: “Actions runner gets terminated and job fails with SetInstanceProtection error.” Severity: annoying. Frequency: every couple of days. Workaround: rerun the job, which almost always succeeded on the second attempt.
The startup I work with builds AI agents for enterprises. I handle the infrastructure. The founders and their engineers build the product.
I run infrastructure for a startup. Over the past two years I’ve built a system that manages the company’s entire GitHub organization — over 100 repositories, their permissions, CI/CD pipelines, AWS environments, and security policies — from a single source of truth.
I run infrastructure for a startup. When I joined, the GitHub organization had a handful of repos created by hand through the web UI. Permissions were assigned by clicking buttons. CI/CD was configured manually in each repository. Secrets were copy-pasted.
OpenClaw is everywhere right now. 247,000 GitHub stars, an AWS Lightsail blueprint, people running autonomous AI agents from their phones via WhatsApp. It’s legitimately impressive - an open-source agent that can manage your email, execute shell commands, browse the web, and remember context across sessions.
We recently came in as consultants to a startup with PostgreSQL performance problems. They didn’t have a DBA on staff - not unusual for a company their size. They had monitoring: some CloudWatch dashboards, a DataDog subscription. But the data was scattered across tools, and none of it told the complete story.
On Friday, December 26th, 2025, I released a bugfix for our private PyPI server. The server had been running for months in a degraded single-instance mode to work around a cache synchronization bug across EFS-backed containers. With caching enabled, the single instance performed well, but adding more instances would trigger the bug. The fix removed caching entirely by switching to --backend…
If you write or review infrastructure code-Terraform, AWS IaC, CI/CD pipelines, automation scripts - you’ve likely felt the pain points in this story. Maybe you’ve tried commercial AI review tools and found them shallow. Maybe your team struggles with inconsistent reviews. Or maybe you’re scaling quickly and need a way to enforce standards without slowing development down.
Discover how InfraHouse transformed a routine Lambda module into production excellence through disciplined AI collaboration. Same timeline, exponentially better outcome-including ISO 27001 compliance, comprehensive testing, and security patterns discovered after years of experience.
A practical engineering story about replacing Keycloak with Cognito to create a self-hosted Terraform registry using Tapir, AWS ECS, and ALB - a simpler, cost-efficient, and fully reproducible setup.
In Part 1 we explored how tools like OSV-Scanner help you detect vulnerabilities in application-level dependencies (think requirements.txt , package-lock.json , etc.).
Part 1 of the Vulnerability Management Series — how to manage dependency vulnerabilities with OSV-Scanner and ih-github while meeting SLAs and keeping developer velocity high.
When HashiCorp releases a new major version of the AWS Terraform provider, engineering teams often brace themselves. Major upgrades bring new features and bug fixes, but they also come with breaking changes. A module that “just worked” under v5 might fail or drift silently under v6.
I had a conversation with a colleague other day, and he asked who has access to a specific password. We use AWS Secrets Manager to store secret data and AWS Identity and Access Management to control access to it. Seemingly simple question, it was difficult to answer. I started off with describing how an IAM role can have particular permissions on a particular secret, etc. Pretty soon, I realized,…
Aleks is short for Oleksandr. What Aleks ships to production The infrahouse GitHub org has ~69 Terraform modules I wrote and maintain — ECS services, ALB, RDS, ACM, Route 53, IAM, Control Tower account vending, and more. They are versioned, tested, and running in production.
Production-ready infrastructure tools built with ISO 27001 compliance, monitoring, and operational excellence in mind.
$10K/Month Flat Rate · 24/7 Expert Team · 50+ Hours of Development Included
Platform and infrastructure engineer with 20+ years of experience designing, scaling, and evolving the systems that underpin engineering velocity.
Effective Date: 7/5/2026 InfraHouse (“we,” “our,” or “us”) values your privacy. This Privacy Policy explains how we collect, use, and protect your information when you visit our website.
The Infrastructure-First Path to SOC 2 & ISO 27001 Compliance Stop audit anxiety. We design, audit, and blueprint AWS environments that are audit-ready by design and built to satisfy the most demanding global security standards.
Terraform Module Catalog 47 production-ready Terraform modules for AWS infrastructure. All modules are tested against real AWS and designed for ISO 27001 compliance.