Cloud Platforms
Popular
Cloud Bill Review
A detailed review of your cloud invoices that ends with a ranked list of savings, each marked with the effort and risk involved.
₹13,999
Cloud Platforms
OB-CLD-102
Infrastructure as Code Setup
Your cloud setup rewritten as version-controlled code, with separate accounts, a planned network and no more manual console changes.
- Timeline
- 25 working days
- Deliverables
- 7 listed
- Fixed price
- ₹48,999
What this service delivers
Infrastructure built by clicking around a console is hard to review, hard to copy and risky to change. We describe your cloud environment as code instead. Production and non-production run in separate accounts, private subnets stay private, access roles are given to workloads rather than individuals, and state is stored remotely with locking so two people cannot overwrite each other. Modules are written for reuse, and every change flows through a pull request that shows the planned effect before anyone approves it.
Deliverables 7 items
What you receive
- Reusable modules that define the network, subnets, firewall rules, identity roles and shared services
- Separate accounts for production and for staging
- Remote state stored centrally, with locking and a history of versions
- Pull request workflow that previews changes and applies them on merge
- Existing resources imported into the code wherever it is practical
- Written standards for naming, tagging and environments
- Runbook covering first-time setup, drift checks and disaster recovery
How the work runs, in 4 steps
-
Step 1: Survey
We list what exists today and how it is connected
-
Step 2: Design
Account layout, network ranges and module boundaries are agreed
-
Step 3: Codify
Resources are written as code and imported, environment by environment
-
Step 4: Handover
The review workflow is switched on and your engineers are walked through it
Who it suits, and what we need from you
Ideal for
- Companies whose infrastructure knowledge sits with one person
- Teams preparing for auditors who will ask how infrastructure changes are approved
- Startups about to add a new environment or region
What we need from you
- Administrator access to every cloud account in scope
- A maintenance window for moving shared networking
- An engineer available for the handover sessions
You share these through the brief in your account after checkout.
What changes for your team
-
01
Every production change is reviewed before it happens
-
02
A lost environment is recreated from code, not patched by hand
-
03
New joiners learn the setup by reading the repository
Questions about this service
Most resources are imported without being recreated. Where networking must change, we schedule it inside an agreed maintenance window.
You can, but those changes will show up as drift. The runbook explains how to bring them back into code afterwards.
This is a remote technology service, so nothing is shipped physically. Work is delivered into systems you control. Read delivery and handover and refunds and cancellation for the full terms.