Skip to main content

Types of drift 🔀

Source of truth​

The modern cloud infrastructure is more like a living organism than a static resources that are not supposed to be updated frequently. That's why IaC (Infrastructure as Code) is the most suitable way to build and manage cloud infrastructures, whatever the language you pick. It cloud be Terraform, Ansible, Pulumi, CloudFormation, Azure Bicep...

This infrastructure is managed by different people, frequently making changes to it. That's why it is important to have a unique source of truth, otherwise it will be challenging to track all the changes and troubleshoot errors/incidents when they occur.

By having a unique source of truth, it is also important to constantly monitor if the real infrastructure (that is already provisioned in your cloud provider(s)) has not drifted from its source.

This source of truth could be Brainboard, Git, local files...

Definition​

A drift is when the actual state of the deployed infrastructure diverges from the desired or expected state described in the code. Usually, it occurs when changes are made directly/manually to the deployed infrastructure outside of the IaC tool's control.

Types of drift​

There are 2 types of drift:

  1. Between environments: This happens when the deployed infrastructure in one environment for e.g. staging is different from another environment for e.g. production that is supposed to be part of the same lifecycle of the infrastructure.

    For e.g.

    • When the dev environment is different than staging or QA or production.
    • When the disaster recovery configuration is different from the production.

  2. Between the code and the infrastructure: This happens when the provisioned cloud infrastructure (all resources and their configurations) is different from the configuration that you have in the source of the truth (Terraform code).

The root cause of the drift could be legitimate, for e.g. when there is a security incident and as an emergency response, an engineer can chose to quickly do the action on the console of the cloud provider (like blocking a user) because it may take time to be done through IaC (especially if the infrastructure is big because Terraform may take hour(s) to refresh the state).