Devops on ferkakta.dev

I answered 114 AWS Well-Architected Review questions from my terminal

Fri, 03 Apr 2026 23:00:00 -0500

I was fourteen questions into the AWS Well-Architected Review when my wrists told me to stop. Each question is a page: read the description, check the boxes, type notes into a 2084-character text field, click Next. The Container Build Lens alone has 28 questions. I had two more lenses queued — the main Well-Architected Framework (57 questions) and the Generative AI Lens (29). That’s 114 questions total, and the console wants me to click through every one.

Recovering Claude Code sessions from history.jsonl after index corruption

Tue, 10 Mar 2026 09:00:00 -0600

I still have every email I’ve sent and received since 1998. I don’t lose data. So when Claude Code stopped resuming sessions for a project I’d used daily for months, I didn’t think “oh well.” I thought “where did it go.”

The project directory still existed in ~/.claude/projects/. There was even a sessions-index.json in it. But the actual per-session JSONL files — the ones that contain the conversation data — were gone. Every one of them. The index was a catalog pointing at empty shelves.

From eight manual steps to one command

Tue, 03 Mar 2026 09:00:00 -0600

I provisioned two tenants by hand before I decided that nobody should ever provision a tenant by hand.

The provisioning flow for our multi-tenant SaaS platform was 8 steps across 4 tools — a Python CLI, a shell script with 5 flags per invocation, a GitHub Actions workflow, and two Kubernetes job manifests requiring injected DB connection strings. Each step had different inputs, different env files, and subtly different flag names for the same concept. The two populate runs used --appname apiserver and --appname tenant_auth_service — note the underscore in one and not the other. That naming inconsistency is a guaranteed typo on a Friday afternoon. Each flag is a chance to silently write 24 SSM parameters to the wrong path.