AWS DevOps / Cloud Engineer
I keep production infrastructure running on AWS — operating and automating what the business runs on. And when it breaks at 2 AM, I'm the one who finds out why, and fixes it.
incident log
Production doesn't fail politely. Here's the incident log — real events I diagnosed and drove to resolution, the evidence-first way. Hover a marker to open the report.
A severe peak-hour database overload traced to a scheduled-job collision. I followed the evidence through the web tier and drove the fix — read replica, load-aware autoscaling, and connection limits.
Recurring instance replacements turned out to be I/O-bound media traffic invisible to CPU-based autoscaling. I disproved the team's first hypothesis with metrics, then fixed the scaling signal itself.
Auth calls were blocked before reaching the app. I isolated it to a security-group and routing issue and remediated with WAF allow-lists and routing changes — tradeoffs written down.
Contributed to a production migration with minimal downtime — secure multi-tier VPC design and reusable Terraform modules for repeatable, reviewable deployments.
the day-to-day
AWS-certified DevOps engineer. Most of my day is operational — triaging alerts, resolving infrastructure tickets, investigating failures, reading logs and AWS Health events, keeping backups green, and writing evidence-based RCAs when something goes wrong.
Alongside that I build and maintain the infrastructure itself with Terraform, CI/CD pipelines, and containers on Amazon ECS. Because the team is small, I work the whole stack — network, compute, data, security, and cost — rather than one narrow slice.
currently running
the stack
get in touch
Open to conversations about AWS, DevOps, and cloud roles. Fastest way to reach me: