Harshwardhan Choudhary

services

Engagements I take on — end-to-end or advisory, depending on what you need.

• AWS Landing Zone Design

  Multi-account foundations with Control Tower, SCP governance, and identity federation. Validated against the Well-Architected Framework.

• Cost Optimization

  FinOps engagements, AWS Well-Architected cost pillar reviews, and multi-agent automation for ongoing cost visibility.

• Security Hardening

  IAM scope reduction, centralised logging normalised to OCSF, supply-chain security, and Well-Architected security reviews.

• DevOps & CI/CD Automation

  GitHub Actions and GitLab pipelines with OIDC, release governance patterns, DORA metrics, and deployment guardrails for regulated environments.

• GenAI Implementation

  RAG architectures on Bedrock, multi-agent systems, pgvector-based retrieval, and production-ready agent orchestration.

• Platform Engineering

  Amazon EKS platforms with GitOps delivery, developer experience as a first-class concern, and operational guardrails built in.

• Architectural Reviews

  Independent design reviews against the Well-Architected Framework. Written deliverables, recommendations prioritised by impact.

• Mentoring

  Helping engineers start their cloud journey. 1:1 coaching, structured training, and career guidance for AWS-focused platform and DevOps roles.

how i work

1. Discover

   Every engagement starts with listening. Not with a template, not with a “starter package” — because real cloud problems rarely fit a standard shape. You describe what you need; I ask the follow-ups that surface what you actually need, which is often adjacent to the original ask. By the end of this phase we’ve agreed on the problem, the constraints, and a shared definition of done.

2. Build

   From that definition of done, I work backwards. Priorities get explicit — must-haves first, should-haves next, nice-to-haves when there’s runway. Work happens in the open: I prototype before I promise, and you see demos early — from rough MVP to production-ready — so the direction stays yours to steer, not mine to surprise you with. Decisions are documented as they’re made, not reconstructed later when someone asks why.

3. Hand over

   The production version isn’t handed over at the end — it’s handed over throughout. Your team is building alongside me from the middle of the Build phase, not receiving a finished artifact at the end. Pair sessions, runbooks, post-mortems on real incidents. By the time the engagement closes, your team has been running the system for weeks. No black boxes, no surprise dependencies.

skills

• AWS Platform Engineering

  EKS · ECS · Lambda · Control Tower · multi-account governance

• Infrastructure as Code

  Terraform · Terragrunt · CDK · Terraform Cloud

• Kubernetes & Containers

  EKS · Helm · ArgoCD · GitOps delivery

• CI/CD & Automation

  GitHub Actions · GitLab · OIDC · release governance

• Data Engineering

  Kafka · Airflow · Glue · Parquet · Jupyter · ETL pipelines

• GenAI & ML

  Bedrock · SageMaker · RAG architectures · pgvector · LangChain · LangGraph · API-first development

• Observability

  OpenTelemetry · Prometheus · Grafana · OpenSearch · Loki · Datadog

• Security & Governance

  IAM · OCSF logging · SCPs · DevSecOps · audit pipelines · supply-chain security

• Languages

  Python · Bash · C++ (legacy) · YAML

education

• M.Sc. · Software Systems Birla Institute of Technology & Science (BITS), Pilani · TODO: year
• B.E. · Electronics & Communication Engineering Anna University · TODO: year

certifications

• AWS Certified AI Practitioner
• AWS Certified Solutions Architect – Associate
• AWS Certified Developer – Associate
• AWS Certified SysOps Administrator – Associate
• AWS Cloud Practitioner
• HashiCorp Terraform Associate
• Certified Kubernetes Administrator
• Certified Kubernetes Application Developer

things outside work

chess · cooking · forest walks · gardening

More spectator than player on chess. The rest, regularly.