Madhosh Yagnik | DevOps Engineer

Portfolio
DevOps Engineer

Madhosh Yagnik

Production infrastructure across AWS and Azure - IaC migrations, CI/CD pipelines, and automation that replaces slow manual work. I care about systems that are reliable, cost-efficient, and easy for the next person to understand.

8+projects
~$1000saved / mo
1.6yr+production
madhosh ~ whoami
$ cat profile.json
cloudAWS · Azure · GCP
iacTerraform . Terraform Cloud . Ansible
containersDocker · Podman · Docker Compose
cicdGitLab CI · Azure DevOps · GH Actions
scriptingBash · Python
systemsLinux · NGINX · systemd
self-hostedGitLab on personal hardware
statusopen to new work ✓
$
01Work
tap to expand
01AWS Disaster Recovery & Infrastructure AutomationAWS
Oct 2024 - Mar 2025 · Singapore-based bank

Designed and delivered multiple DR and infrastructure automation solutions for a production banking environment. Every decision was weighed against cost.

  • Migrated Bastion servers from CentOS 7 (EOL) to Ubuntu 24.04 LTS with no service disruption. Rewrote the setup guide for Debian and YUM-based distros.
  • Built a cost-effective DR system: EventBridge + Lambda for automated RDS snapshots, cross-region copy, and health-monitored auto-recovery if primary failed.
  • Developed a parallel EC2 DR solution with AMI rotation, cross-region copy, auto-launch on health check failure, and SNS alerting.
  • Evaluated AWS Read Replicas and DMS; excluded both on cost grounds after full POC - documented the decision with analysis.
  • Resolved urgent Bitbucket pipeline failures and stabilised CI/CD long-term.
  • Recovered access to a Windows EC2 instance after the private key was lost.
↑ Multiple automated DR paths · Cost-justified throughout
02DevOps Backlog - Docker, CMake, Makefile, Git, LinuxLinux
Dec 2024 - Jan 2025 · Contract

Cleared a backlog of 72 DevOps tasks across Docker, Linux, Git, Makefile, and CMake - 64 accepted on first review.

  • Picked up CMake and Makefile tasks while learning both tools in parallel - no blocked work or delays.
  • Daily stand-up transparency with clear progress tracking throughout.
↑ 64 / 72 tasks accepted · Full delivery satisfaction
03Full Azure Migration & CI/CD PipelineAzure
Feb 2025 - Mar 2025 · Primary DevOps resource

Took a project running entirely on local setups and brought it to a production-ready Azure deployment in one month.

  • Migrated full stack to Azure Cloud, resolving routing and network configuration issues along the way.
  • Iterated CI/CD across three approaches - GH Actions, Azure DevOps via SSH, and finally an Azure agent-based pipeline with client-approved security controls.
  • Optimised the frontend Dockerfile to serve static files - load time dropped from seconds to milliseconds.
  • Dockerized all services; created Docker Compose stacks for consistent local and cloud environments.
  • Added systemd services and cron jobs for self-starting apps at VM boot.
↑ Zero-to-cloud in one month · Load time: seconds → milliseconds
04Terraform IaC Migration & Cost OptimisationAWS
Mar 2025 - Aug 2025 · Primary DevOps

Inherited a production AWS environment with no IaC, no state management, and known security gaps. Left it fully Terraform-managed, secured, and cheaper to run.

  • Migrated all AWS resources to Terraform with Terraform Cloud for remote state and environment isolation. Negligible downtime during migration.
  • Partnered with the security team to audit past incidents and implement preventive IAM controls.
  • Reduced monthly AWS spend by ~$95-100 via right-sizing and cleanup.
  • Moved the on-prem chatbot server from the office to the server room - eliminated recurring accidental disconnections.
  • Delivered a complete handover; incoming engineer appreciated the thoroughness.
↑ ~$100/month saved · Zero config drift · Clean security posture
05Lightweight RDS Backup AutomationAWS
Apr 2025 · Short contract

Client was paying for daily automated RDS backups on a staging environment that did not need them. Replaced the default behaviour with a purpose-built, native solution.

  • Disabled built-in backups; implemented monthly snapshot Lambda and quarterly cleanup Lambda retaining the latest snapshot.
  • Scheduled via EventBridge with SNS alerts. Wrote complete manual recovery documentation.
↑ Meaningful cost reduction · Simpler, auditable backup workflow
06Production Server Management & Deployment SecurityLinux
Apr 2025 - Ongoing · Two products, Israel-hosted

Ongoing management of production and staging for two separate products. Minimal setup, stable operations.

  • Manage deployments and NGINX configurations; coordinate with hosting provider for system-level updates.
  • Resolved CORS and React routing issues from misconfigured NGINX paths.
  • Replaced Git token-based deployment with SSH deploy keys - documented in a one-page team guide, adopted on a separate Azure project for consistency.
↑ Stable ops · Improved deployment security · Standardised across projects
07SSL, DNS Recovery & Chatbot StabilisationAWS + DNS
Apr 2025 - Ongoing

Picked up a production chatbot platform mid-incident - expired SSL, broken auto-renewal, and a domain blocked by a major social platform.

  • Diagnosed and fixed the failed auto-renewal mechanism; renewed certificates.
  • Resolved a domain blockage that had disrupted chatbot operations.
  • Set up a temporary subdomain for business continuity; decommissioned cleanly after the main domain stabilised.
  • Managed full domain transition to a new subdomain, updating backend and dependent service configurations.
  • Upcoming: scoping migration of chatbot logic from AWS to client's own GCP VM.
↑ Production restored with minimal downtime · Client appreciation received
08OpenShift CI/CD & Lab AutomationConfidential
Apr 2025 - Ongoing · Confidential client

Working across two internal projects - a completed OpenShift plugin platform (Backstage) and an ongoing lab provisioning system used by around 1000 engineers.

  • Led end-to-end DevOps delivery for the OpenShift plugin platform (Backstage), taking it from local development to production. This effort led to the decommissioning of the legacy resource hub and development of the cluster platform to replace it.
  • Implemented GitLab CI pipelines for linting, SonarQube scanning, and container image build/release automation. Supported plugin releases from v0.0.2 to v0.0.24 - stable with minimal maintenance since.
  • Contributed to a monorepo-based solution enabling consistent developer deployments across internal teams.
  • Actively migrating RHEL7 Lab Controllers to RHEL9 as part of a vulnerability remediation effort.
  • Automated VPN connection setup - removed manual OTP and credential steps, now single-click.
  • Automated recovery for 'Broken' lab machines—originally a parallel Bash/xargs script that reduced lookup time from ~1 hour to minutes. Refactored to Python for team consistency and now runs via GitLab pipeline schedules for ongoing automated maintenance. This operation had been manual for over a decade.
↑ Legacy hub replaced by cluster platform · Stable infra for ~1000 engineers · Recovery: ~1 hr → minutes
02Tools & Stack
Cloud
AWSAzureGCP
IaC
TerraformTerraform CloudAnsibleVagrant
Containers
DockerPodmanDocker ComposeKubernetes
CI/CD
GitLab CIAzure DevOpsGitHub ActionsSonarQube
AWS Services
LambdaEventBridgeRDSEC2IAMSNS
Systems
LinuxBashPythonNGINXsystemd
Build
CMakeMakefileGit
Platforms
OpenShiftBackstageHardware Integration TestingPM2
03What I care about
Automation over manual
If something is done twice, it gets scripted. VPN setup, snapshot workflows, broken machine recovery - all automated.
$
Cost-aware decisions
Every solution includes a cost analysis. I have excluded approaches specifically because they could not justify their bill.
Documentation that holds up
I write docs people actually use. When the old guide does not cut it, I rewrite it from scratch. KTs with no gaps.
Self-healing infrastructure
DR that triggers on its own. Pipelines that recover. Monitoring that acts, not just alerts.
🔒
Security by default
IAM audits, SSH keys replacing tokens, Terraform removing config drift. Not a separate phase - the default.
Clean handovers
Systems should be understandable by whoever comes next. Architecture docs, runbooks, annotated Terraform - all part of the job.
04Personal Infrastructure
Checking Status...
Self-hosted GitLab
Running on my personal laptop (which I do turn off at times), migrating to a Raspberry Pi 5 · gitlab.madhoshyagnik.space
© Madhosh Yagnik.RSS