Prem Gurung · Principal Cloud & Platform Consultant

Cloud architecture that moves engineering forward.

I help engineering leaders make clear AWS architecture decisions, build reusable platform capabilities and improve resilience—connecting technical design with business priorities and operational reality.

Independent expertise · Nepal & international clients

The outcomes that matter

Architecture, teams and business outcomes

01

Make better decisions

Understand architectural options, trade-offs and priorities before committing engineering time and investment.

02

Enable engineering teams

Create reusable platform capabilities with clear ownership, practical automation and a path to adoption.

03

Prepare for failure

Connect recovery architecture with runbooks, responsibilities and evidence that the organisation can recover.

Focused engagements

Start with the problem you need to solve

AWS Architecture Session

Making a migration, scaling or design decision? Clarify requirements, compare options and leave with practical next steps.

Explore the session →

Platform Engineering Review

Help teams deliver independently with reusable infrastructure, better automation and clear platform ownership.

Explore the review →

AWS Resilience Assessment

Understand failure paths, recovery dependencies and gaps between your recovery objectives and operational readiness.

Explore the assessment →

My approach

Good architecture starts with the right questions.

Direct collaboration with the person doing the architecture work, from the first conversation to the recommended next steps.

  1. Understand the business problem

    What matters, why now and who owns the decision.

  2. Align requirements and stakeholders

    Agree constraints, priorities and responsibilities.

  3. Evaluate architecture and trade-offs

    Examine complexity, reliability, delivery and operational effort.

  4. Create an actionable plan

    Leave teams with decisions, ownership and prioritised work.

Architecture in practice · Illustrative example

A reusable platform needs more than automation.

Consider a team turning repeated infrastructure requests into a self-service catalogue. The decision involves ownership, guardrails and adoption as much as Terraform modules.

Explore the problem, trade-offs and evidence →

Independent expertise

Hi, I’m Prem Gurung.

My background spans more than a decade in IT, from Linux administration to cloud consulting. I bring that operational perspective to AWS architecture, platform engineering and resilience, helping teams connect technical decisions with the people who deliver and operate them.

More about my approach →

Insights

Technical depth behind the decisions

Practical writing on AWS, Kubernetes, infrastructure automation and observability.

Feb 2024

Lets Learn about AWS SCP

What are SCP ? Link to this heading SCP permissions are crucial guardrails within AWS environments, serving as intersections of identity policies, resource …

Nov 2023

Pod and Container Security

A Deep Dive into Pod and Container Security Link to this heading To keep Kubernetes clusters safe, it’s crucial to prevent unwanted changes that could …

Nov 2023

Resource Management In kubernetes

Mastering Kubernetes Scheduling and Resource Management: A Comprehensive Guide Link to this heading Kubernetes, the orchestrator of containerised applications, …

Browse all insights →

Nepal & international

What does your platform need to do next?

Share your context, the decision you’re facing and what a useful outcome looks like. We’ll agree an engagement around your goals and scope.

Start a conversation