Infrastructure as Code Explained

Deploying servers and serverless infrastructure programmatically using Infrastructure as Code (IaC) is a great way to improve scalability, predictability, reliability, version control, change management, and disaster recovery. If you're deploying to the cloud, Infrastructure as Code is something you should give serious consideration to learning.
This video introduces the basics, with examples of how it can be used.
➡️ Additional resources
🔗 Introduction to Terraform: www.terraform.io/intro/index....
🔗 Terraform Tutorial (AWS): learn.hashicorp.com/collectio...
🔗 Terraform Tutorial (Azure): learn.hashicorp.com/collectio...
🔗 Terraform Tutorial (Google Cloud): learn.hashicorp.com/collectio...
💬 Follow Me
/ andrewmrquinn
The Pro Tech Show provides tech, tips, and advice for IT Pros and decision-makers.
#InfrastructureAsCode #IaC #Cloud

[@andypokladowski3562]

Bravo ! Best most concise explanation of IaaC on youtube ! Unless there is another one that I haven’t come across after searching and watching 10 other times….😊

[@ProTechShow]

Thanks!

[@ckennington1]

Great video! I am definitely interested in hearing about how to integrate terraform with Ansible to create a full deployment pipeline.

[@ProTechShow]

Thanks Curtis 🙂

[@diamondparteyh]

Yay, I understood the concept because of you! Thanks :)

[@ProTechShow]

Glad it helped!

[@YeetPC]

Great video! A video about configuration management concepts and tools like Ansible would be nice. Keep up the great content!

[@ProTechShow]

Thanks!

[@harrytrueman4216]

Yep, make a video on config management pls.

[@ProTechShow]

I shall put it to the list. Thanks guys.

[@donaldkennedy7993]

great intro to IaC ;)

[@ProTechShow]

Thanks!

[@harrytrueman4216]

Does Inf as code work well for windows domain environments or better for linux environments?

[@ProTechShow]

The provisioning side of things I've showed here doesn't really care because at this stage it's not really Windows or Linux yet. It's more the underlying cloud or virtualisation platform that matters.
When it comes to the configuration management side both work, but Linux is better supported. Most of the tools began on Linux and added Windows support later. The big difference is that most Linux configuration is based around editing a text file, which is really easy to automate and all you need to scale it is SSH. Windows is more complicated and has a load of different interfaces and APIs to deal with. If something exists in Linux it can almost certainly be automated. If something exists in Windows it can probably be automated... as long as Microsoft have exposed it in some way these tools can hook into it using something like WinRM or PowerShell.

[@chrishoedt]

Should/must work for both