Penang · Infrastructure as code

Cloud Grove Consulting

Checklist-led programming consulting for teams shipping Terraform, OpenTofu, Pulumi, and CI pipelines that keep cloud estates auditable. Scoped project work and ongoing technical advisory from George Town.

Fiber optic cables managed in a server room with modern connectivity hardware

Physical racks still matter when your modules declare them.

When drift hides inside modules

Most cloud incidents trace back to state that nobody can replay: hand-edited console changes, forked modules, or pipelines that deploy without policy gates. We document the current graph, write the target module layout, and leave runbooks your engineers can execute without us in the room.

Engagements stay bounded—design reviews, import plans, pipeline hardening—not open-ended staff augmentation unless you ask for advisory hours with a written scope.

We do not sell licenses or resell cloud capacity. You pay for defined consulting blocks that end with merged pull requests, module boundaries, and evidence your auditors can follow.

Three ways teams bring us in

Person working on a laptop in a modern office setting

Greenfield module kit

Opinionated folder layout, remote state, and environment promotion rules for a single cloud account or landing zone slice.

Digital tablet with planner layout and stylus on a desk

Import & refactor sprint

Map click-ops resources into code, split monolithic states, and add policy-as-code checks before the next production promotion.

Office desk with a widescreen monitor displaying colorful artwork

Advisory retainer

Standing office hours for principal engineers—pipeline failures, module API design, and cost guardrails without a full project charter.

Readiness checklist before we write code

Use this list internally; we walk through it on the first call so scope stays honest.

  • Identity for CI runners and human break-glass accounts is documented, not shared in chat.
  • Remote state buckets or equivalents have versioning and least-privilege IAM attached.
  • Production changes ride the same pipeline as staging—no console exceptions without a ticket.
  • Module boundaries match team ownership; shared networking is not copied into every service repo.
  • Rollback means reverting a known commit, not guessing which console toggle moved.

Online service disclosure (Malaysia)

Supplier
Cloud Grove Consulting (Priya Rashid, sole proprietor)
SSM registration
202003481230
Address
46,Jalan Macalister, 10400 George Town, Malaysia
Contact
+60-4-0000-1712 · info@cloud-grove.digital
Offer
Paid programming consulting: scoped infrastructure-as-code projects and advisory retainers. Fees quoted per statement of work; starting figures labelled when shown.
Payment
Bank transfer or invoice per agreed statement of work (methods confirmed before work starts).
Supply timing
Consulting delivered remotely or on-site in Malaysia; schedules agreed in writing per engagement.

Full terms · Refund policy