Generating AI answer…
SRE & DevOps Engineering Blog | Ankit Bhardwaj
Field notes from production: Kubernetes, AWS, Terraform, database migrations, and real SRE...
About — 12+ Years in Engineering & DevOps | Ankit Bhardwaj
Ankit Bhardwaj's career: from web developer to Site Reliability Engineer. 12+ years across...
Contact | Ankit Bhardwaj
Get in touch with Ankit Bhardwaj — Site Reliability Engineer & DevOps specialist. Reach ou...
Optimizing Kubernetes Costs on AWS: A Practical Guide | Ankit Bha...
Practical strategies that meaningfully cut my Kubernetes cluster costs on AWS — right-sizi...
Field notes from production: Kubernetes, AWS, Terraform, database migrations, and real SRE war stories from running infrastructure at 99.99% uptime.
Ankit Bhardwaj's career: from web developer to Site Reliability Engineer. 12+ years across telecom, financial data, and healthcare. AWS & Terraform certified.
Get in touch with Ankit Bhardwaj — Site Reliability Engineer & DevOps specialist. Reach out by email, LinkedIn, GitHub, or contact form. Chandigarh, India.
Practical strategies that meaningfully cut my Kubernetes cluster costs on AWS — right-sizing, cluster autoscaling, spot instances, and storage optimization.
An idle public IP sat on my EC2 instance for months, billing me for nothing. The fix was simple — I'd just lacked the confidence to do it without downtime.
We migrated Aurora to RDS with zero downtime — then quietly paid for two databases for two months. The fix wasn't more knowledge. It was a forcing function.
Most of us use the same 20% of Terraform daily. The rest turned up two features I wish I'd known sooner: ephemeral blocks and DynamoDB-free state locking.
Selected work: XIRR Ledger serverless finance tool, zero-downtime AWS migrations, Kubernetes platform engineering, and full-stack builds across industries.
Everyone treats Aurora as the premium PostgreSQL choice on AWS. But for regulated healthcare workloads, what mattered was how fast CVE patches actually land.
Our Aurora to RDS cutover went perfectly — pgcopydb, logical replication, all of it. Then the app wrote to RDS and every insert exploded. The cause: sequences.