Getting Started with Terraform on AWS
Having looked at Vagrant previously, the next in the HashiCorp stable is Terraform. Terraform is great because you define the state of the infrastructure you want to have. So rather than manually creating AWS resources such as an EC2 instance, or an S3 bucket, you create a configuration file that contains the definition of what the environment should look like. Terraform will then ensure that your environment meets that definition.
Automate the provisioning of VMs across multiple platforms
In terms of moving away from "point-and-click" administration, one of the first tasks should be to look at what can be automated. If you can automate it, you reduce human error, and you can allow your "customer" to initiate tasks. While virtualization has promised the creation of resources in minutes, the reality is that the processes, approvals, and internal delays, often turn minutes into weeks. So when you automate it, not only is it less error prone, you can turn the task into "standard work", which should mean you can get it done as an ITIL standard change, reducing the delays even further. In ITIL, standard changes don't need to go via a CAB, they are pre-approved.
Backups using Cloudberry Backup
Backups are a critical part of any IT operation, and they should be at home too. Cloud services make the abiilty to run a backup much easier, and obviously you don't require new hardware in order to run it.