01About 02Expertise 03Projects 04Incidents 05Experience 06Now 07Blog 08Contact Resume (PDF) ↗
DevOps Engineer · Infrastructure Team Lead

Designing and running cloud infrastructure for smart metering.

At Polaris Smart Metering I build and look after the AWS and OCI platforms that state electricity utilities across India use to collect and manage smart-meter data.

Scroll

I'm a DevOps engineer, and I lead a small infrastructure team. Most of my work is in the small decisions that keep a platform healthy: how a cluster scales, where a database should run, which alert is worth waking someone up for, and what a change will cost before it ships. I specialise in Kubernetes autoscaling, Kafka and MQTT, multi-account AWS and FinOps, and I pick up whatever else a project needs on AWS, OCI or open source. I care most about systems that are easy to operate and cheap to run.

smart meters devices EMQX mqtt Kafka strimzi AWS OCI services eks Grafana alerts

how a meter reading moves through the platform

3+
years running production infrastructure
$45K
saved a year through cost work
~90%
faster builds after reworking CI
4
current certifications in AWS, Kubernetes and Terraform

Expertise

Where I spend most of my time, across AWS and OCI.

01

Kubernetes & Autoscaling

Designing how workloads scale on EKS: Karpenter for nodes, KEDA for Kafka consumers, HPA and VPA for the rest, and fixed capacity where the load is steady. I also own the version upgrades, AMIs and launch templates.

EKSOKEKarpenterKEDAHPAVPAGoldilocksHelmArgo CD
02

Kafka & MQTT

Running the messaging layer for IoT traffic: EMQX clusters for device connections and Kafka for everything after. I've moved Kafka from EC2 to MSK and from MSK to Strimzi, and I plan moves like these so they can be rolled back.

KafkaStrimziMSKMirrorMaker 2EMQXMQTTNLB
03

Cost & FinOps

Treating cost as part of the design. I go through the AWS bill every month, right-size, buy reserved capacity, set retention policies, and switch off what isn't being used.

Cost ExplorerSavings PlansReserved InstancesCURAthenaECR lifecycletagging
04

Accounts, Security & Networking

Setting up multi-account AWS so it holds up as projects are added: an OU layout, SCP guardrails, SSO instead of IAM users, cost tags, VPCs per tier, and site-to-site VPN into on-prem data centres. Some projects also run on OCI.

OrganizationsSCPsIAM Identity CenterTag PoliciesVPCSite-to-site VPNOCIWAF
05

Databases & DR

Deciding where data should live and how it comes back after a failure: Aurora and self-managed PostgreSQL, MySQL for older apps, DR with pgBackRest, and tuning for write-heavy workloads.

PostgreSQLAuroraMySQLpgBackRestPgBouncerTimescaleDBValkey
06

Monitoring & On-Call

Building alerting people can act on: alarms from every account routed to one place, paging tuned so it means something, infra on-call, and a postmortem after each incident.

PrometheusGrafanaLokiFluent BitOpenTelemetryCloudWatchAlertmanager

Projects

Work I've designed or led, and what came out of it.

02
Kubernetes

Layered Autoscaling on EKS

Designed the move of the head-end services from static node groups to Karpenter, with KEDA scaling Kafka consumers on lag, HPA for request traffic and Goldilocks-guided VPA for sizing. I kept the meter-data workloads on fixed capacity on purpose, because their load is steady and moving them around only adds risk.

KarpenterKEDAHPAVPA
4production clusters
0managed node groups left
03
FinOps

AWS Cost Optimisation

Led the first round of a cost cleanup across our AWS accounts: retention policies on 500+ ECR repositories, 167 unused pipelines, build projects and registries removed after backing each one up, an idle node group switched off, and reserved instances for Aurora.

Cost ExplorerECRCodePipelineReserved Instances
$45Ksaved a year
500+ECR repos cleaned up
04
MigrationFinOps

Legacy Application Re-platforming

Moved an old application running on Python 2.7 and MySQL 8 onto smaller, cheaper infrastructure, with no change for the people who use it.

Python 2.7MySQL 8EC2
$2,200 → $1,300per month
41%lower cost
05
CI/CD

Change-Aware CI/CD Pipeline

Reworked a pipeline that rebuilt and redeployed the whole platform on every commit. It now maps changed paths to services, builds only those, and deploys across accounts with shared IAM roles.

CodePipelineCodeBuildIAM roles
30 → 3 mintypical build
~90%less time per commit
06
Kubernetes

EKS 1.33 → 1.35 Across Five Accounts

Upgraded every cluster from 1.33 to 1.35 before extended-support pricing started, working through custom AMIs, launch template versions that didn't apply as expected, and the IMDS hop limit.

EKSEC2Launch TemplatesAMIs
5AWS accounts
1.33 → 1.35EKS version
07
DataReliability

PostgreSQL DR with pgBackRest

Designed disaster recovery for self-managed Postgres on EC2 with pgBackRest physical and logical backups instead of streaming replicas, so recovery stays predictable without paying for a second database. The S3 path is locked so backups can't be deleted.

PostgreSQLpgBackRestS3IAM
0standby servers
Delete-proofbackups in S3
08
Governance

Multi-Account Landing Zone

Designed the OU layout, SCP guardrails, tag policy and SSO permission sets, and moved the team off IAM users. I kept cost tags report-only on purpose, because enforcing them would have blocked node launches in the middle of a scale-up.

OrganizationsSCPsTag PoliciesIAM Identity Center
56% → 100%instances tagged
SSOin place of IAM users
09
Capacity

Capacity Planning for 10M Meters

Built a capacity model for a 10-million-meter rollout from 14 days of production data, instead of multiplying today's numbers. It showed that pods and Kafka partitions scale out fine and the database writer doesn't, because its load is almost all writes.

KafkaAuroraPerformance InsightsLocust
10Mmeters modelled
14 daysof production data
10
Open source

Portfolio Site on Cloudflare

Built and host this site on Cloudflare's free plan. Every script is pinned and hashed under a strict CSP, the background is rendered once and served as video, and a daily GitHub workflow checks the live site from outside.

View on GitHub ↗
Cloudflare WorkersCSPGitHub Actions
$0hosting beyond the domain
40checks every day

Production Incidents

Issues I root-caused on call, and the fixes that followed.

01
PostgresLinux

PostgreSQL Connection Failures

Services across one cluster kept dropping their Postgres connections with "unexpected EOF", which pointed at the network. I traced it to the database host instead: strict memory overcommit with no swap left Postgres about 140 MB to start new connections. Fixed with one kernel setting and no restart.

PostgreSQLLinuxOKE
140 MB → 10 GBmemory headroom for new connections
02
KubernetesKafka

Kafka Consumer Lag Caused by VPA

A consumer group kept rebalancing and lag reached 20 million messages. VPA had cut the decoder pods from 500m to about 53m CPU, so batches ran past the poll timeout and the consumers were dropped from the group. I pinned CPU at 200m and moved VPA to recommendation-only mode.

VPAKEDAKafka
20Mmessages of lag
53m → 200mCPU per pod
03
MQTT

EMQX Cluster Cold-Start Failure

After a full outage no broker would rejoin, because the boot script stopped any node that couldn't find a peer. I bootstrapped one node manually, joined the rest to it and restored the configuration. The investigation also showed the same check had been producing empty 187-byte backups.

EMQXAuto Scalinguser data
187 bytesempty backups found

Experience

Three years at Polaris Smart Metering. I joined as an intern and now lead the infrastructure team.

  • DevOps Engineer, Infrastructure Team Lead
    Polaris Smart Metering · team of five · 22 AWS accounts and OCI
    May 2025 – now
  • AWS Cloud Engineer
    Polaris Smart Metering · IAM and SSO model · Redis to ElastiCache · Kafka to MSK · first EMQX cluster
    Nov 2023 – Apr 2025
  • Cloud Engineering Intern
    Polaris Smart Metering · AWS inventory · first alarms and dashboards
    Aug – Oct 2023
  • B.Tech, Computer Science
    B.K. Birla Institute of Engineering & Technology, Pilani
    2020 – 2024

What I'm working on

  • Capacity Planning for 10M Meters
    Where Kafka and the databases need to change at five times today's load
  • New State Platform on Terraform
    Terraform · Argo CD · dev, stage and prod as code
  • Backend Engineering & DSA
    Boot.dev, in Python

Get in touch

If you're working on something similar, or hiring for it, email is the quickest way to reach me.

Sushant Nagil

  • DevOps Engineer · Infrastructure Team Lead, Polaris Smart Metering
  • Kubernetes · Kafka & MQTT · AWS & OCI · FinOps
  • CKA · AWS Solutions Architect · AWS Data Engineer · Terraform
  • B.Tech Computer Science, BKBIET Pilani · Jaipur, India