Skip to main content
Service · Configuration management

CONFIGURATION MANAGEMENT

  1. Home
  2. Services
  3. Configuration management
Configuration management

Ansible for repeatable fleet behaviour

Ansible turns drift-prone configuration into reviewed playbooks: essential when Linux, Windows, network, and cloud APIs all need the same audit trail. Where Terraform declares what infrastructure exists, Ansible declares how hosts and clusters are configured: idempotently over SSH or WinRM without a permanent agent.

We use Ansible across hybrid environments spanning Linux, Windows, network gear and SaaS APIs: usually as the configuration partner to a Terraform-built foundation, sometimes standalone for legacy fleets that aren't going anywhere fast.

Where Ansible shines

  • OS hardening, patching and compliance baselines across Linux and Windows.
  • Application bootstrap and configuration on top of cloud or on-prem VMs.
  • Network device automation (Cisco, Juniper, FortiGate) using vendor collections.
  • Recurring operational runbooks (rotate, scale, fail over, restore).
Our approach

How we use Ansible at The Factory

A small set of disciplines that make playbooks survive the team that wrote them.

Roles and collections

Reusable roles with documented inputs, sane defaults and Molecule tests. Internal collections version common patterns so playbooks stay short and readable.

Controller-driven runs

Plays run from Ansible Automation Platform (Tower / AWX), not from a laptop. RBAC, scheduling, surveys and a real audit trail come for free; no SSH keys live on engineers' machines.

Pipelines and policy

Lint, syntax checks, ansible-lint and Molecule tests run on every pull request. Production playbooks ship through the same CI/CD pipeline as application code: and live next to the Terraform that built the targets.

Outcomes

What disciplined Ansible gives you

Configuration management isn't glamorous, but configuration drift is the silent cost driver in most hybrid environments. We make drift the exception, not the default.

  • Consistent fleets: every host configured the same way, every time.
  • Faster patching: patch cycles measured in hours, not weeks.
  • Audit-ready compliance: playbooks themselves are the evidence.
  • Lower MTTR: operational runbooks codified, not tribal.
  • Vendor-agnostic reach: same engine for Linux, Windows, network and cloud APIs.
  • Knowledge retained: when an engineer leaves, the playbook stays.
Use cases

Where customers ask us to help

Greenfield Ansible practice

You are starting Ansible from scratch and want roles, collections, CI and a controller in place before the first production play.

Legacy fleet rescue

You have hundreds of hand-configured VMs and a "don't touch it" reputation. We codify the existing state, then refactor it.

Compliance baselines

You need CIS, BSI or sector-specific hardening across Linux and Windows hosts: applied, validated and reported on a schedule.

Why The Factory

Boring, predictable, automated

Tested playbooks

Molecule, ansible-lint and integration tests on every change. Playbooks don't reach production untested.

Security-first

ISO 9001, ISO 27001, and NEN 4400-1 certified: Vault for secrets, signed roles, and least-privilege controllers.

Knowledge transfer

We pair with your team and leave behind documented patterns and a controller they can run themselves.

Our Ansible consultancy across the Netherlands

The Factory is a Dutch cloud consultancy based in Rijswijk (Zuid-Holland). We work with organisations across the Randstad (Amsterdam, Utrecht, Rotterdam, Den Haag, Eindhoven), and with customers elsewhere in the European Union. Our architects and platform engineers operate in Dutch and English, with experience on AWS, Azure, and hybrid environments.

  • Based in Rijswijk: on-site across the Randstad, remote elsewhere in the EU
  • NEN 4400-1, ISO 9001 and ISO 27001 certified
  • Bilingual delivery in Dutch and English
  • EU data residency, NIS2, DORA, and GDPR factored into the design
Who we work with

Mostly mid-size and enterprise organisations across the Netherlands: in financial services, public sector, healthcare, education, industry, and SaaS. Engagements range from a short cloud assessment to long-running managed cloud operations.

The Factory B.V.
Veraartlaan 12
2288 GM Rijswijk, The Netherlands
info@thefactory.nl

Talk to an engineer
Start your automation journey

Request an Ansible practice review

We'll audit your existing playbooks (or help you start the right way) and come back with a concrete plan: covering structure, testing, controller setup and integration with your IaC.

Talk to an engineer
Behind every assignment

The same engineers stay on the work.

  • Documented decisions. Architecture, trade-offs, and runbooks live in the same repository as the code: reviewable on day one and on day 200.
  • Monthly WTF sessions. Engineers walk through customer work, technical deep-dives, experiments, and what didn’t work. What The Faqtory!: our standing internal review.
  • Standing learning investment. Active Pluralsight and A Cloud Guru access, certification time, and study agreements where the depth justifies it.

The point isn’t novelty. The point is that two years in, the platform still makes sense to the people running it. Read about our engineering culture

goToTop