Available for consulting & fractional DevOps

DevOps Architect who digs until the root cause gives up.

I'm Mayank Gandhe — a Kubernetes consultant and AWS engineer with 7+ years designing cloud platforms for fintech, banking and SaaS. I've been the founding DevOps engineer at startups, led migrations across AWS, GCP and Azure, and I build with AI agents every day.

  • AWS Certified Solutions Architect – Professional badgeAWS SA Professional
  • Certified Kubernetes Administrator badgeCKA
  • HashiCorp Certified Terraform Associate badgeTerraform Associate
0+

years in cloud & DevOps

0

clouds migrated across (AWS · GCP · Azure)

0%

AWS cost cut, no upfront spend

0

merged PRs in upstream open source (AWS-IA, Fluentd, j8a)

// how I can help

DevOps consulting for teams that need it done right the first time

Whether you need a founding DevOps engineer to build from zero, a fractional DevOps lead to own the platform part-time, or a Kubernetes consultant to fix the thing nobody else could — here's what I do.

⎈

Kubernetes Consulting

EKS, GKE and AKS clusters built with Terraform. Cloud-agnostic Helm charts, Karpenter autoscaling, Gateway API, IRSA, secrets-store CSI and deep networking troubleshooting.

☁

AWS & Cloud Architecture

Multi-AZ, private-subnet VPCs, multi-account Landing Zones with Control Tower and SCPs, multi-cloud networking, and zero-downtime migrations from on-prem, Azure or GCP.

🚀

Founding & Fractional DevOps

I've built startup platforms from an empty AWS account to production. You get infrastructure as code, CI/CD, runbooks and on-call practices your team can own after I step back.

🛡

DevSecOps & Compliance

SOC 2, PCI-DSS, CCPA and GDPR controls: KMS encryption, CloudTrail/Config audit trails, image scanning and hardening, Packer vulnerability pipelines, SAST and secret scanning in CI.

⚙

CI/CD Pipelines

GitHub Actions, GitLab CI, Jenkins and CircleCI with reusable workflows, environment gates and safe rollbacks. Jenkins → GitLab migrations that cut licensing costs.

₹$

Cloud Cost Optimization

FinOps grounded in data: right-sizing, x86 → ARM, Savings Plans sized to real usage, Spot for batch, off-hours scheduling and per-namespace Kubernetes cost allocation.

◉

Observability & SRE

OpenTelemetry, Datadog, Prometheus/Grafana, ELK and Splunk with correlation IDs across services. SLOs, error budgets, runbooks and blameless post-mortems.

✦

AI Agent Infrastructure

AWS Bedrock Agents, Knowledge Bases on OpenSearch vectors, Lambda action groups and Helm-packaged AI stacks. I also use AI coding agents to ship migrations faster.

// root cause or it didn't happen

Debug stories: how I solve problems by digging deep

Anyone can restart a pod. These are problems where the obvious fix was wrong and the real answer sat a few layers down. Filter by area, then open a story.

Kubernetes · Networking

DNS queries failing cluster-wide — but CoreDNS looked healthy

Symptom

Intermittent DNS resolution failures across services, even though both CoreDNS pods were Running and Ready.

Dig

Checked pod placement: the scheduler had put both CoreDNS replicas on the same node. All cluster DNS traffic was hitting one node's network limits.

Root cause

No anti-affinity rule on the CoreDNS deployment — high availability on paper, a single point of failure in practice.

Fix

Added podAntiAffinity so replicas always spread across nodes. Failures stopped and cannot recur from placement.

Kubernetes · HashiCorp Consul

Consul pods spiking CPU and crashing under config load

Symptom

Every application read configuration from Consul. As workloads grew, Consul pods spiked CPU and crash-looped.

Dig

Traffic analysis showed all queries funnelling into a fixed number of Consul pods regardless of how many nodes ran applications.

Root cause

Consul ran as a Deployment, so its capacity didn't scale with the workloads that depended on it.

Fix

Moved Consul to a DaemonSet: one agent per node, traffic stays local and capacity scales automatically with the cluster.

AWS · Kinesis Firehose

Logging SDK ran out of threads — only with Kinesis as the sink

Symptom

A custom logging SDK had two sinks. Under high load the Kinesis Firehose sink exhausted threads; the Logstash backup sink was fine.

Dig

Compared both sinks' transport: Kinesis used per-request HTTP calls, Logstash used a persistent stream with a dedicated connection.

Root cause

Every log line triggered an HTTP request, consuming CPU and a thread each time — fine at low volume, catastrophic at peak.

Fix

Tuned the SDK's buffer settings to batch records before sending to Kinesis. Thread exhaustion disappeared under the same load.

AWS · Lambda

Long-running Lambda hitting out-of-memory on financial files

Symptom

Recurring OOM errors and timeouts in a Lambda processing financial data files.

Dig

Profiled memory across invocations and found it climbing with every warm start.

Root cause

DB connections and socket objects were created per invocation and never reused or released.

Fix

Moved clients outside the handler for reuse, then redesigned into a fan-out pipeline (SQS → executor → S3 → parser → Elasticsearch), with files over 500 MB offloaded to auto-scaling EC2.

Security · Cloudflare

Stopping a live brute-force attack after geo-blocking failed

Symptom

Anomalous traffic spike on the load balancer metrics.

Dig

Traced request origins through Cloudflare monitoring and saw the attack shifting regions to evade geo-blocks.

Root cause

A distributed brute-force attempt — location-based rules alone could never keep up.

Fix

Implemented rate-based IP blocking rules that neutralized the attack within minutes.

Kubernetes · Memory

Pods OOM-crashing during image uploads

Symptom

Application pods repeatedly killed for exceeding memory limits.

Dig

Correlated crashes with upload activity and inspected what the pod held in memory at the time.

Root cause

Uncompressed images were being processed inside the pod, inflating memory usage on every upload.

Fix

Offloaded compression to Lambda, shrinking the pod's memory footprint and ending the instability.

Architecture · Zero downtime

Single-instance public prod → multi-AZ private subnets, no downtime

Symptom

Production ran on one instance in a public subnet — a single point of failure with direct internet exposure.

Dig

Mapped every dependency and traffic path so the cutover could happen live.

Root cause

Infrastructure grew organically before anyone owned the architecture.

Fix

Rebuilt with Terraform as multi-AZ public / private / data subnets behind an ALB with NAT for egress, then cut over with zero downtime.

DevSecOps · Secrets

Plaintext secrets everywhere → AWS Secrets Manager

Symptom

Credentials stored as plaintext environment variables across Elastic Beanstalk, Lambda and Kubernetes.

Dig

Inventoried every secret consumer and how each runtime loads configuration.

Root cause

No central secret store, so each platform invented its own approach.

Fix

Moved everything to Secrets Manager — a pre-execution binary for Beanstalk and secrets-store-csi-driver for Kubernetes — so secrets never appear in config panels.

// blueprints

Architecture diagrams

Systems I've designed and shipped. Click any diagram to enlarge.

Multi-AZ AWS VPC with public, private and data subnets for SOC 2 and PCI-DSS
SOC 2-ready multi-AZ VPCPublic / private / data subnets, NAT egress, KMS everywhere.
Event-driven fan-out Lambda pipeline with SQS, S3 and Elasticsearch
Fan-out Lambda pipelineGenerator → SQS → executor → S3 → parser → Elasticsearch.
AI agent infrastructure on AWS Bedrock with OpenSearch vector knowledge base and Lambda actions
AI agents on AWS BedrockBedrock Agents, OpenSearch vectors, Lambda action groups, Helm.
GCP to AWS cloud migration using AWS DMS
GCP → AWS migrationAWS DMS for databases, AI-assisted SDK refactoring.
OpenTelemetry collector shipping metrics and logs to Datadog
OpenTelemetry → DatadogClient-site telemetry into one pane of glass.
EKS platform with Karpenter, Gateway API, IRSA and secrets-store CSI driver
Production EKS platformKarpenter, Gateway API, IRSA, secrets-store CSI.

// toolbox

Skills: fundamentals first, tools second

Tools change every year. Networking, Linux, IAM, distributed systems and cost models don't — that's what lets me pick up any stack and debug it.

  • AWS
  • GCP
  • Azure
  • EC2
  • Lambda
  • ECS Fargate
  • EKS
  • Elastic Beanstalk
  • RDS
  • S3
  • SQS
  • AWS Batch
  • AWS DMS
  • Cloud Run
  • VPC & multi-cloud networking
  • Control Tower
  • Landing Zone
  • Cost Explorer
  • Savings Plans

✦ How I work with AI agents

I treat AI agents as a force multiplier, not a replacement for understanding. In the GCP → AWS migration I used AI-assisted refactoring to port application code from GCP SDKs to AWS SDKs, then verified every change against the fundamentals. I build agent infrastructure for clients too — Bedrock Agents calling Lambda actions, grounded by RAG on OpenSearch.

// git log --author="Mayank Gandhe"

Open source: what I've built and contributed

When a tool I depend on breaks, I fix it upstream instead of working around it. When the tool doesn't exist, I build it. Everything below is public on GitHub.

Featured projects

Merged upstream contributions

aws-ia / terraform-aws-opensearch-serverless

Official AWS Integration & Automation Terraform module for Amazon OpenSearch Serverless.

merged#12 Fix duplicate principals in access policySep 2025

Found while wiring this module to the Bedrock agent module for an AI-agent stack: the generated policy repeated the same principal and AWS rejected it. Fixed with distinct().

fluent / fluentd-kubernetes-daemonset

The official Fluentd DaemonSet and Docker images for Kubernetes log shipping.

merged#1312 Container log path configurable via envOct 2021

The container log path was hard-coded, which broke clusters with non-default runtimes. Made it configurable through an environment variable while keeping Fluentd's path syntax.

More tools I've built

See all repositories on GitHub →

// verified

Certifications & achievements

// questions I get asked

FAQ

What does a fractional DevOps engineer do?

A fractional DevOps engineer works part-time or on a retainer to own your cloud infrastructure, CI/CD, Kubernetes and security posture without the cost of a full-time hire. I set up the platform, document it, and leave your team with infrastructure as code and runbooks they can operate.

Can you build our AWS infrastructure from scratch as a founding DevOps engineer?

Yes. I've been the founding DevOps engineer at multiple startups, building Terraform-managed AWS environments from zero: multi-AZ VPCs with private subnets, EKS or ECS Fargate, CI/CD, secrets management, observability and SOC 2 / PCI-ready controls.

How do you reduce AWS costs?

By measuring before cutting: right-sizing instances, pods and RDS from real utilization, moving workloads from x86 to ARM (Graviton), right-sizing Savings Plans, using Spot for batch, and scheduling non-production and Karpenter nodes off outside business hours. On one fintech platform this delivered roughly 20% savings with no upfront payment.

Do you help with Kubernetes consulting and troubleshooting?

Yes. I'm a Certified Kubernetes Administrator who has run EKS, GKE and AKS in production, written cloud-agnostic Helm charts, migrated Ingress to the Gateway API, and debugged issues like CoreDNS replicas saturating one node's network and Consul overload fixed by moving to a DaemonSet.

Can you build infrastructure for AI agents?

Yes. I've built AWS infrastructure for AI agents using Amazon Bedrock as the model layer, Bedrock Agents with Lambda action groups, OpenSearch as the vector knowledge base for RAG, and Helm charts to deploy the AI stack into client environments.

Which open-source projects have you contributed to?

I have merged pull requests in aws-ia/terraform-aws-opensearch-serverless (fixing duplicate principals in access policies), fluent/fluentd-kubernetes-daemonset (configurable container log path) and simonmittag/j8a (merging secrets into YAML config, plus a logging fix). I also maintain my own tools such as helm-autoUpgrade, kDebugger, pull-aws-inventory and ECS-Terraform-FullSetup.

Which compliance frameworks have you worked with?

SOC 2, PCI-DSS, CCPA and GDPR — including KMS CMK encryption at rest and TLS in transit, CloudTrail and AWS Config audit pipelines, SCPs, Landing Zone and Control Tower, Packer-based vulnerability management and container image hardening.

// kubectl apply -f collaboration.yaml

Have a hard infrastructure problem?

Founding DevOps, fractional DevOps lead, Kubernetes consulting or a cost-optimization sprint — tell me what's breaking and I'll tell you how I'd dig in.

Based in Indore, India · Working remotely with teams in Australia, the US and worldwide