Skip to content
View nitishponguluri-collab's full-sized avatar

Block or report nitishponguluri-collab

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
nitishponguluri-collab/README.md

Nitish Chowdari Ponguluri

Senior Cloud Platform Architect  ·  Hyderabad, India

LinkedIn  AWS SAP

I've spent 15 years making cloud infrastructure boring — in the best way possible. Boring means your team ships without opening tickets to the platform team.

ValueLabs

I've run hybrid AWS and Azure environments — eight AWS accounts, AKS clusters alongside EKS, and everything wired together with Terraform and GitOps. Built the multi-account landing zone from scratch — account vending, SCPs, network topology, guardrails that actually hold under pressure. Put EKS platforms into production with GitOps workflows that teams adopted without a training deck. Wrote the Terraform modules we still use. When I left, the platform ran itself most days.

Optum

Healthcare cloud means HIPAA and SOC2 aren't checkboxes before a release — they're real audit environments with real consequences if you get it wrong. That shaped how I think about compliance: architect it in from day one, don't layer it on after the fact.

Featured repos

Repo What it is
aws-multi-account-landing-zone The landing zone pattern I'd build again if I had to start over
terraform-aws-modules Modules with sensible defaults, not just thin wrappers
eks-platform-blueprint EKS setup that gives teams guardrails without getting in their way
devsecops-pipeline-templates Security gates that don't break velocity
aws-mlops-platform SageMaker pipelines, MLflow tracking, Bedrock access with per-team IAM scoping — the AI/MLOps layer on top of the platform
azure-platform-blueprint AKS platform with Azure AD integration, ArgoCD GitOps, Prometheus, and AGIC — the Azure equivalent of the EKS blueprint

Popular repositories Loading

  1. nitishponguluri-collab nitishponguluri-collab Public

    Senior Cloud Platform Architect · AWS · EKS · Terraform · MLOps · Open to Remote

  2. aws-multi-account-landing-zone aws-multi-account-landing-zone Public

    Production-ready AWS multi-account landing zone — Organizations, SCPs, IAM Identity Center, CloudTrail, Config, and Security Hub wired together with Terraform.

    HCL

  3. terraform-aws-modules terraform-aws-modules Public

    Opinionated Terraform modules for AWS — VPC, EKS, RDS, IAM, observability, SageMaker pipelines, and S3 backend. Production defaults, not minimal configs.

    HCL

  4. eks-platform-blueprint eks-platform-blueprint Public

    Opinionated EKS platform — Karpenter, ArgoCD, Prometheus, ALB Controller, and ExternalDNS wired together. GitOps from day one.

    HCL

  5. devsecops-pipeline-templates devsecops-pipeline-templates Public

    GitHub Actions workflows for secure delivery — Terraform plan/apply with OPA policy gates, container scanning with Trivy, EKS deploy with Helm, and compliance checks with Checkov.

    Shell

  6. aws-mlops-platform aws-mlops-platform Public

    MLOps platform on AWS — SageMaker pipelines, managed MLflow tracking, Bedrock access with per-team IAM scoping, and model serving on EKS. Built with Terraform.

    HCL