We’ve now reached the final article in this three part series covering Configuration Management in Azure automation. In Part 1, I discussed the Inventory tool and how to onboard an AWS EC2 virtual machine to Azure. Part 2 covered Change tracking and how to monitor changes to various resources on the AWS instance. In this article, Part 3, I will cover Azure State configuration (DSC) and how to register an AWS VM as a DSC node to apply a desired state.
In part 1 of this series, I discussed the Inventory tool that is a part of Azure Automation’s config management and how to on-board an AWS VM for management. In this article, I will cover Change Tracking. With Inventory, you get a report on the Windows files, registry and services, as well installed software for the machines being monitored. However, Change Tracking takes it a step further and provides a notification whenever there is a change to anything that’s being tracked on the machine. It also provides the capability to perform queries against the change logs. Let’s take a look and see how it works.
One of the first questions asked whenever a system or application goes down is “what changed recently”. Ill-planned or unplanned changes are often the underlying cause of failures. And if you live on the Operations side of the IT fence like me, a large portion of your existence is dedicated to mitigating the negative impact of these age accelerating events.