Configuration management with Ansible
Standardize IT Infrastructure
Reproducible Instead of Manual
Each configuration is available as code and runs identically on all systems. Manual retightening is not necessary.
New Servers in Minutes
Ansible playbooks deploy standard setups in minutes. If done manually, it would take hours.
Agent-free
Ansible works via SSH. No additional agent on the target systems, which reduces maintenance and the attack surface.
Documented & Traceable
The code is the documentation: every change is versioned in Git and can be reviewed.
Enforced Consistency
The target state has been defined once. Configuration drift is detected and corrected before it can accumulate.
All from a single source
As open-source experts, we offer you a one-stop solution: consulting, playbook development, operations, and training.
Common Problems with Manual Server Configuration
If servers are set up manually and inconsistently, nothing is reproducible. Without centralized configuration management, no one knows exactly what is configured on which server.
Server set up manually
Every admin does it a little differently. Setups are not reproducible and take time to reconfigure with every new system.
Configuration Drift
Over time, the systems drift apart. No one knows what the actual situation really is anymore, and it’s becoming difficult to trace errors.
Knowledge is in people’s minds
Only one person knows how to set up a system. If it fails, the knowledge is lost instead of being stored in shared, versioned code.
Here’s how we work with you
Four Steps to Successful Configuration Management. They guide you from the initial standards to an automated, reproducible infrastructure in a live environment.
Analysis & Concept
We assess systems, recurring tasks, and standards, and determine what is worth automating.
→ We automate the tasks that truly save time and effort.
Setup & Integration
We develop reusable playbooks and roles, version them in Git, and integrate them into a CI pipeline.
→ Infrastructure as Code instead of one-off scripts that no one understands anymore.
Commissioning & rollout
Go-live: Configurations are rolled out consistently across all systems, monitored, and traceable.
→ Deploy changes in a controlled manner instead of manually, system by system.
Support & Operations
We maintain and expand the playbooks and, upon request, can take over operations (MyEngineer) or train your team.
→ Automation remains relevant and evolves along with your environment.
What We Automate
Configuration as code is the starting point; a consistent rollout is the result. The building blocks are interconnected and can be introduced step by step.
Configuration as Code
Server configuration is encapsulated in reusable playbooks and roles rather than in manual steps.
Result: identical , reproducible systems.
Versioned & Traceable
The playbooks are stored in Git: Changes are versioned, can be reviewed, and can be rolled back at any time.
Result: Every change is documented and traceable.
Rollouts & Routine
Result: Hours of manual work are reduced to minutes.
Ensure Consistency
Result: The systems no longer drift apart.
Here’s how you can do that
Consistency, Speed, and Traceability Through Configuration Management with Ansible
Faster & error-free
Standard setups are completed in minutes without typos, missed steps, or manual rework.
Full consistency
All systems are in their defined target state. No drift, no unpleasant surprises during operation.
Knowledge in Code
Setups are documented and shared within the team, rather than being tied to individual people.
What is your solution built with?
For your configuration management, we rely on proven open-source components that run either in-house or via NETWAYS Web Services. You decide what you’ll do yourself and what we’ll take care of.
Ansible
Foreman
GitLab
Icinga
We’ll integrate what you’re already using with
The pipeline integrates code, security, and the target environment. A selection of the building blocks we use to build DevSecOps setups.
Operating Systems
- RHEL / CentOS
- Debian / Ubuntu
- SUSE
- Windows
Code & CI
- GitLab
- Git
- CI Pipelines
- Molecule (Tests)
Operations & Quality
- Icinga
- Idempotence
- Drift Checks
- Reporting
Automation
- Ansible
- Playbooks & Roles
- AWX / AAP
- Ansible Galaxy
Provisioning & Cloud
- Foreman
- VMware
- Proxmox
- Cloud APIs
Expertise in Configuration Management
Want to dig deeper? You might find these blog posts on configuration management interesting.
Ansible Loop: Basics and Looping Across Multiple Tasks
Last updated: October 1, 2026 · Reading time: 4–6 minutes With an Ansible loop, you can run a task for each item in a list.…
Ansible: What to Do with Standalone Roles?
Last updated: September 3, 2026 · Reading time: 9–11 minutes Ansible has been using so-called ” Collections” since 2019. They are the primary method for…
Foreman 5.0
Last updated: August 27, 2026 · Reading time: 7–8 minutes A new major release, Foreman 5.0, is coming soon. Since the first release candidate now…
Ansible and the Elastic Stack
Last updated: August 6, 2026 · Reading time: 4–6 minutes In this article, I’d like to introduce you to the Ansible Collection netways.elasticstack, which allows…
Ansible Icinga Collection
Last updated: July 16, 2026 · Reading time: 4–6 minutes With Ansible and Icinga, you can automate the setup of your entire monitoring environment. The…
Foreman & Katello Update | Fixes, CVEs, and New Releases
Installer Fix and CVE Updates At the Foreman Release Team Meeting on July 1, 2026, it was reported that the previously malfunctioning foreman-installer-source-release is now…
Ansible basics
Last updated: 28.05.2026 Imagine you have to install the same packages, start services and adjust configurations on 10 servers. Manually via SSH, with copy-paste commands…
Questions & Answers
Frequently Asked Questions About This Solution