22. 06. 2026
Automation, Development, DevOps
18. 09. 2026
Matteo Cipolletta
Automation, NetEye
Making Elastic Configurations Repeatable, Secure, and Governable
How Terraform has turned our NetEye Cloud Elastic configuration management into a declarative, verifiable, and repeatable process that improves governance, security, and operational speed.
From Manual Configuration to a Declarative Platform
The configuration of an observability and security platform quickly grows in complexity.
Workspaces, permissions, retention policies, data views, and user experience settings must remain consistent over time and across many different operational contexts. Managing them manually increases the risk of undocumented differences, recurring errors, and unpredictable activation times.
In practice, manual configuration tends to produce the same recurring symptoms:
- Settings that quietly diverge between one context and another
- Changes that depend on who makes them, rather than on an agreed standard
- Onboarding steps that take longer as the platform grows
- Issues that surface only after they have already affected users
To address this challenge, we adopted Terraform as the foundation for our configuration management. The goal was not merely to automate individual tasks, but to treat configuration as a product: versioned, verifiable, repeatable, and governable.
One Model for Consistent Configurations
The work begins with a simple principle: Every configuration should be clearly described and consistently generated. Starting from a declarative definition, Terraform provisions the components required for each operational context, applying shared conventions while allowing for approved customizations.
This approach combines standardization with flexibility. Core settings are applied consistently, while authorized variations remain explicit, reviewable, and tracked alongside the code. Onboarding a new context no longer requires a series of manual operations; it becomes the controlled evolution of a definition.
The same lifecycle applies to every change, regardless of its size:
Because every stage is automated and repeatable, the same lifecycle scales from a small adjustment to a large batch of changes without adding operational risk.
Security and Governance Built into the Process
Access management is one of the areas where automation delivers the greatest value. Roles, permissions, and visibility boundaries are defined as code, using a consistent model that’s applied uniformly. This reduces the risk that a partial configuration or an isolated change results in privileges that are not aligned with established policies.
Governance in this area also improves. Every change goes through review, can be compared with the previous state, and leaves a history that explains what changed and why. The result is a configuration that relies less on individual knowledge and is easier to verify over time.
In concrete terms, treating access as code means:
- Roles and permissions are defined once and reused everywhere, instead of being recreated by hand for every context
- Every change to a role or a permission is proposed, reviewed, and recorded before it takes effect
- Who changed what, and when, can always be reconstructed from history
- The same guardrails apply whether the change is large or small
Preventing Drift Before It Becomes a Problem
In manually managed environments, the gap between the desired and actual configuration tends to accumulate silently. Terraform makes that difference visible before changes are applied, creating a checkpoint to assess their impact and correctness.
The process uses preventative controls for customizations and permitted combinations. This enables configuration errors and incompatible requests to be identified before they reach the target environment. The execution plan thus becomes a practical quality tool as well as a technical stage of automation.
Among the issues these checks are designed to catch before they reach a live environment are:
- A customization that references a setting outside what’s allowed
- A combination of options that’s technically valid but not supported
- A typo that would otherwise only surface as a runtime error
- A change that would silently overwrite something managed elsewhere
Separating the Platform from Content
Another key element is the separation of responsibilities. Terraform governs the platform’s structural elements, while operational content evolves through a dedicated lifecycle. This distinction prevents content publication from unintentionally changing security or governance settings, and allows the different workflows to evolve independently at a pace appropriate to their purpose.
This separation also clarifies ownership and operational boundaries. Each team can work on its area using appropriate tools and controls without losing the overall consistency of the platform.
| Aspect | Platform structure | Operational content |
|---|---|---|
| Typical owner | Platform engineering | Content and operations teams |
| Pace of change | Deliberate, reviewed | Frequent, lightweight |
| Managed through | Declarative definitions | A dedicated content pipeline |
| Impact of a mistake | Potentially wide-reaching | Contained to the content itself |
More Reliable and Observable Delivery
Automation is now integrated into the regular delivery flow. Changes are first analyzed, then applied in a controlled and repeatable way. Credentials remain outside the versioned definition, while state connects what’s declared with what’s actually present in the platform.
This model improves release predictability and reduces the time required to identify a difference or restore a consistent configuration. The same discipline that makes changes safer also makes it easier to measure their impact and continuously improve the process.
| Dimension | Before | After |
|---|---|---|
| Speed of change | Manual, sequential steps | On demand, automated |
| Consistency | Depends on the operator | Uniform across every context |
| Visibility of impact | Known only after applying | Known before applying |
| Recovery from drift | Manual investigation | Detected and reconciled automatically |
The Value of the Journey
Terraform has transformed configuration from a manual, distributed activity into an engineered process. The main benefits are:
- Consistent, repeatable configurations
- Faster onboarding and changes
- Preventative checks before release
- Reduced risk of drift and untracked interventions
- Greater transparency around ownership and changes
- A clear separation between platform structure and operational content
- A solid foundation for sustainably extending automation
The point is not simply to use a new tool. It’s to build a way of working in which reliability, security, and speed are not competing objectives, but properties of the process itself.
These Solutions are Engineered by Humans
Did you find this article interesting? Are you an “under the hood” kind of person? We’re really big on automation and we’re always looking for people in a similar vein to fill roles like this one as well as other roles here at Würth IT Italy.
Matteo Cipolletta
Author
Latest posts by Matteo Cipolletta
10. 07. 2026
NetEye Extension Packs
Announcing the New NetEye Extension Pack for Audiocodes Devices in NetEye 4.49
31. 03. 2026
NetEye Extension Packs
Announcing the New NetEye Extension Pack for pfSense Firewall in NetEye 4.47
17. 12. 2025
NetEye
Enabling Self-Service InfluxDB Metrics Migration
12. 05. 2025
Log Management, Log-SIEM
Keeping Elastic Agents Updated in the Dark: A Fully Offline Upgrade Workflow