Stralya

DevOps

Infrastructure as code consultant

An infrastructure as code consultant replaces manual cloud setup with versioned, reviewable code. We cover Terraform and OpenTofu, remote state, modules, drift detection and secrets.

TerraformOpenTofuPulumi

In short

An infrastructure as code consultant replaces manual cloud setup with versioned, reviewable code. We cover Terraform and OpenTofu, remote state, modules, drift detection and secrets. The result: environments you can rebuild, compare and audit. Stralya works as a team and hands over documentation and training.

2 to 3 weeks

IaC audit

Existing code, state files, console changes and permissions reviewed, with a codification plan.

6 to 12 weeks

Typical engagement

From the audit to environments changed only through pipelines, handover included.

2 clouds

Vendor-neutral

We work on AWS and Azure and pick tools your team can maintain.

An infrastructure as code consultant helps you describe servers, networks and cloud services in code instead of clicking through consoles. Changes become reviewable, repeatable and reversible.

Stralya's team designs the structure, writes the first modules with your engineers and sets the rules that keep it clean. This page belongs to our DevOps consultant offer.

Why infrastructure as code matters

Manual infrastructure ages badly. Nobody remembers who changed what, and no two environments match.

Code fixes that. Every change has an author, a review and a history. A new environment becomes a command, not a project.

Terraform and the tools around it

Terraform is the most common choice, and OpenTofu is its open source fork. We also use Pulumi when teams prefer a general-purpose language, and Ansible for server configuration.

ToolBest forWatch out for
Terraform / OpenTofuMulti-cloud provisioning with a large provider ecosystemState management and module sprawl
PulumiTeams that prefer TypeScript, Python or GoLess shared convention across teams
AnsibleConfiguring servers and installing softwareNot designed for long-lived state
AWS CloudFormation / CDKAWS-only estatesLock-in to one cloud

The right tool is the one your team can maintain.

Structuring Terraform projects

Good structure prevents most pain later. We usually set up:

  • Remote state

    with locking, one state per environment and component

  • Reusable modules

    for networks, clusters, databases and permissions

  • Environment separation

    with clear promotion from dev to production

  • Naming and tagging rules

    so costs and owners are visible

  • Review workflow

    where every change goes through a plan and a pull request

Common mistake: one giant state file for everything. It slows every change and raises the risk of each one.

Drift detection and control

Drift happens when real infrastructure no longer matches the code, usually after a manual fix during an incident.

We handle it in three steps:

STEP 01

Detect

Scheduled plans that report differences without applying them.

STEP 02

Decide

Either bring the code up to date or revert the manual change.

STEP 03

Prevent

Restrict console access and route urgent changes through a fast path in the pipeline.

Secrets management

Secrets do not belong in repositories or plain pipeline variables. We set up a proper secret store and show how code references it without exposing values.

  • Secret managers such as AWS Secrets Manager, HashiCorp Vault or SOPS

  • Short-lived credentials for pipelines instead of long-lived keys

  • Rotation and access review as routine tasks

  • Scanning to catch secrets committed by mistake

Free infrastructure audit

Share how your environments are built today and we tell you where the risks are.

Book a free audit

How an infrastructure as code mission works

STEP 01

Inventory

We list what exists, what is managed and what is not.

STEP 02

Design

We agree on structure, tooling and conventions.

STEP 03

Import and build

We bring existing resources under code and build new ones from modules.

STEP 04

Automate

Plan and apply run in your pipeline with approvals.

STEP 05

Hand over

Documentation and a working session for your engineers.

Duration depends on how much infrastructure exists and how much is undocumented.

How to choose an infrastructure as code consultant

CriterionWhat to look for
Hands-on depthReal experience with state, modules and imports
Cloud knowledgeUnderstanding of the services behind the code
ConventionsClear standards your team can follow after the mission
SafetyPlan review, approvals and limited credentials
HandoverDocumentation and training included

Deliverables

  • Inventory of current infrastructure

  • Repository structure and reusable modules

  • Pipeline for plan and apply with approvals

  • Drift detection schedule

  • Secrets management setup and guidelines

  • Documentation and training

Infrastructure as code pricing

Every engagement starts with a diagnosis of your accounts and existing code, and ends with a fixed quote. Durations are typical, not promised, and depend mostly on how much of the estate was built by hand.

FormatDurationPrice
IaC audit and drift report2 to 3 weeksFixed quote after diagnosis
Codification of an existing estate6 to 12 weeksFixed quote after the assessment
Within a full DevOps transformation3 to 6 monthsFixed quote after the assessment

What changes the price: number of cloud accounts and environments, share of resources built by hand, number of teams consuming modules and compliance requirements.

The quote covers senior consultants only, a defined set of accounts and the deliverables of each phase. Cloud resources, state storage and any commercial licence for an IaC platform or policy tool are billed by their providers, separately from our fees.

Frequently asked questions

Terraform or OpenTofu?

Both work for most teams and share the same core syntax. We help you pick based on licensing preferences, tooling and your existing code.

Can you import our existing infrastructure?

Yes. We import resources step by step, starting with the least risky ones, and check each plan before applying.

How do you stop manual changes?

With access rules and a fast path for urgent fixes. If changing code is easy, people stop reaching for the console.

Do you only work on AWS?

AWS is our main platform, and the same approach applies to Azure. See our cloud consultant page for architecture work.

Will our team be able to maintain it?

That is the goal. We write conventions, keep modules simple and train your engineers during the mission.

Reviewed by

Julien Mauclair

Co-founder, technical delivery · Stralya

Last updated:

Environments to rebuild? Talk to the team

Reply within 24h · First call, no commitment