@lbagga
About
Software Engineer at Bayer transitioning into Cloud and DevOps engineering, with 8+ years of software development experience across mobile and web. Currently working hands-on with AWS infrastructure, Terraform, and Kubernetes in a production environment.
鈿欙笍 Technical Foundation
AWS Certified Solutions Architect Associate and Cloud Practitioner, currently pursuing HashiCorp Terraform Associate, with hands-on focus on:
- Infrastructure as Code (Terraform, Helm)
- CI/CD pipelines (GitHub Actions, OIDC-based AWS authentication)
- Container orchestration (AWS EKS, Kubernetes)
- Serverless architecture (Lambda, S3, SNS, SQS, API Gateway)
At Bayer I work alongside senior infrastructure engineers on production AWS EKS deployments, writing Terraform for real infrastructure, and building automated pipelines.
Open to connecting with cloud professionals and exploring Cloud Engineer, DevOps Engineer, and Platform Engineer opportunities in Ottawa and remote. 馃
Available for
Nothing here yet.
Lalit Bagga's blogs
Recently published
Building a Serverless File Upload Pipeline: API Gateway, Lambda, S3, and SNS
May 12 路 6 min read 路 Intro In my last post, I broke AWS Lambda on purpose to understand IAM permissions. This time I wanted to go further, build a real pipeline where multiple AWS services talk to each other. The goal: se
Join discussion
Breaking Lambda to Learn It: S3 Triggers, Permissions, and Pitfalls
May 1 路 7 min read 路 Intro I wanted to build something simple upload a file to S3, have Lambda pick it up, log the filename. That's it. But "simple" in AWS always has layers, and somewhere between the IAM console and Clou
PParveen commented