ControlMonkey makes use of the Terraform Infrastructure-as-Code (IaC) know-how to outline the setting. The platform connects to every supported vendor and reverse engineers dwell configurations into Terraform HCL code. It then creates versioned snapshots each day.
The workflow has three phases. First, the platform performs a full asset stock after connecting a vendor. Second, it identifies which sources don’t have any code protection and flags them for the operator. Third, it permits each day configuration snapshots so groups have a known-good state to get well from.
“The way in which to again up your configuration is with infrastructure as code,” Twizer defined. “We particularly do this with Terraform, and our core know-how, our secret sauce, is to take suppliers or distributors of infrastructure and reverse engineer current configuration, dwell configuration, to code.”
Restoration is executed via a one-click restore. When an incident happens, the platform makes use of Terraform automation to provision the final known-good configuration right into a second tenant. Prospects also can use ControlMonkey APIs to construct automated restoration playbooks triggered from exterior alerting instruments resembling PagerDuty or Datadog.
Scope: Configuration restoration, not vendor availability
To be clear, ControlMonkey isn’t an answer that may resolve the problem of supplier outages. The platform addresses configuration restoration, not vendor availability monitoring.
The first state of affairs ControlMonkey is designed for is a ransomware assault that deletes or corrupts community configurations moderately than information. In that scenario, workloads and information could also be intact however the community management airplane is gone and functions turn into unreachable.
