Skip to content
View la-moss's full-sized avatar

Block or report la-moss

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 supported. This note will be visible to only you.
Report abuse

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

Report abuse
la-moss/README.md

Lee Moss

Azure Platform Engineer building secure, governed cloud foundations with Terraform, landing zones, identity, and platform-focused incident labs.

I build and support secure Azure infrastructure with a focus on Terraform, governance, identity, and hybrid platform design.

Most of my work sits at the foundation layer: landing zones, policy guardrails, RBAC, CI/CD, and the standards that make cloud environments repeatable, secure, and easier to operate at scale.

I am particularly interested in what happens when platforms drift from design into reality, where routing, identity, policy, or runtime behaviour expose flaws that architecture diagrams never show. That is why I also build hands-on incident labs to practice debugging, failure isolation, and root-cause analysis under pressure.

Everything shared publicly is built in personal sandbox environments only.


What I Focus On

  • Azure platform engineering
  • Terraform and infrastructure delivery
  • Landing zones and cloud foundations
  • Governance, policy, and guardrails
  • Entra ID, RBAC, and least-privilege design
  • Hybrid networking and platform reliability
  • Incident debugging and failure analysis

Current Areas of Interest

  • Secure Azure platform foundations
  • Terraform module design and infrastructure workflows
  • Azure Policy and governance at scale
  • Identity and access design across platform environments
  • Hybrid and private networking patterns
  • Failure-mode thinking and platform troubleshooting
  • Repo-based incident labs for realistic debugging practice

Incident Labs

Alongside platform engineering work, I build repo-based incident labs based on realistic failure modes.

These labs are designed to simulate the kind of issues that appear when systems move from clean architecture diagrams into live environments, where the real problem is often hidden behind misleading symptoms.

Typical areas include:

  • DNS and routing failures
  • Private endpoint and private DNS issues
  • IAM / RBAC and access-control problems
  • Terraform design and coupling risks
  • Guardrail and governance failures
  • Runtime instability and verification failures
  • Failure isolation and root-cause analysis under pressure

The goal is simple: clone a broken repo, investigate signals, identify root cause, implement a fix, and verify behaviour.


What You’ll Find Here

This GitHub is mainly used for:

  • platform and infrastructure projects
  • Terraform-based work
  • governance and identity-focused repos
  • incident lab repositories
  • experiments related to platform reliability and failure analysis

Principles Behind My Public Work

  • Build in sandbox only
  • Keep infrastructure work practical
  • Focus on foundations before hype
  • Prefer clear reasoning over tool-chasing
  • Treat troubleshooting as a core engineering skill
  • Share work that reflects real operational problems, not just ideal-state architecture

Note

All content shared here is built in personal sandbox environments only.
No employer systems, data, or internal configurations are used.


Popular repositories Loading

  1. la-moss la-moss Public

  2. week-1 week-1 Public

    HCL

  3. week-2 week-2 Public

    HCL

  4. week-3 week-3 Public

    HCL

  5. week-3.5 week-3.5 Public

    HCL

  6. week-4 week-4 Public

    HCL