/user/kayd @ devops :~$ cat about.md

About Karandeep Singh About Karandeep Singh

QR Code linking to: About Karandeep Singh

Summary

Karandeep Singh — Senior DevOps Engineer, Calgary, AB I’m a Senior DevOps and Site Reliability Engineer based in Calgary, Alberta. I’ve spent over a decade in software and the last six-plus years focused on building, automating, and operating scalable AWS infrastructure — the kind that keeps companies …
Karandeep Singh
Karandeep Singh — Senior DevOps Engineer, Calgary, AB

I’m a Senior DevOps and Site Reliability Engineer based in Calgary, Alberta. I’ve spent over a decade in software and the last six-plus years focused on building, automating, and operating scalable AWS infrastructure — the kind that keeps companies running at 2 AM when the alerts fire.

KARANDEEP(1)Calgary, ABKARANDEEP(1)

Name

karandeep — senior DevOps / site reliability engineer

Synopsis

karandeep [--aws] [--kubernetes] [--jenkins] [--terraform] problem

Description

Builds, automates and operates AWS infrastructure. Ten-plus years in software, six-plus of them on AWS. Writes it all down at karandeepsingh.ca — currently 92 articles and 18 cheatsheets.

Options

  • --aws — EC2, S3, Lambda, ECR, RDS/Aurora, VPC, IAM, CloudWatch, Step Functions, Athena
  • --kubernetes — EKS, ECS/Fargate, Docker; CKAD-certified
  • --jenkins — controller, build-agent fleet, shared-library pipeline tooling
  • --terraform — plus CloudFormation, Ansible and Packer, for immutable infrastructure
  • --go — small operational tools that replace bash once it needs tests and arguments

Exit status

Returns 0 when the runbook works at 2 AM without you.

See also

aws(1), kubectl(1), terraform(1), atuin(1)

karandeep 6.0-LTSAugust 2026KARANDEEP(1)

What I work on

Cloud architecture, infrastructure automation, and CI/CD. The layers I spend my week in, bottom to top:

stack.svg
The layers of the stack I work inFive layers, top to bottom: delivery (Jenkins controller, agent fleet, shared libraries); compute (EC2, ECS and Fargate, EKS, Lambda); infrastructure as code (Terraform, CloudFormation, Ansible); images (Packer, immutable AMIs, ECR); and guardrails (IAM, Secrets Manager, CloudWatch, Athena).deliveryJenkins controller · agent fleet · shared librariescomputeEC2 · ECS/Fargate · EKS · LambdacodeTerraform · CloudFormation · AnsibleimagesPacker · immutable AMIs · ECRguardrailsIAM · Secrets Manager · CloudWatch · Athena
Nothing here is a preference. Each layer exists because the one below it stopped being reproducible by hand.

A few things that came out of those layers:

  • Automating Linux patching with Lambda + Step Functions + EventBridge, so a fleet patches itself on a schedule instead of on a ticket.
  • Cutting S3 storage costs by finding orphaned objects with Athena and automating lifecycle policies with Ansible.
  • Moving a Jenkins controller onto Packer-built AMIs. Deployment went from 40-plus minutes to roughly 15, and rebuilds became repeatable and version-controlled instead of remembered.
  • Rotating credentials across Jenkins, Bitbucket and AWS during a supply-chain incident, then delivering secrets through S3 and Secrets Manager so the next rotation was a job, not a weekend.

Get new articles by email

One DevOps article a week, plus the 18-cheatsheet PDF pack. No spam, one click to leave.

Where the week actually goes

Not the job description — the honest split, averaged over a quarter:

Why I write here

Most online tutorials skip the failure modes. They show you the happy path, hand you a working snippet, and leave you stranded the first time it breaks at 2:13 AM in production.

vimdiff most-tutorials.md karandeepsingh.ca
most tutorials

Start from a clean account.

Paste the snippet that works.

Stop at the happy path.

Never mention the version, the Region, or the flag that makes it fail.

here

Start from the actual problem.

Try the obvious thing and show it break.

Fix it, and say why it was wrong.

End with the version that goes in the runbook.

That’s the whole format, in order:

method.svg
How an article here is builtFive steps in order: start with a real problem; try the simple solution; watch it fail in a specific, documented way; show the fix and why the first attempt was wrong; end with the version that goes in the runbook. Step three is highlighted as the one most tutorials leave out.1start with a real problem2try the simple solution3watch it fail, and document how4show the fix, and why5end with the runbook version
Step 3 is the one everyone else deletes. It is the reason the rest is worth reading.

If that means an article on sed is mostly about the time the GNU vs. BSD difference broke a deploy on a developer’s MacBook — that’s the version I’d want to read.

Certifications

  • AWS Certified Solutions Architect – Professional
  • AWS Certified Solutions Architect – Associate
  • CKAD – Certified Kubernetes Application Developer (The Linux Foundation)

Currently

systemctl status karandeep.service active
● karandeep.service - Senior DevOps Engineer, Calgary AB
     Loaded: loaded (/lib/systemd/system/karandeep.service; enabled; preset: enabled)
     Active: active (running) since ~10 years in software, 6+ on AWS
      Tasks: cloud architecture, CI/CD, infrastructure automation
     Memory: AWS, Kubernetes, Jenkins, Terraform, Go
     CGroup: /system.slice/karandeep.service
             └─open to talking about AWS cost, Jenkins at scale, and the command line
Aug 2026  writing about Lambda cost, Aurora, and terminal tooling
Aug 2026  this site got an MCP server, so an AI client can read it directly

Calgary’s DevOps community is smaller than Silicon Valley’s, but the work is real and the stakes are real. I’ve spent the last several years in SaaS and infrastructure-operations roles at Calgary technology companies — environments where the system going down costs measurable money per minute, and where “we’ll fix it next sprint” is rarely an acceptable answer.

Connect

Reach out if you want to talk DevOps, compare notes on cloud architecture or CI/CD, or just argue about whether awk is the right tool for a given task (it usually is).

Package configuration

Configuration contact-karandeep

Happy to talk about AWS cost, Jenkins at scale, Kubernetes, or the command line.

Replies come from Calgary, so allow for Mountain Time.

Do you accept?

< Email >< Later >

Get new articles by email

One DevOps article a week, plus the 18-cheatsheet PDF pack. No spam, one click to leave.